Directadmin Services SSL

[Richard G]

All the certificates point to hostname server-89-116-52-173.da.direct

That's because you're not following the howto.

In the guide you have to look at this line:

Remove these files (as far as present) if the server.xx.xx.da.direct hostname stays present after a hostname change and everything is setup correctly:

Below thise line there are some things you need to remove for things to get working.

Before that, all other things (correct hostname on system and in DA) must already be done.
So if the PTR/rDNS is working correctly for the correct hostname, then you need to remove these files and request a new server certificate and then things should become correct on the correct hostname.

 

[LaqueP]

That's because you're not following the howto.

In the guide you have to look at this line:

Below thise line there are some things you need to remove for things to get working.

Before that, all other things (correct hostname on system and in DA) must already be done.
So if the PTR/rDNS is working correctly for the correct hostname, then you need to remove these files and request a new server certificate and then things should become correct on the correct hostname.

Hi Richard;

I do the process again of your https://forum.directadmin.com/threa...e-your-servers-hostname-in-directadmin.70371/

I deleted all the files, but when I try to generate a new cert the software returns the same Lego error

After delete cert files, directadmin can't start because the https validation.

It's so strange

 

[Richard G]

It's so strange

Yes that is very strange.

Can you issue this command:
whereis lego
it should give the result like:
lego: /usr/local/bin/lego

if that is the case, you can best send in a ticket because something doesn't work as should be then.

 

[floyd]

Try cd /usr/local/directadmin/scripts/ then the ./letsencrypt.sh command.

 

[LaqueP]

Yes that is very strange.

Can you issue this command:
whereis lego
it should give the result like:
lego: /usr/local/bin/lego

if that is the case, you can best send in a ticket because something doesn't work as should be then.

The directory of the tool is in the corred path

Try cd /usr/local/directadmin/scripts/ then the ./letsencrypt.sh command.

The same error.

The think I don't understand is why I can't ping the hostname from other machine.

 

[floyd]

You have to have the hostname set up correctly before anything else will work. If you can't ping the host name then it's not set up yet. Do you not have DNS records for the host name?

 

[LaqueP]

Debe tener el nombre de host configurado correctamente antes de que funcione cualquier otra cosa. Si no puede hacer ping al nombre del host, entonces aún no está configurado. ¿No tiene registros DNS para el nombre de host?

hola floyd,

I configured the servernames like Richard said me (attached)

 

[Richard G]

why I can't ping the hostname from other machine.

From any other machine or only your pc at home? Because if it works from another server, then there is nothing wrong.

If you can't ping it from any machine, then something is wrong with either DNS or nameserver.

You can best post the correct hostname so we can investigate or give it to me by pm if you don't want to post it in public.

 

[Richard G]

The nameservers ns1 and ns2.hstgr.cloud are not registered with your hstgr.cloud domain name registrar.

That doesn't really matter if you use the hostinger DNS. But you didn't copy your A records to the hostinger DNS and not your MX records.
Without those A records, your domain can not be found.

So if you want to use your domain, you have to copy all your records, so A, TXT, MX and DKIM records to your DNS from hostinger for things to work.

 

[floyd]

Remember that all control panels assist administrators. They do not take the place of an administrator. You still have to know how things work.

 

[ericosman]

It seems that hstgr.cloud is not even reacting to anything.

Step one, make sure the url is linked to your server.
Because in this situation.... it will never work.

This seems like wanting to drive a car, bought petrol, bought new weels.....
But not having a car at all..

 

[floyd]

It seems that hstgr.cloud is not even reacting to anything.

Step one, make sure the url is linked to your server.
Because in this situation.... it will never work.

This seems like wanting to drive a car, bought petrol, bought new weels.....
But not having a car at all..

It's more like you bought a car but don't know how to drive it.

 

[ericosman]

It's more like you bought a car but don't know how to drive it.

In that case... just watch youtube... hahaha.
But please dont try to become a driving instructor

 

[floyd]

Do you not have a host name that is based on a domain name that you own?

 

[Richard G]

Do you not have a host name that is based on a domain name that you own?

Yes he does according to the information. But the A records are not in his external DNS, so it won't work until they are in there.

This seems like wanting to drive a car, bought petrol, bought new weels.....

Yes same reason if you buy your wheels from somewhere else. Could also be a beginner with hobby site. We all had to start at some points at lots of personal license owners are devs of hobbyists not used to administer a server, so a learning curve is required.
Just as we all had to do.

 

[ericosman]

Just as we all had to do

Sure, no problem with people that have to and want to learn, me myself also asked looking back on it way too many questions, but i do think people should at least try to see a certain amount of logic.

If your domain is not linked to an ip, you cant create anything.

 

[Richard G]

If your domain is not linked to an ip, you cant create anything.

Correct. But if you don't understand how DNS works.....especially if one is using external DNS... and DNS is not the most easy thing.
One has to learn that too. Which is why I explained he had to copy the records to his external DNS.

So lets wait and see if he succeeds now.

 

[ViT]

I also experience the same. @LaqueP

Hello,

I need to update the SSL certificates for the directadmin Services, I try using the .Letsencrypt.sh script, but it return a Lego error:

./letsencrypt.sh request_single server-xx-xxx-xx-xxx.da.direct 4096
missing 'lego' command, it can be installed using CustomBuild with command:
da build install lego

/usr/local/directadmin/scripts/letsencrypt.sh server_cert
missing 'lego' command, it can be installed using CustomBuild with command:
da build install lego


Lego is installed and all the domains auto-renew is working correctly.

I need the SSL for directadmin services to connect third party services.

Anyone know how to solve it?

 

[LaqueP]

I also experience the same. @LaqueP

I solved creating a subdomain with some domain from yours, is the only way, with other panels you can use the hostinger hostname but with Directadmin I didn't found the way.

 

[fln]

If you are having a problem checking lego version after installing it with CustomBuild, for example:

[root@srvXXXX custombuild]# lego --version
bash: lego: command not found

Make sure your working shell do have /usr/local/bin directory in the PATH environment variable. This environment variable controls where to search for installed applications. You can check it with command echo $PATH, it contains a list of directories separated with : symbo. Example of default linux server PATH variable value:

root@server:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

It might vary a little between different distributions but it is important that it would include /usr/local/bin, because this is where lego tools is installed. If this directory is missing in the list, it might mean you have server configuration customizations that override the default PATH value. Then the source of the change needs to be found and adjusted. If left unfixed you will most likely run into obscure problems in the future running scripts and commands.