Hostname SSL certificate is requested automatically during setup ?

[MaXi32]

When I install DirectAdmin for a new server, I notice that https://server.domain.com:2222 is accessible and has valid SSL from letsencrypt without any notice from the terminal how it was done. Does that mean, we do not need to manually request SSL for the hostname again as mentioned here?

Automatic TLS Certificate For Server Hostname | Directadmin Docs

DirectAdmin Knowledge Base

docs.directadmin.com

How can we tell the DA installer to use another certificate provider like zerossl during setup (I don't like letsencrypt) ? I don't see any documentation about these changes anywhere. Can anyone confirm this magic thing?

If you ask, the reason I need this information is to make my DA automated script work in the correct flow. thanks.

 

[Richard G]

we do not need to manually request SSL for the hostname again as mentioned here?

On a fresh install this is not needed anymore if all is correct.
However, you have to doublecheck if the hostname is correct. Because in certain cases, DA will put in a hostname themselves to be able to be resolved during installation, to prevent installation from failing for that reason.

In this thread all is explained.

Hostname selection during install

On new servers I've installed recently, the setup script picks a generic server-.da.direct hostname. The server already has a proper hostname, and it's valid in both forward and reverse DNS. Why does the install script insist on setting this third party hostname? At first glance, I can't find...

forum.directadmin.com