Can't get Let's Encrypt working on the hosting panel

Hi,

I have followed both of these without success:
https://www.howtoforge.com/tutorial/securing-ispconfig-3-with-a-free-lets-encrypt-ssl-certificate/
https://www.howtoforge.com/communit...l-port-8080-with-lets-encrypt-free-ssl.75554/


With the first one, I create the site for example my fqdn is web1.example.com, then I create a site with the fqdn web1.example.com.
I create a new DNS zone, also web1.example.com, I also added and A record to the original DNS zone, web1 point to the server ip.

And the steps up to "Changing ISPConfig 3 Control Panel (Port 8080)".

The ssl certificates does get generated and when I visit the panel the error I receive is that it does not correspond with the current address (I can't remember the error message exactly, but it summarize to that), when I check the certificate in the browser it does state it is a let's encrypt certificate with the domain as web1.example.com.

So I started over fresh with the second guide from ahrasis, the scripts completes and then nothing works, ftp, imap and smtp down. I had to start over again.

I am on the latest version of ISP Config and using Apache.

Please help as I am starting to pull my hair out.

 

According to that you create website web1.example.com twice. In addition to that, if you already have FQDN web1.example.com, you can not create domain web1.example.com.
Have you verified you DNS is correctly set up? If DNS does not work properly, that is one reason why Let's Encrypt fails.

 

Let's encrypt is working perfectly, I did it exactly as on the tutorial.

Here is the error it gives me:
NET::ERR_CERT_COMMON_NAME_INVALID

https://web1.relianx.com/

Note: I have not tried it again, this is only the A record pointing to the hosting. Should I remove the A record from the one zone and only add it to the other?

 

It gives exactly the same error when I remove the web1 A record from zone relianx.com and create a new zone with web1.relianx.com

 

In summary my setup are as follows:

DNS Zones:
relianx.com (with an A record for web1)
web1.relianx.com

Sites:
relianx.com
web1.relianx.com

SSL:
The certificate for relianx.com is created on the panel.
the certificate for web1.relianx.com is created via ssh exactly as on the tutorial.

 

Do you now remember the exact error message?

 

That was also done, I am referring to these commands at the ssh terminal:

Code:

cd /usr/local/ispconfig/interface/ssl/
mv ispserver.crt ispserver.crt-$(date +"%y%m%d%H%M%S").bak
mv ispserver.key ispserver.key-$(date +"%y%m%d%H%M%S").bak
mv ispserver.pem ispserver.pem-$(date +"%y%m%d%H%M%S").bak
ln -s /etc/letsencrypt/live/$(hostname -f)/fullchain.pem ispserver.crt
ln -s /etc/letsencrypt/live/$(hostname -f)/privkey.pem ispserver.key
cat ispserver.{key,crt} > ispserver.pem
chmod 600 ispserver.pem

Every step works fine, even after the above command. Yet going to https://relianx.com:8080 I am greeted with NET::ERR_CERT_COMMON_NAME_INVALID.

Checked the certificate is does show web1.relianx.com and that the issuer is let's encrypt.

 

NET::ERR_CERT_COMMON_NAME_INVALID. <-- On chrome (Checked the certificate is does show web1.relianx.com and that the issuer is let's encrypt.)

 

Thank you Till, I will quickly test it again later tonight and provide feedback.

 

i'm lost here ...
i just need to put ISPConfig pannel (8080) with a true let's encrypt cert.
After install is done how can i put the panel with let's encrypt ?

(my pannel is at https://gestion.domain.com:8080)

 

hello jesse,
"We don't have to do the above anymore as we no longer use certbot webroot."
????
Why ? , certbot is already installed on all web server , as webmaster server (with panel)
there is no easyer method ?

 

humm, not only !
this how to is done for single server setup.
i have multi server , so my panel is hosted on webmaster (server), not on web1, we2 , mail1, 2 etc : servers !
AND : mail servers , are with FQDN : mail1.domain.com , mail2.domain.com
web servers : web1.domain.local, web2.domain.local (for client website, let's encrypt is workling perfectly !)
so i'm pretty lost ;-) ...

ls -alh /etc/letsencrypt
ls: cannot access '/etc/letsencrypt': No such file or directory
(certbot is installed, but after creating website , with domain : domain.com and Auto-subdomain : * ... no let's encrypt cert ....)

 

this is not working for us ...
https://www.howtoforge.com/tutorial/securing-ispconfig-3-with-a-free-lets-encrypt-ssl-certificate/

 

hello th0m, thank answering.
Why on web1 ? my panel is only installed on webmaster server ?
let's encrypt cert (etc) will then created on web1 ... not on webmaster ...
so ...