/.well-known/acme-challenge/xxxxx returns 404

RomainTT commented 3 years ago

Hello,

I would have avoided a new issue, but I'm desperate. Here is the deal:

My "Nginx Proxy Manager" is available from the outside (port 80 and 443 are forwarded from my router to the server). As proof, http://cloud.taprest.fr/ shows a custom page (that I wrote in the GUI of NPM).
But files in /.well-known/acme-challenge/ are not available. I created a file 1234 in /data/letsencrypt-acme-challenge/, and http://cloud.taprest.fr/.well-known/acme-challenge/1234 returns 404.
I checked /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf and it is correct (same as your sources).

For this reason, I am unable to create/renew certificates with Letsencrypt of course.

Do you have any idea of what could be wrong please?

Thank you for your work.

Edit: my setup is:

server is raspberry Pi
I am using docker-compose with latest tag

RomainTT commented 3 years ago

I have successfully created a new certificate using DNS method. Therefore the url above will lead to my Nextcloud Instance and my description is obsolete.

But the problem remains, and I can't use HTTP method.

KRSogaard commented 2 years ago

I am also having this issue, i have been debugging for hours but can't find the root cause. I can acces the site Nginx is proxying, but all requests to /.well-known/acme-challenge/ are met with a 404. I also tried created a file called hello in /data/letsencrypt-acme-challenge/ but i am not able to navigate to it from wget or a browser

ppittle commented 1 year ago

Did you ever get the Lets Encrypt http challenge working (ie able to hit /.well-known/acme-challenge/)?

jlesage / docker-nginx-proxy-manager

/.well-known/acme-challenge/xxxxx returns 404 #202