The redirect method for www. has a snag. Most browsers seem to look for a www.mydomain.com cert before following the redirect. This results in users seeing a warning and not redirecting.
The solution is to add a second domain arg to each of the commands. EG:
I noticed and tried to add a certificate for www using this script and everything said in this thread, but it does not add it. I says
The domain 'abc' seems to already have an ECC cert, let's use it.
[Tue Feb 11 12:26:24 EST 2025] Applying sitelist filter DEPLOY_CPANEL_AUTO_INCLUDE: *
[Tue Feb 11 12:26:24 EST 2025] Applying sitelist filter DEPLOY_CPANEL_AUTO_EXCLUDE:
[Tue Feb 11 12:26:24 EST 2025] Successfully deployed certificate to 0 of 0 sites via UAPI
and no certificate is added. Any suggestion would be really appreciated. With some domains it seems to work in the same hosting package...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The redirect method for www. has a snag. Most browsers seem to look for a
www.mydomain.comcert before following the redirect. This results in users seeing a warning and not redirecting.The solution is to add a second domain arg to each of the commands. EG:
You'll still want to add the redirect, but this will now avoid the error for users.
I noticed and tried to add a certificate for www using this script and everything said in this thread, but it does not add it. I says
The domain 'abc' seems to already have an ECC cert, let's use it.[Tue Feb 11 12:26:24 EST 2025] Applying sitelist filter DEPLOY_CPANEL_AUTO_INCLUDE: *
[Tue Feb 11 12:26:24 EST 2025] Applying sitelist filter DEPLOY_CPANEL_AUTO_EXCLUDE:
[Tue Feb 11 12:26:24 EST 2025] Successfully deployed certificate to 0 of 0 sites via UAPI
and no certificate is added. Any suggestion would be really appreciated. With some domains it seems to work in the same hosting package...