Can't update my server TLS Certificate

[webtopia]

Hi All,

I was running Centos 7 on my server and was running into all sorts of issues. So decided to do a complete clean install of AlmaLinux 8. From there I ran the install of directadmin.

My plan was to recreate all my accounts and upload my websites (I only have a few).

Everything went OK but directadmin setup under https://server-xxx-xxx-xxx-xxx.da.direct:2222/. (where the Xs represent my IP address).

I want to access through https://xxx.xxx.xxx.xxx:2222

So I went about updating everything in the admin account to refer the IP address directly. The issue is the TLS certificate was setup for the https://server-xxx-xxx-xxx-xxx.da.direct:2222/ and it shows my server as insecure. So I tried to manually update it in SSH and I now have the message

x509: certificate signed by unknown authority

Is there an easy way to refresh the TLS certificate for the server using the https://xxx.xxx.xxx.xxx:2222 format or the actual server name (I have a domain registered for my server).

Not for the websites themselves they have been setup ok.

Any help much appreciated.

 

[Richard G]

Everything went OK but directadmin setup under https://server-xxx-xxx-xxx-xxx.da.direct:2222/. (where the Xs represent my IP address)

This is a hostname to help you start.
You have to create your own FQDN hostname, best is before installation, but afterwards it can be changed, just more work.

You can fix it by following this manually very carefully, check all things mentioned!!

Thread '[How-To] Create or change your server's hostname in Directadmin'

Mar 21, 2024

This is a guide on how to create a correct FQDN hostname on a sever or VPS.
I created this newly here in this section, for easier reference and it's also easier to find.

There is also another method, but the method described here is another method which is also still very usable.

Before you install Directadmin you can already take care the correct hostname is used bij Directadmin.

The domain mydomain.com is used her as example and 192.168.0.1 as example server ip. Ofcourse replace all examples with the domain or hostname your are using. So don't use 192.168.0.1 in the real situation...

• Richard G
• Replies: 7
• Forum: How-To Guides

• 

P.s. you won't get an SSL certificate on an ip. You need a hostname.