Certbot failed to report authenticate some domains (authenticator:standalone) reddit / selfhosted ---------------------------------------------------------------------- anasp1 · 2023-12-05 05:31 I ran this command: sudo certbot certonly --standalone -d MYDOMAINNAMEHERE It produced this output: Requesting a certificate for MYDOMAINNAMEHERE Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: MYDOMAINNAMEHERE Type: connection Detail: 52.x.x.x : Fetching [http://MYDOMAINNAMEHERE/.well-known/acme- challenge/vS5u\_wy5wNjthh9wrLKu5tOid7pn0SBbGmS\_GjfaN0I:](http://mydom ainnamehere/.well-known/acme- challenge/vS5u_wy5wNjthh9wrLKu5tOid7pn0SBbGmS_GjfaN0I:) Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet. My web server is (include version): nginx 1.18.0 The operating system my web server runs on is (include version): Ubuntu 22.04.3 LTS My hosting provider, if applicable, is: AWS EC2 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): No The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.21.0 **Addtional details of issue:** What ended up happening was i am trying to host my app that is running in a docker container on my instance on a specific subdomain (lets say prefix.test.dev). I have got the app running the docker container and I can access it via the ipv4, and now I am trying to use certbot to ensure https because it ends in a .dev subdomain. And then I messed up in some configuration, so I decided instead of trying to troubleshoot my way out of this pit, I'll just nuke the EC2 instance (terminated it) and start fresh in like 15 mins. So I did that, but I forgot to deactivate / detach all the certbot stuff that I had previously setup for my domain name, which by the way, was successfully authenticated as HTTPS. So I think that's why it's failing. MY QUESTION IS, how long before I am able to use certbot again on my new fresh instance for the domain name that I wanted? The old instance with the certification stuff is terminated and gone, so I have no way of reaching it and detaching / deleting the previous certifications... ---------------------------------------------------------------------- NoNameJustASymbol · 2023-12-05 05:41 Their certs are good for 90 days. So, you have to revoke it or wait the 90 days... or use a different name. Did you get the original cert with or without an account? ---------------------------------------------------------------------- anasp1 · 2023-12-05 05:45 Account for what? I did it all through the CLI on my ubuntu EC2 machine. ---------------------------------------------------------------------- NoNameJustASymbol · 2023-12-05 05:48 [https://letsencrypt.org/docs/revoking/](https://letsencrypt.org/docs/ revoking/) ---------------------------------------------------------------------- NoNameJustASymbol · 2023-12-05 05:50 An ACME account for certbot at Let's Encrypt. Forget that see my other response with the link to revoking. ---------------------------------------------------------------------- anasp1 · 2023-12-05 05:52 I am on another EC2 instance though, I don’t think there is any access to my other terminated EC2 instance which had the certbot info on it and certified it. ---------------------------------------------------------------------- NoNameJustASymbol · 2023-12-05 05:55 I understood that from your original post. You asked what to do. Figure out how to revoke it, wait the 90 days, or use a different name. ---------------------------------------------------------------------- NoNameJustASymbol · 2023-12-05 05:59 You may be able to have a new one issued to supersede the one you lost. ---------------------------------------------------------------------- highly_confusing · 2023-12-05 06:44 So do you have port 80 open, and do you have a firewall enabled like UFW? Also is the service that is attached to your domain listening on port 80? ---------------------------------------------------------------------- lilolalu · 2023-12-05 07:07 So can you access? http://mydomainnamehere/.well-known/acme- challenge/vS5u_wy5wNjthh9wrLKu5tOid7pn0SBbGmS_GjfaN0I That's what the certbot tries and fails, but you can try yourself. ---------------------------------------------------------------------- RedWyvv · 2023-12-05 07:26 Your domain is not accessible. Make sure that the DNS is set correctly and firewall is disabled. Try opening the URL in your browser and it should show something: [http://mydomainnamehere/.well-known/acme-challenge/vS5u\_wy5wNjthh9wr LKu5tOid7pn0SBbGmS\_GjfaN0I:](http://mydomainnamehere/.well- known/acme-challenge/vS5u_wy5wNjthh9wrLKu5tOid7pn0SBbGmS_GjfaN0I:) Since you're using AWS, you need to look into your security groups and ensure that incoming port 80 and 443 access is enabled. ---------------------------------------------------------------------- RedWyvv · 2023-12-05 07:27 In contrast to other comments, I don't believe that you need to revoke your Lets Encrypt. If there's such an issue, it will show up clearly on your screen. This is clearly an issue that your ports are not open. ---------------------------------------------------------------------- ferrybig · 2023-12-05 08:42 > MY QUESTION IS, how long before I am able to use certbot again on my new fresh instance for the domain name that I wanted? The old instance with the certification stuff is terminated and gone, so I have no way of reaching it and detaching / deleting the previous certifications... The rate limits are documented here: https://letsencrypt.org/docs/rate-limits/ Note that the staging environment has higher rate limits than the production environment, so use that if you want to test things and are not sure if your config is correct. Later switch to the production env if everything is okay