Can't use SSL for /roundcube

[ronoved3v]

I don't understand why domain https://da.xxx.dev
can then be accessed with SSL
but https://da.xxx.dev/roundcube got Your connection isn't private
Please help me.

 

[Richard G]

There is a difference between domain name and hostname, even if the hostname is within the domain name.

Create a seperate DNS record for your hostname.
The request a new hostname SSL certificat like this via SSH:

cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.domain.com 4096

replace server.domain.com with your hostname.

 

[ronoved3v]

There is a difference between domain name and hostname, even if the hostname is within the domain name.

Create a seperate DNS record for your hostname.
The request a new hostname SSL certificat like this via SSH:

cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.domain.com 4096

replace server.domain.com with your hostname.

Thks u very much it work!

 

[zEitEr]

I don't understand why domain https://da.xxx.dev
can then be accessed with SSL
but https://da.xxx.dev/roundcube got Your connection isn't private

I wonder the same. Usually if DirectAdmin has a valid certificate for a hostname, the same is used by a webserver. Thus if directadmin is secured with a valid certificate, then the webserver should be secured with the same certificate too. What do I miss?

 

[Richard G]

Usually if DirectAdmin has a valid certificate for a hostname,

In this case it looks like Directadmin does not have a valid certificate for the hostname.

On installation, in earlier days, a separate hostname certificate was created by DA and one had to create a hostname (so da certificat) manually.

On newer installations nowadays, that won't happen anymore. To prevent odd issues, DA is using the 12.34.56.78.da.direct hostname (or what was it called) and create the certificat for that, so DA will work after installation with https.

However, this domain is owned by DA. So if the hostname is changed, the hostname certificate will not be valid anymore and one has to create a new hostname certificate.

At least, that's how I think it works. Please correct me if I'm wrong.