TechDaddies
Verified User
- Joined
- May 3, 2020
- Messages
- 35
Today we installed CustomBuild updates on our server, the same way we do every Monday. I don't know what happened during the update, but everything broke. It seemed like DA reverted back to default settings somehow. It no longer knew that we were running Litespeed. It forgot the server's hostname. All kinds of weird issues occurred.
We got everything back to normal, EXCEPT we cannot access DA via the server's hostname. When we try to renew the hostname's SSL cert with
, we get the following error message:
This kind of makes sense, because the issues we noticed after the botched upgrades this morning seemed to be caused because the directadmin.conf was basically reset back to the default. It was missing our servername line, for example, and forgot our ethernet device.
Here are the current contents of directadmin.conf
We have multiple DA servers with the same software configuration, and this is the only one we experienced this issue on.
Unfortunately, I did not realize until today that our /usr/local/directadmin directory wasn't being backed up as part of our daily remote backups, so I cannot look at the old version of directadmin.conf to see what may be different.
Any help is very appreciated, both in figuring out what happened (And how to prevent in the future), and what is wrong with the directadmin.conf that's causing the Lets Encrypt renewal for the hostname to not go through.
We got everything back to normal, EXCEPT we cannot access DA via the server's hostname. When we try to renew the hostname's SSL cert with
Code:
/usr/local/directadmin/scripts/letsencrypt.sh request_single our_hostname.com 4096
DirectAdmin certificate has been setup.
There are too few entries in the directadmin.conf after the read. Something is likely missing/broken. Please report the exact commands used to DirectAdmin Support if the file on disk still has more than 20 valuesThere are too few entries in the directadmin.conf after the read. Something is likely missing/broken. Please report the exact commands used to DirectAdmin Support if the file on disk still has more than 20 valuesSetting up cert for Exim...
Setting up cert for WWW server...
Setting up cert for FTP server...
The services will be restarted in about 1 minute via the dataskq.
This kind of makes sense, because the issues we noticed after the botched upgrades this morning seemed to be caused because the directadmin.conf was basically reset back to the default. It was missing our servername line, for example, and forgot our ethernet device.
Here are the current contents of directadmin.conf
Code:
http2=1
unified_ftp_password_file=1
cloud_cache=1
nginx=0
nginx_proxy=0
litespeed=1
openlitespeed=0
ethernet_dev=enp94s0f1
apache_ver=2.0
enable_ssl_sni=1
letsencrypt=1
servername=our_hostname.com
dovecot=1
add_userdb_quota=1
frontpage_on=0
We have multiple DA servers with the same software configuration, and this is the only one we experienced this issue on.
Unfortunately, I did not realize until today that our /usr/local/directadmin directory wasn't being backed up as part of our daily remote backups, so I cannot look at the old version of directadmin.conf to see what may be different.
Any help is very appreciated, both in figuring out what happened (And how to prevent in the future), and what is wrong with the directadmin.conf that's causing the Lets Encrypt renewal for the hostname to not go through.