Closed romprod closed 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Up, I am a new user ( mailcow fan ), I have exactly the same problem
Fri Apr 9 07:30:03 CEST 2021 - Certificate /var/lib/acme/mail.jemail.be/cert.pem missing or changed domains 'mail.jemail.be' - start obtaining Fri Apr 9 07:30:03 CEST 2021 - Checking resolver... Fri Apr 9 07:30:03 CEST 2021 - Resolver OK Parsing account key... Parsing CSR... Found domains: mail.jemail.be Getting directory... Directory found! Registering account... Already registered! Creating new order... Order created! Verifying mail.jemail.be... Traceback (most recent call last): File "/usr/bin/acme-tiny", line 8, in
sys.exit(main()) File "/usr/lib/python3.8/site-packages/acme_tiny.py", line 194, in main signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca, disable_check=args.disable_check, directory_url=args.directory_url, contact=args.contact) File "/usr/lib/python3.8/site-packages/acme_tiny.py", line 149, in get_crt raise ValueError("Challenge did not pass for {0}: {1}".format(domain, authorization)) ValueError: Challenge did not pass for mail.jemail.be: {'identifier': {'type': 'dns', 'value': 'mail.jemail.be'}, 'status': 'invalid', 'expires': '2021-04-16T05:30:07Z', 'challenges': [{'type': 'http-01', 'status': 'invalid', 'error': {'type': 'urn:ietf:params:acme:error:unauthorized', 'detail': 'Invalid response from http://mail.jemail.be/.well-known/acme-challenge/0yWIOTyMlkcuyAanSDOo40XeiXqOG3iB8n53_NfFLs8 [xxxx]: "\r\n 404 Not Found \r\n\r\n\r\n 404 Not Found
openresty</cente"', 'status': 403}, 'url': 'https://acme-v02.api.letsencrypt.org/acme/chall-v3/12197037820/7J7iFA', 'token': '0yWIOTyMlkcuyAanSDOo40XeiXqOG3iB8n53_NfFLs8', 'validationRecord': [{'url': 'http://mail.jemail.be/.well-known/acme-challenge/0yWIOTyMlkcuyAanSDOo40XeiXqOG3iB8n53_NfFLs8', 'hostname': 'mail.jemail.be', 'port': '80', 'addressesResolved': ['xxxx'], 'addressUsed': 'xxxx'}], 'validated': '2021-04-09T05:30:09Z'}]} Fri Apr 9 07:30:11 CEST 2021 - Failed to obtain certificate /var/lib/acme/mail.jemail.be/cert.pem for domains 'mail.jemail.be' OK Fri Apr 9 07:30:11 CEST 2021 - Some errors occurred, retrying in 30 minutes...
Hi, you have an openresty server in front of your mailcow that's not configured correctly. And also not supported by us. It can absolutely work, but we don't provide example configs.
Can I still ask you a question? ( 2 ;) ) Maybe the reason is i've location / { redirect } to forward my client directly to SOGo ?
On Friday, April 09, 2021 07:58 CEST, André Peters @.***> wrote: Hi, you have an openresty server in front of your mailcow that's not configured correctly. And also not supported by us. It can absolutely work, but we don't provide example configs. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
I would love to help, but I have no glue. Isn't it basically Nginx? Excuse my ignorance. :-)
Prior to placing the issue, please check following: (fill out each checkbox with a
X
once done)Description of the bug: What kind of issue have you exactly come across?
Unable to complete cert request which then loops after 30 minutes
Reproduction of said bug: How exactly do you reproduce the bug?
System information
I've tried each of the following settings but the HTTP validation always fails.
Further information (where applicable):
docker version
)docker-compose version
)I've changed the domain name and IP address of the above log
Traefik v2.0.1 is set to redirect http to https.
When I goto http://autoconfig.fred.it/.well-known/acme-challenge/ejG-wVfy85jMG_do9Y-JVMin2oJT_nsP7Jybc-2P0IE it redirects to https://autoconfig.fred.it/.well-known/acme-challenge/ejG-wVfy85jMG_do9Y-JVMin2oJT_nsP7Jybc-2P0IE and I can see the file correctly.
I understand the HTTP challenge is ok being redirected to HTTPS as per https://letsencrypt.org/docs/challenge-types/
This maybe the same issue as #2748 but I've checked the Nginx config and I don't have the extra section which has been fixed here #2736
I'm running the latest Mailcow version, which has just been updated this morning using the update script.