• 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

SSL Issue

dirtyL-123

New Pleskian
I installed a Cert per Lets Encrypt extension and set it to the domain. but when i open https://mydomain.com it will not open the website and i get a "ERR_CONNECTION_CLOSED" error.
443 is not open at all. but openssl ins installed and when i take a look in the var/www/vhosts/system/mydomain/conf/ngingx.conf anf httpd.conf the certs are the right ones.
Any idea whats wrong ?
Plesk Firewall is not activated in backend so i guess this is not the problem !?
please help out
 
if you do a telnet from an external location to your 443 port. Does it kick you out, is the connection stay open?
Does your website works in http?
 
Trying X.X.x.X...

Connected to mydomain.de.

Escape character is '^]'.

Connection closed by foreign host.

This is what i got on Telnet.....and yes - Http is working as usual.
 
are you able to have an ssh session without issue?

You can try this command: netstat -tulpn | grep "443" (run it as super user)
What is listening on port 443? does you see nginx?

--

Maybe you can give a look to this too : https://kb.plesk.com/en/115587
 
Anything in your syslog file? whats the log plesk give you in your app subscription?
 
i intalled syslog watch - nothing special goin on..only mailserver and the cornjobs im runing...only 1 line i dont know: plesk_saslauthd[26658]: select timeout, exiting ....besides that everythings seams to be okay
 
in your subscription on your plesk account. You have a lot of options like PHP settings, email adresses etc. You have a "Log" section, can you go on it after trying to reach your website in https and provide logs?
Also, are you able to connect to your server with ssh
 
ah okay...so when i connect to https://mydomain.de nothing changes in the syslogs in plesk. but i filtered out all ssl entries for ngingx and apache in the logs and take a look:
2016-01-26 09:49:41Error151.80.31.125404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff2016-01-30 20:10:51Error188.165.15.85404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff2016-02-14 14:25:30Error151.80.31.121404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff

even the bots dont get access to the https protocoll...i dont get it !?
 
ah okay...so when i connect to https://mydomain.de nothing changes in the syslogs in plesk. but i filtered out all ssl entries for ngingx and apache in the logs and take a look:
2016-01-26 09:49:41Error151.80.31.125404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff2016-01-30 20:10:51Error188.165.15.85404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff2016-02-14 14:25:30Error151.80.31.121404GET /robots.txt HTTP/1.0
log-browser-robot.png
2.92 KApache-SSL-Zugriff

even the bots dont get access to the https protocoll...i dont get it !?

Seems to be a 404 error. Could you send me the link to your domain? You can do it privatly if you don't want to make it public.
 
Back
Top