I have an Ubuntu 24.04.2 LTS server with ISPConfig Version: 3.3.0p1. and many websites installed. I use CloudFlare to manage the DNS records as well. I also have a website where I installed WHMCS, but after I changed the modem device it can't connect to the ISPConfig server anymore with the remote user, and I get the following error message: Code: cURL error 60: SSL certificate problem: self-signed certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) Besides, the ISPConfig interface SSL certificate is not working and the website is not secure. Why is that and how can I fix it?
I've tried that many times but it didn't work. How about the CloudFlare settings? Is there any recommandation?
It seems like Let's Encrypt is not able to validate the ceriticiate. Is the server reachable from the Internet? What do you use Cloudflare for? Do you have proxy enabled in Clouldflare for this host? Check out this FAQ https://forum.howtoforge.com/threads/lets-encrypt-error-faq.74179/
Yes, the server is reacable from the Internet. I use Cloudflare as the DNS server but I don't have proxy enabled for this host. On the other hand, the websites SSL certificates are working but only the ISPConfig interface SSL certificate is not working.
When running ispconfig_update.sh --force I get the following message: Code: Server's public ip(s) (190.160.20.98, 2800:150:107:10a3:b699:baff:fede:d5e0) not found in A/AAAA records for servidor2.surempresa.com: 192.168.0.10 Ignore DNS check and continue to request certificate? What does this mean?
It means your system is likely behind a NAT router. In this case, do what the prompt suggested and continue to request the SSL cert. Btw, you must disable let's Encrypt check in ISPConfig as mentioned in the Let's Encrypt error FAQ checklist, otherwise you won't get SSL certs.
Ok thank you. I fixed the issue by answering y to Ignore DNS check and continue to request certificate?.
Thanks everyone for sharing the steps here. I applied the same approach to my project, and it worked perfectly. Ignoring the DNS check during certificate request finally solved the SSL issue for me. I’ve written about my experience here: https://nolcardbalanceae.com/ in case it helps others working on similar setups.
