Hi I'm trying to update my ssl certificate. It's a godaddy certificate. I have a Ubuntu 16.04 and the lastest ispconfig I pretty much tried everything. But always ends up with no page work ERR_CONNECTION_REFUSED Both on my website and admin site to ispconfig. If I create a new one it just creates files h2osport.se.crt.err h2osport.se.csr.bak etc... I'm going crazy because I had to recover my server 100 times last two weeks. Any ides?
Enable the ISPConfig debug mode by following the steps from this guide: https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/ After doing so, set the new SSL cert for the web and run the server.sh script manually. Share the output with us.
You are using a really old Ubuntu version which is not supported by latest ISPConfig anymore. ISPConfig 3.2.5 supports Ubuntu 18.04 and Ubuntu 20.04. This does not necessarily has to be the reason or related to your issue, I just want to mention it as it might be related. But debugging like @Th0m mentioned will show if there are any issues related to the very old OS that you use.
Hi How's the correct way to set new ssl? I have two files from Godaddy one is bundle. In Ispconfig there's SSL key, request, cert from my old cert. Bundle is empty.
The steps to update your SSL cert are: 1) Copy the existing CSR. 2) let it sign from godaddy again and copy the new SSL CRT that you received from godaddy into the SSL certificate field. Copy the SSL bundle into the SSL bundle field. 3) Choose save certificate as action and press save. But these easy steps only work if you did not delete the old key and if you did not recreate a new self signed SSL cert as this would have wiped out the old key and changed the CSR. If you did created a new self-signed cert instead of renewing the old one or if you deleted the old cert and key and you don't have a backup of the old key, then you will have to follow these steps: 1) Update ispconfig to nightly build, all SSL CSR is not shown in current stable version. 2) Create a new self signed SSL cert so you get a new key and csr. 3) let the new CSR sign again from godaddy. 4) let it sign from godaddy again and copy the new SSL CRT that you received from godaddy into the SSL certificate field. Copy the SSL bundle into the SSL bundle field. 5) Choose save certificate as action and press save.
They stay there. You should really read the manual, it's all described there as tsp by step instructions incl. screenshots.
I'm think of changing to a paid service in Godaddy 26.08.2021-01:17 - DEBUG - Calling function 'check_phpini_changes' from plugin 'webserver_plugin' raised by action 'server_plugins_loaded'. 26.08.2021-01:17 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock finished server.php. in Ispconfig CONFIGURATION ERROR 2021-08-26 00:57 : Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
The issue is that you seem to have mixed up ssl certs and keys, apache can't start if you provide him with a invalid key/cert combination. ISPConfig prevents this normally, so either this protection has been disabled on your system or some of the SSL files were edited manually and not trough ISPConfig UI. But that#s not dramatic and can be sorted out. If you need help by remote login, send @Th0m a PM, he provides ISPConfig support services and might be able to help you to sort this out. I don't think that Godaddy support knows ISPConfig, the'yll probably mess things up even more or manually edit files which they should not edit.
SOLVED I got pissed of so I been sitting all day and updating everything on my server. Now it's Ubuntu 18.04. It was a lot that wasn't updated also.... But I saw now that in under options in my site under Apache Directives there was a link to a old bundle file. I just deleted that and could save my new ssl certificate.
