• 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.

Resolved Issue with accessing https

Spikerok

Basic Pleskian
The site works when accessed via HTTP, yet when I swap to https my browser times out. Same applies to all sites on the system except for the Plesk control panel.

I had a look at the secure and messages log file but couldn't see anything interesting. No idea on where to start debugging. I am aware that we do have FTPs in place via port 22 where each user has there own dir outside of Plesk, which might have something to do with it.
 
One is WordPress, another one is custom, the third one is a newly created domain with default Plesk page. Neither can be accessed via https.
 
Stupid question - but do you have a firewall that might be blocking 443?

Nginx/Apache or just Apache?
 
I had a look and port is in fact closed.

The port is said to be open within the cloud server panel but clearly, it's blocked within OS.

I had a look at Plesk and it seems to me that I am running Nginx/Apache combo.
 
Let's see if something is actually running on that port. Connect to CLI and run;

# lsof -i:443

If you see nothing - then the issue is that Nginx isn't listening on that port.
If you DO see Nginx showing in your results - continue on.

In general you can use below command to open port 443 (assuming it's not some sort of hardware firewall);

# iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
 
I had a look and port 443 is open and Nginx is listening to the port 443 but for some reason port is not available externally.
 
The problem was due to a second firewall that we have on the server which had to be disabled -.-

Thank you for your support!
 
Back
Top