hostname ssl not updated

T

techtroves

New member
Joined
Dec 29, 2023
Messages
2
I set the hostname and i checked it with
hostname -f
also, i checked the 'hostname -f' is same as 'servername" in directadmin.conf
i also installed ssl following below
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single $(hostname -f) 4096

but, still, when i tried to login to directadmin under port 2222, the ssl is still showing as invalid.

kindly help resolve.
thanks
 
You have a real FQDN hostname like server.domain.com and not domain.com?
Did the request process worked without any errors and provided certificate and also restarted services?

If yes, just to be sure, check that this hostname is present in /etc/hosts and /etc/hostname too.
If that is all correct, then you could try this.

Remove these files:
  • /usr/local/directadmin/conf/ca.csr
  • /usr/local/directadmin/conf/ca.san_config
  • /usr/local/directadmin/conf/cacert.pem
  • /usr/local/directadmin/conf/cacert.pem.combined
  • /usr/local/directadmin/conf/cacert.pem.creation_time
  • /usr/local/directadmin/conf/cakey.pem
  • /usr/local/directadmin/conf/carootcert.pem
  • /usr/local/directadmin/conf/letsencrypt.key
  • /usr/local/directadmin/conf/letsencrypt.key.json
After that, request again. You can also to it manually like this:
Code: 
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single server.domain.com 4096

ofcourse replace this example hostname with your own hostname.
 
I have the same issue. Followed your steps, @Richard G still don't have luck. I don't have letsencrypt files, though. Checked with other working servers, I don't have either. The error is NET::ERR_CERT_DATE_INVALID, and it's showing with a wildcard SSL *.domain-using-with-hostname, while I requested single. Any other place should I check?
 
Make sure your server time and date and time zone are correct and also your own computer.
 
gate2vn said:
and it's showing with a wildcard SSL *.domain-using-with-hostname, while I requested single.
Click to expand...
You only use the request_single command for the hostname. For domain names it's normally just request.
If you have the same problem on other working servers, then it might be a configuration issue or customisation issue.

Make sure your computers date/time are also correct.

gate2vn said:
I don't have letsencrypt files, though.
Click to expand...
I can only help with Letsencrypt. Other certificates are to applied in another way, except ZeroSSL which is kind of the same, but probably uses another script to request.

Give us one domain name so we can investigate if we find something. I'm not sure I can be of fast help as I'm being sick at the moment, so will not spend much time at my pc.
 
techtroves said:
I set the hostname and i checked it with
hostname -f
also, i checked the 'hostname -f' is same as 'servername" in directadmin.conf
i also installed ssl following below
cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single $(hostname -f) 4096

but, still, when i tried to login to directadmin under port 2222, the ssl is still showing as invalid.

kindly help resolve.
thanks
Click to expand...
Do you have the same domain on your server?
Let's say you have server.cherry.com are you also running the domain cherry.com on the server? I guess the domain itself does not have a SSL yet if this is the case.

And did you check:

Automatic TLS Certificate For Server Hostname | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com

Command is either:
Code: 
/usr/local/directadmin/scripts/letsencrypt.sh server_cert
or what I use is:
Code: 
/usr/local/directadmin/scripts/letsencrypt.sh request_single $(hostname) 4096
 
Last edited:
gate2vn said:
I have the same issue. Followed your steps, @Richard G still don't have luck. I don't have letsencrypt files, though. Checked with other working servers, I don't have either. The error is NET::ERR_CERT_DATE_INVALID, and it's showing with a wildcard SSL *.domain-using-with-hostname, while I requested single. Any other place should I check?
Click to expand...

Do you have the same domain on your server?
Let's say you have server.cherry.com are you also running the domain cherry.com on the server?
Did you check your zonefile of this domain if this is the case? Maybe you have a wrong zonefile.

If you do not use Let's Encrypt but something else like a commercial maybe check:

Automatic TLS Certificate For Server Hostname | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com
 
Last edited:
Stije said:
Do you have the same domain on your server?
Let's say you have server.cherry.com are you also running the domain cherry.com on the server? I guess the domain itself does not have a SSL yet if this is the case.
[/CODE]
Click to expand...
That's the reason. Thank you.
Just FYI, yes, I am using ZeroSSL and Let's Encrypt.
 
You must log in or register to reply here.
Back
Top