• 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

Recent content by Sven A.

  1. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Damn. Thanks for your suggestions. One question. If I delete the domain and all certificates and create new ones and delete the Lets Encrypt Extension and reinstall it, why do I have to backup the "/opt/psa/var/modules/letsencrypt/etc/live" folder and copy it back afterwards? I would think I...
  2. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Hm. I changed the certificate name manually in the server.conf and repeated /usr/local/psa/admin/sbin/httpdmng --reconfigure-all, but I get the same error message. I don't know why, but he uses the old certificate file name which can't be found in the server.conf anymore. Any ideas why? Are...
  3. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Thanks. I tried both. The Webserver Configuration Troubleshooter and the command line way. But both give me the following error:Execution failed. Execution failed. Command: httpdmng Arguments: Array ( [0] => --reconfigure-server [1] => -no-restart ) Details: [2017-04-12 14:26:13] ERR...
  4. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    In Plesk I get now the following error message: AH00526: Syntax error on line 168 of /etc/apache2/plesk.conf.d/server.conf: SSLCertificateFile: file '/opt/psa/var/certificates/certgz9PAPJ' does not exist or is empty .
  5. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Ok. This changes the error if I try to run my domain via https from "can't connect" to "502 bad gateway". And the proxy_error_log says: [error] 10698#0: *251562 SSL_do_handshake() failed (SSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol) while SSL handshaking to upstream...
  6. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED REJECT tcp -- anywhere anywhere tcp flags:!FIN,SYN,RST,ACK/SYN reject-with tcp-reset...
  7. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Nope. Never. As I said before it's almost a default installation. The only thing I changed is a private/public key based SSH access and removing the password based one.
  8. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    So this is wrong? But how do I change this? If I change it by hand it will be changed back later from Plesk (at updates or so). <IfModule mod_ssl.c> <VirtualHost xx.xxx.xxx.xxx:7081 > ServerName "mydomain.tld:443" ServerAlias "www.mydomain.tld"...
  9. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Ok. I can't find anything special or wrong. First I used find /etc/apache2 -type f -name "*.conf" -exec grep --color -Hni ":443" {} \;, which found nothing. Then I used find / -type f -name "*.conf" -exec grep --color -Hni ":443" {} \; which listed several things: 1. the nginx and httpd conf...
  10. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Yes. The IP is secured with the default certificate. Ok. Thanks. I will investigate these files. Let's see what's wrong with my Plesk.
  11. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Damn, sorry. Ok. 1. Yes. Apache AND nginx use the same certificate. 2. ‪Ubuntu 14.04.3 LTS‬ and Plesk 12.5.30 Update #62, nginx version: nginx/1.11.1, openssl 1.0.1f 3. Yes. No firewall blocks port 443. And yes, Fail2Ban doesn't block this port. 4. No, I don't have SELinux installed. lsof -i...
  12. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Both tests fail. SSL Server Test says "Assessment failed: No secure protocols supported" (I think because it can't connect to the server) and HTTP Request and Response Header says "Connect to xx.xxx.xxx.xxx on port 443 ... failed Error while fetching URL" But why? And also I tried to run...
  13. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    "FastCGI served by nginx" isn't in the select, so I chosed "FPM served by nginx", but the error message in the nginx logs remains the same. I also changed from Lets encrypt to none and also to the default certificate. Nothing changes. I can't access the domain via https. With http everything...
  14. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Sure. Thanks. Dropbox - plesk-hostingsettings.jpg
  15. Sven A.

    Issue Plesk 12.5.30 and Lets encrypt - ERR_CONNECTION_RESET

    Ah ok. I see. Thanks. So that's not the problem. I tried plesk repair web -y, but it changes nothing. Any ideas where else I could something could wrong?
Back
Top