There is an issue with apache DCV validation while apache runs on a custom port. This may result in accessing the DCV temporary files via proxy from another webserver in port 80
Steps to Recreate the issue:
1) Access the key webdisk.example.com/.well-known/pki-validation/DE86811B0380F9DFF632716F443CF18D.txt via apache on port 80 works fine without redirection to ssl port
2) Change apache port to some other port say 9080 , then webdisk.example.com:9080/.well-known/pki-validation/DE86811B0380F9DFF632716F443CF18D.txt, won't work. It always redirect to HTTPS.
For updating the correct Autossl certificate those subdomain urls must be need to be working in HTTP instead of HTTPS even with custom port change in apache. This issue exist in all versions of cpanel.
Steps to Recreate the issue:
1) Access the key webdisk.example.com/.well-known/pki-validation/DE86811B0380F9DFF632716F443CF18D.txt via apache on port 80 works fine without redirection to ssl port
2) Change apache port to some other port say 9080 , then webdisk.example.com:9080/.well-known/pki-validation/DE86811B0380F9DFF632716F443CF18D.txt, won't work. It always redirect to HTTPS.
For updating the correct Autossl certificate those subdomain urls must be need to be working in HTTP instead of HTTPS even with custom port change in apache. This issue exist in all versions of cpanel.
Last edited by a moderator: