Richard G
Verified User
We've installed a new server in february. From there we restored a lot of accounts from the old server.
Under the impression that on this new server, all existing domains would be using AutoSSL.
By accident I discovered that this is not always the case. I have several domains parked where the main domain is not created with AutoSSL.
All these domains did not get any SSL certificate when restored on this server. There might be others but I haven't checked yet.
So I tried to get AutoSSL to work for these domains, which will not work. For some reason they will not get into the /etc/virtual/snidomains file but also no certificate is created for them for some reason.
The Directadmin error.log is only showing this error every time I try for some domain:
I also tried disabling SSL and enabling again, but to no effect.
In post #3 I've found a bug.
Under the impression that on this new server, all existing domains would be using AutoSSL.
By accident I discovered that this is not always the case. I have several domains parked where the main domain is not created with AutoSSL.
All these domains did not get any SSL certificate when restored on this server. There might be others but I haven't checked yet.
So I tried to get AutoSSL to work for these domains, which will not work. For some reason they will not get into the /etc/virtual/snidomains file but also no certificate is created for them for some reason.
The Directadmin error.log is only showing this error every time I try for some domain:
Code:
2024:03:24-01:14:16: Ssl::getKeyBit: Error checking for key bit size:
2024:03:24-01:14:28: Ssl::getKeyBit: Error checking for key bit size:
2024:03:24-01:14:41: Ssl::getKeyBit: Error checking for key bit size:
2024:03:24-01:14:51: Ssl::getKeyBit: Error checking for key bit size:
2024:03:24-01:15:59: Ssl::getKeyBit: Error checking for key bit size:
I also tried disabling SSL and enabling again, but to no effect.
In post #3 I've found a bug.
Last edited: