• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Unable to connect externally

T

Tbdsamman

Guest
Hello all,

I've installed Plesk to my Windows Server 2003 and was able to forward port 80 and see the server from my external IP but I restarted my server and was unable to see my server from my external IP anymore, nor would the internext work on the server. I've tried changeing settings on the server and turning off Plesk, but to no avail.

I was wondering if this is a security feature of Plesk, but it would kinda be stupid since the server would only work locally.

Sorry if theres a post like this, I searched and couldn't find anything.

Any help is welcome and appreciated.
 
Hello Dsam,

I'm very new to Plesk so this could be a very stupid answer, but I need access to port 8443 if I want to get through my Plesk control panel from another location.

Basically, this means I need to type: https://www.mydomain.com:8443. Also note the "https", not "http".

I had to explicitely open port 8443 on my firewall for this to work.

Hope this helps a little bit...

Regards,

Benoit.
 
I am trying to access the "This is the Pleskâ„¢ default page" page from just typing the IP. I don't think opening the admin port would fix my problem.
 
Hello Dsam,

Let's start over. You said: "I was able to forward port 80" - what exactly did you do there to achieve this ?

Also, if you surf to what you expect to be the right page, what do you get: nothing at all (like in "the page cannot be displayed") or something else ? If it's something else, can you post a screen shot ?

Finally: is there a difference if you try to connect externally (i.e. from a remote IP adres) or locally on the machine (i.e. http://localhost, directly in a browser on the console of the server) ?

Regards,

Benoit.
 
I used my firewall to route port 80 so I could see the default page from my external IP and check if everything would work.

When I use my internal IP or localhost on the server I can access the default page but when I try to use my external IP, it comes up with "This page can't be displayed".

I know its not my firewall because I can change it to forward my own computer, installed IIS w/ PHP for testing, and see the forbidden page from my external IP.
 
Hello Dsam,

Ok, I see - I thought you were referring to the Plesk control panel, which is not available on htt port 80 but on https port 8443.

It's clear to me now what you mean, but I would not know why that it the case !

i would suggest in the first place looking for a non-Plesk related issue, since the server does now "know" where you are coming from (internal or external), so the only things I can come up with are rather not Plesk related: correct external IP address, correct port forward from hardware firewall to server, software firewall on the server itself, etc... but it seems to me you got all that covered already.

Please post when you DO find a solution !

Regards,

Benoit.
 
I suppose there is just wrong NAT settings.
Also in case of NAT using yoiu have to set up domains on the internal IPs in Plesk, but DNS records should point to external ones.
I
 
Back
Top