• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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