Hi, am unable to connect to my control panel on its URL on centos 7.6 with ISPConfig 3.1.15p2 after tried to secure its interface with SSL following the guide https://www.howtoforge.com/tutorial/securing-ispconfig-3-with-a-free-lets-encrypt-ssl-certificate/. Mistake was, i ran ispconfig_update.sh before creating a site for the server FQDN. i now get the error: Error code: SSL_ERROR_RX_RECORD_TOO_LONG how can i recover from this silly mistake?
That actually is not a problem. You can run that process again and choose to create ssl for ispconfig (which will be using the self-signed certs created during the process) and later change them to letsencrypt certs by following the tutorial again.
Already tried that, not fixing the problem, Is there a way to revert back to http, so i can log in, create the site & start the process again?
Perhaps not back to http, but doing what @ahrasis wrote in #2 should get your ISPConfig Panel working with self signed HTTPS certificate. Then you can expiment with setting things up again.
I had a similar problem view days ago. I solved it by manually changing /etc/apache2/sites-available/ispconfig.vhost I inserted the "snakeoil" certificate and key, instead of the default ispconfig ones. So the SSL Configuration part of the vhosts-file looked like this (please make a backup if this file before): Code: # SSL Configuration SSLEngine On SSLProtocol All -SSLv3 SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key # SSLCertificateFile /usr/local/ispconfig/interface/ssl/ispserver.crt # SSLCertificateKeyFile /usr/local/ispconfig/interface/ssl/ispserver.key # SSLCACertificateFile /usr/local/ispconfig/interface/ssl/ispserver.bundle After that I was able to login in ispconfig again and could configure Let's encrypt with the tutorial. Of course, at the end you have to revert the changes of the ispconfig.vhost (or copy back the backup of that file you've made before) so it points again to its own certificate.
You can always manually edit your website config (to support http), however, ispconfig will overwrite it with the next update.
