• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

https Not Working - Help!

C

Chris

Guest
I have a new Plesk 7.5.3 server running on CentOS 3.3. I set up a domain for SSL (I have been using Plesk for quite some time and I'm very certain I set this up correctly). The domain works correctly via http; however, when I go to https://www.domain.com I get a "Cannot find server" error.

When I restart Apache I'm getting this error:
NameVirtualHost xxx.xxx.xxx.xxx:443 has no VirtualHosts

(The xxx's are IP addresses of course.) It repeats the same message for all of the IPs on the server. Apache starts okay, but no https. I looked in the httpd error_log and nothing there to indicate the problem.

I should mention that the Plesk control panel is working fine, so I assume SSL is running on the server okay.

I did a search here and found a couple of threads that talk about this exact problem but no solutions. I hope someone can help.
 
I have done the update from atomicturtle (apache en mod_ssl) after that everything was working!
 
This was a stupid mistake on my part. mod_ssl was not installed. I assumed it was because the Plesk control panel was working under https. After installing mod_ssl everything is fine.
 
Back
Top