• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue SSL drives me crazy on 12.5

PaulRomeijn

New Pleskian
Hi guys,

I have been trying to run a website thru https and have not been able to get it to work.

  1. Requested the certificate. (all OK)
  2. Installed the certificate. (all OK)
  3. Turned on SSL Support and selected the SSL Certificate (all OK)
When trying to access the website thru HTTPS nothing happens, it just stays at HTTP
When changing the additional http/https/nginx redirects in "apache & nginx settings" the site
changes to https but shows me a "This site can't be reached" message.
I have tried on Chrome, Safari and Firefox and cleared cache/history after every change.

I am out of options and searching all the forum didn't provide me any useful answers.

If anybody has an idea, please help.

Thanks,
Paul
 
Does the website use an .htaccess file? Does that contain a rewrite rule? Is your CMS set to use a fixed URL (is a URL entered in a configuration table, so that the CMS will always redirect to that URL upon initialization)?
 
Does the website use an .htaccess file? Does that contain a rewrite rule? Is your CMS set to use a fixed URL (is a URL entered in a configuration table, so that the CMS will always redirect to that URL upon initialization)?

It is a Wordpress site which has a .htaccess file and has the fixed URL setup but I have tested with an other unused domain name without CMS, just the default Plesk page and a self-signed certificate and that is not working either so I think it is a server wide problem :-(
 
Does the issue show up in access.log or error.log files? The request to Nginx and/or Apache should be logged there and may have thrown an error leading to the cause.

but I have tested with an other unused domain name without CMS, just the default Plesk page and a self-signed certificate and that is not working either

Does your server respond to port 443 requests at all when you query it from an external service, e.g. test https://www.ssllabs.com/ssltest/ against your host name? Do you have any security extension installed that might be blocking the requestion? If you have Fail2Ban activated, have you added the localhost address to your whitelist? Else Nginx might fail to request services from Apache.

... additional http/https/nginx redirects in "apache & nginx settings" ...
What exactly is that? There should not be any entries by default in these sections. If you have redirects or any individual settings there, they might cause the issue.

Have you tried to reconfigure the domain?
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain <DOMAIN>

Have you tried to disable Nginx, does the issue occur, when only Apache is serving the site?
# /usr/local/psa/admin/sbin/nginxmng -d
 
Does the issue show up in access.log or error.log files? The request to Nginx and/or Apache should be logged there and may have thrown an error leading to the cause.



Does your server respond to port 443 requests at all when you query it from an external service, e.g. test https://www.ssllabs.com/ssltest/ against your host name? Do you have any security extension installed that might be blocking the requestion? If you have Fail2Ban activated, have you added the localhost address to your whitelist? Else Nginx might fail to request services from Apache.


What exactly is that? There should not be any entries by default in these sections. If you have redirects or any individual settings there, they might cause the issue.

Have you tried to reconfigure the domain?
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-domain <DOMAIN>

Have you tried to disable Nginx, does the issue occur, when only Apache is serving the site?
# /usr/local/psa/admin/sbin/nginxmng -d

The response thru the ssllabs is negative, no https

I know there shouldn't be any entries by default but it did make a change (which did not work either btw)

Will look into the logfiles and try your suggestions, but it is the same for all domains.
 
The response thru the ssllabs is negative, no https

You are not saying that the server is responding but delivers certificate warnings or other data. Do I understand correctly that your statement "response is negative" means the server is not responding at all? If that is the case, a firewall is blocking port 443. You will need to find out, if either a hardware firewall in front of your server is blocking traffic or if the software firewall on your machine is blocking traffic. Are your sure that all traffic to port 443 is blocked? I have never seen that before and cannot think of any reason why that should be the case. Are you using the Plesk Firewall extension or have you configured iptables manually?
 
Back
Top