• 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 Can't access SSL/HTTPS sites on server

surfgatinho

New Pleskian
Hi,
I'm setting up a new Plesk server. I transferred over a few domains from the old box and some worked fine, others didn't.
I'm running Apache and Nginx.

All the non-https ones are OK, but none of the https ones are working. Another strange thing is the domain names resolve fine wherever I try them from but I don't get a ping response - firewall rule says to allow.

Plesk is working fine over

Things I've tried are renewing the SSL certificate (LetsEncrypt) and restarting everything.

Another thing - I can access the http sites locally (running CURL) but not remotely. I tried telnet to port 80 on my PC and this works, but not on port 443...
So seems to be some kind of vhost thing(?) or not listening on 443 externally(??)

Any ideas? Thanks.
 
Just re-imaged the server and this is still not working... Sites work fine on https, but as soon as I go to https version I get nothing.

Getting lots of these in the logs too:
AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name

This is a brand new server. Why can't I get SSL to work on it?! Help!
 
Last edited:
OK, ignore all the above. My hosting company Ionos seem to think it is a good idea to not allow port 443 on their default firewall (additional to Plesk firewall). Can't believe that in this day and age they would do that....
 
Back
Top