• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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