• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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