• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Sites not accessible over https, except for plesk panel.

Pavel12

New Pleskian
Hi all and sorry for rooky question, but I can't figure this out:

My server (SentOS / Plesk) is behind router. Router is configured to forward ports 1-10000 to the server.

Everything works on local network via http and https.

When accessed through public IP, only plesk panel works via https, all other sites are not accessible, and web stats are not accessible as well.
Everything works via http.

I think it has something to do with linux settings for all individual webspaces, but not sure how to deal with it.

Any help appreciated.
Thanks!
 
Hello,

Can you please post the error you are getting while accessing using "https". Also, please run the following command in server,

netstat -ntlp | grep 443

and check if any service is running under this port.
 
Connection timed out. ERR_CONNECTION_TIMED_OUT

netstat -ntlp | grep 443
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LIST EN 1707/sw-cp-server
tcp 0 0 192.168.0.33:443 0.0.0.0:* LIST EN 1493/nginx
tcp 0 0 :::8443 :::* LIST EN 1707/sw-cp-server

192.168.0.33 is the local ip of the server.
This tells me that nothing is running, but souldn't it be 0.0.0.0:443 instead?

Thanks
 
Problem solved.
Router is to blame.

When remote management on the router is forced to https, it takes up the port.
 
Back
Top