Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always challenge failed #130

Open
DiogoAbdalla opened this issue Sep 21, 2022 · 3 comments
Open

Always challenge failed #130

DiogoAbdalla opened this issue Sep 21, 2022 · 3 comments

Comments

@DiogoAbdalla
Copy link

Hey.

First of all, thank you for this. Ive been using for a while this little personal project.

That said, it stopped working here. It always gives me "Challenge failed" now

I tried a fresh clone from this repo, just changed the domain and ran and the result is the same:

http-01 challenge for mydomain.app
Using the webroot path /var/www/certbot for all unmatched domains.
Waiting for verification...
Challenge failed for domain mydomain.app
http-01 challenge for mydomain.app
Cleaning up challenges
Some challenges have failed.

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

   Domain: mydomain.app
   Type:   connection
   Detail: xxx.xxx.xxx.xx: Fetching
   http://mydomain.app/.well-known/acme-challenge/8IDnt4bKrZWPH9vz7duJR-XyTpEWLHGhbNXCmr2bm6U:
   Connection refused

   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. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.

Im fairly sure the domain is correctly configured, as this used to work and I didint change anything

Do you have any idea why this is happening? Any tips would be really appreciated

@belmarca
Copy link

belmarca commented Feb 3, 2023

I have the same error.

@belmarca
Copy link

belmarca commented Feb 3, 2023

It sometimes 404's, sometimes Connection refused, with the same configuration. I can easily serve traffic with just my docker-compose on port 80. I will have to investigate later.

@git-clone-abhinav
Copy link

Any leads on this guys ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants