Auto SSL fails

Auto SSL fails

ndimos	May 31, 2025, 9:22 pm \| Post: 1
Group: Member Post Group: Newbie Posts: 2 Status:	Issue was resolved by the Webuzo Support team. Here's a summary of the resolution: Auto SSL Issue Resolution by Webuzo Support Team The persistent "Auto SSL" issue, which prevented the issuance of Let's Encrypt and ZeroSSL certificates due to 404 Not Found errors during ACME challenges, has been successfully resolved. Root Cause: The problem stemmed from a misconfigured Alias directive within the Apache configuration file, specifically acme.conf. This directive was incorrectly directing all ACME challenge requests to a static, system-wide path (/usr/local/apps/apache2/www/htdocs/.well-known/acme-challenge) instead of dynamically pointing to each domain's actual webroot. This prevented certificate authorities from validating domain ownership, leading to consistent 404 errors. Steps Taken to Fix (by Webuzo Support Team): To rectify this systemic misconfiguration, the Webuzo support team performed the following actions: a. Commented out the incorrect Alias directive and its associated Directory block in acme.conf. b. Added a DirectoryMatch directive to correctly allow ACME challenges to be served from each domain's actual webroot. This ensures that the validator can find the challenge files where acme.sh places them. c. Restarted Webuzo’s Apache service to apply the changes to the server configuration. Outcome: SSL validation is now functioning correctly, and certificates can be issued without any further issues. Origin of Misconfiguration: The misconfiguration in the acme.conf file was confirmed to be a system-level default configuration created by Webuzo itself, not a result of any user action. This hardcoded Alias directive was part of Webuzo’s default Apache setup, which sometimes did not dynamically handle multiple domains’ ACME challenges properly.
IP: --

Users viewing this topic
	1 guests, 0 users.