-
Notifications
You must be signed in to change notification settings - Fork 815
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
nginx_location.conf -> location /.well-known/acme-challenge/ always causing 404 for acme-challenge #138
Comments
This doesn't fix the problem for me. I edited the |
I've forked and fixed the packages required to get this working again, you need to swap out docker-gen for https://hub.docker.com/r/riid/docker-gen-multi/ and swap out docker-letsencrypt-nginx-proxy-companion for https://hub.docker.com/r/riid/docker-letsencrypt-nginx-proxy-companion-multi/ You can use all the previous settings, however I've also added the feature to watch multiple docker endpoints on the same host. |
@Rid Would not it be better if you tried to collaborate with the original project rather than create a "clone"? |
@thiagotalma I don't think the dev is currently active, I'm happy to make a PR if he's around, but judging by the lack of response he may be busy |
@Rid can you make a PR for this project ? |
Hello How to make the same PR here? Update : PR proposed |
I just playing with the example configuration, cloned this repo - https://github.com/fatk/docker-letsencrypt-nginx-proxy-companion-examples - and configured with a test url like 'dev.test.site.com'.
the acme challanges were always failed:
The problem was, nginx says HTTP 404
despite the challange file is exists:
I found, the problem is with the vhost.d/default.conf file:
after I change the location config for this:
Now the nginx able find the challenge files in /usr/share/nginx/html/.well-known/acme-challenge/ folder and the cert generating and verifying is going well
The text was updated successfully, but these errors were encountered: