Let's encrypt issue on server hostname

[gerbenvandijk]

Hi there, I'm trying to get a let's encrypt certificate on the direcadmin control panel at porbut I'm running into the "domain does not exist on the system" message.

For the example, let's say that my directadmin is running on server.com:2222

I've got SSL=0, enable_ssl_sni=1 and servername=server.com in directadmin.conf (haven't changed any other settings); and I have setup several lets encrypt certificates successfully on other domains that are running on this server successfully.

Am I missing something here? I'm following the directions provided at https://help.directadmin.com/item.php?id=15 (under "Using the free "Let's Encrypt" tool to secure 2222").

Thanks a lot, and kind regards,

Gerben van Dijk

 

[DirectAdmin Support]

Hello,

You'd want SSL=1 in the directadmin.conf, then restart DA (after running the tool).
Make sure you're running the perl regex and the echo commands, mentioned in the guide.

John

 

[rnbwkat]

related - domain, + webmail, etc.

Question sort of related to this. I got the "Let's Encrypt" cert installed and working on the primary www domain, but if I try to go to the webmail.domain.com that is not valid for the cert. How do I add a SAN to it, or resolve this - any ideas/suggestions?

Thank you

 

[DirectAdmin Support]

Pre-release binaries:
http://help.directadmin.com/item.php?id=408

have this change:
https://www.directadmin.com/features.php?id=1851

So you could either add the webmail subdomain, if it doesn't already exist.. OR in your case I'm guessing just add webmail to the list, add the whole line to the directadmin.conf

[COLOR=#2E343D][FONT=Open Sans]letsencrypt_list=www:mail:ftp:pop:smtp:[B]webmail[/B][/FONT][/COLOR]

John

 

[zeus]

Pre-release binaries:
http://help.directadmin.com/item.php?id=408

have this change:
https://www.directadmin.com/features.php?id=1851

So you could either add the webmail subdomain, if it doesn't already exist.. OR in your case I'm guessing just add webmail to the list, add the whole line to the directadmin.conf

[COLOR=#2E343D][FONT=Open Sans]letsencrypt_list=www:mail:ftp:pop:smtp:[B]webmail[/B][/FONT][/COLOR]

John

Hi John,
I have the need to get Let's encrypt over webmail.domain.com and I followed your hint, adding:
letsencrypt_list=www:mail:ftpop:smtp:webmail
letsencrypt_renewal_success_notice=1
So I submitted again the request with successfully message.
But if I browse https://webmail.domain.com I get error message, https://domain.com works fine.
What I'm doing wrong?
Have I follow the pre-release guide? My directadmin is 1.50.01.
Thank you very much
Regards

 

[zEitEr]

1. Make sure you've got an empty line at the very bottom of directadmin.conf after you added the new line with letsencrypt_list=
2. Make sure you restarted Directadmin
3. Make sure /usr/local/directadmin/data/users/<username>/domains/<domainname>.san_config has webmail.domain.com in a line with subjectAltName=
4. Make sure that the cert was re-generated
5. Make sure that nginx or apache or both restarted fine (you need to control PID).

 

[zeus]

Hi Alex,
thanks for your help.
I double checked your list but the https doesn't work.
My doubt: 4. re-generate the certification, I sent again all the subdomains I need (webmail included) and the message was success for all of them. Is it right?

 

[zEitEr]

How did you add webmail.domain.com? Did you modify templates or use a subdomain management page in Directadmin for it?

 

[zeus]

Hi Alex,
I think I modified template because when I bought this server I followed this guide: https://help.directadmin.com/item.php?id=92. So the webmail is automatic for every domains. I don't see webmail in the subdomain list for any users.
To use Let's encrypt I followed this guide https://raymii.org/s/articles/Lets_Encrypt_Directadmin_Now_Built_In.html.

 

[zEitEr]

The guide https://help.directadmin.com/item.php?id=92 does not cover a section for 443 (HTTPS). So when you try to open a webmail.domain.com over HTTPS you get a cert for hostname. Thus you need to customize a template virtual_host2_secure.conf for it.