Debian, ISPConfig 3.1* SSL is working for ns1.domain.com:8080 Followed this tutorial: https://www.howtoforge.com/communit...l-port-8080-with-lets-encrypt-free-ssl.75554/ No SSL for https://domain.com and https://www.domain.com Both with A record to same IP as ns1.domain.com (which works with https:// + :8080) Without https:// I get the apache index page, which is what I want (/var/www/html). However please see images below showing browser SSL ERR on https:// links without the :8080 Should I somehow issue another certbot ssl, or use a bundle with the current, or is it a DNS record issue. Thanks
You do not say what os you use or version of ISPConfig, but post in version 2 forum. Recent versions of ISPConfig 3 support Let's Encrypt certificates for website. There is a tick box in website settings. https://github.com/ahrasis/LE4ISPC
ISPConfig 3.1* and Debian. Sorry, I have updated the post. The tick box is only available when a website is created on and by ispconfig, with a file path such as /var/www/client6 Which would effect my original plan of using /var/www/html (where the apache index file is) The tutorial I linked showed how to use LE4ISPC but not that it was necessary or important. Is it critical I go through the tutorial again and this time use the le4ispc sh script?
I ran the le4ispc script, as per the initial post' tutorial.. and continue to see the same problem. Ok, so If I create a website with ISPConfig for domain.com... then use SSL create/save on ISPConfig, will it be running by a separate letsencrypt cert than https://ns1.domain.com (which only works with port :8080 ... little concerning)
Update. I have now created domain.com website within ISPConfig admin and have successfully generated the SSL certificate. However https://domain.com still shows ERR_SSL_PROTOCOL_ERROR Btw. Thank you for the suggestion, I was pretty stuck with the idea that having /var/www/html would be better (probably OCD) I can live with it I guess lol
Did the certificate get created OK? https://www.howtoforge.com/community/threads/lets-encrypt-error-faq.74179/