Certbot for zammad failed the challenges and gave me unauthorized access [403]

Help
1

My domain is: CreoTicket.computeronsite.net

I ran this command: certbot --apache -d CreoTicket.computeronsite.net

It produced this output:

aving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for creoticket.computeronsite.net
Enabled Apache rewrite module
Waiting for verification...
Challenge failed for domain creoticket.computeronsite.net
http-01 challenge for creoticket.computeronsite.net
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: creoticket.computeronsite.net
   Type:   unauthorized
   Detail: During secondary validation: 23.29.129.71: Invalid response
   from
   http://creoticket.computeronsite.net/.well-known/acme-challenge/aHWqVQNXlK5MlEJ__kUEXJ8P6-CbjezkIsNVpsrml7g:
   403

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address.

My web server is (include version): Ubuntu server

The operating system my web server runs on is (include version):

NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): it is ubuntu server

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 0.40.0

2

Welcome @mahmoudelfawair

The first thing to check is the below thread. There was a recent change by Let's Encrypt to validate domain names from more locations around the world.

4 Likes
3

@mahmoudelfawair, in case it was overlooked/not made clear to you.
The primary validation did succeed; It is the secondary validations that are failing.
That usually points at GeoLocation blocking.

4 Likes
4

Thanks, I disabled geo-location blocking and it worked.

4 Likes