When adding new domain - Unable to write user's httpd.conf

zwankie

Verified User
Joined
Apr 19, 2020
Messages
91
Hi,

I have a strange problem on a DA 1.645 on AlmaLinux 8
There is only user admin on the server as this is a Personal license

When I try to create a new domain I get this message:

Unable to write user's httpd.conf
Unable to read my.domain.com.subdomains file
Unable to read my.domain.com.subdomains file
Proxy Config write error, above.

Pushing httpd.conf rewrite to background task.
Domain Created Successfully

Then when deleting the domain I get:

Error deleting testdomain1.com
testdomain1.com's config files have been removed
Unable to write user's httpd.conf
Unable to read my.domain.com.subdomains file
Unable to read my.domain.com.subdomains file
Proxy Config write error, above.

What's interesting is that there is no domain called my.domain.com (this was renamed for privacy) visible under the list of domains (User > Domain Setup) under the user admin on the server.
However, it is listed in the Dashboard dropdown and also when I go to Admin > Show All Users and in Dashboard > PHP Settings then I see the my.domain.com listed. It is also under /home/admin/domains/. So it is definitely somewhere in the system, I just can't remove it.

I might have added it in a test at some point, I can't remember now but I can figure out how to delete it from DA.

I tried ./set_permissions all and ./build rewrite_configs but it does not help.

Any advice would be appreciated.
 
Last edited:
Did you ever at some pointed added that domain? If yes, then at least we know that it's not something odd.

However, the problem is odd. It might be necessary to remove that domain via SSH.
Could also be a permission issue.

Could you give the output of this command in SSH?
ls -la /usr/local/directadmin/data/users/admin
 
The domain probably still exists in /usr/local/directadmin/data/users/admin/domains.list and you might need to remove it manually.
 
Thanks for the replies.
This was very strange, I managed to solve it by adding it as a domain again then deleting it.
 
Back
Top