Open TheZoker opened 4 years ago
Looks like the container is not able to reach the LetEncrypt server.
Can you try:
docker exec <container name> ping acme-v02.api.letsencrypt.org
Hmm yes, something does not seem right:
When I try the same with my AdGuard container it works:
AdGuard is running in host mode, while ProxyManager is running in bridge mode. But bridge mode should work as well, right?
Do you have any idea, how I can fix that?
And thank you very much for your help! Much appreciated
Edit:
In my AdGuard log I can see, that the request from the proxy manager was successful, but somehow the command still fails:
Are you using AdGuard as your DNS server ? If yes. this may be the cause of the issue.
Are you able to ping acme-v02.api.letsencrypt.org
from your Synology ?
Yes I'm using it as my DNS server.
Yes the ping from synology itself works:
Is this DNS server also used by you Synology? You can try to run the following command on your Synology: nslookup acme-v02.api.letsencrypt.org <DNS server IP>
.
Also, can you confirm that this DNS server used by the container:
docker exec <container name> cat /etc/resolv.conf
I am having the same internal error message. I use dnsimple and I do have a certificate on my account for my domain. Pinging the address you said above is successful.
If your container accessible from the internet on port 80 ? You can check with https://www.yougetsignal.com/tools/open-ports/
Same issue here. I am able to ping with:
docker exec
Make sure the container is reachable from the internet on port 80. You can check with https://www.yougetsignal.com/tools/open-ports/
Morning. Port shows as not reachable but both my router settings and the use of the proxy manager is present over port 80. If I use the IP:80 I go directly to where I set redirect to.
443 shows open and listening. Could I just direct through that? 80 is still working fine, It appears my isp blocks port 80, though I can go it via both directly through the IP and via my duckdns dyndns.
If your ISP blocks port 80, then I guess your cannot use Nginx Proxy Manager with automatic certificate generation from LetsEncrypt. Port 80 is required. This is how LetsEncrypt validates that your are the owner of the DNS name.
Odd given I can use port 80 for the hosts from Nginx Proxy Manager. I'll do some more research and report back on a fix for future reference.
I used the hassio addon for quite some time now. Today I tried to migrate the proxy manager to my synology. For that I use the synology docker manager and this docker image.
So I installed the latest version (1.7.0) and configured my port forwarding. The only issue I had was with the lets encrypt certificate. When I tried to request a certificate, I got an "Internal error":![Screenshot_2020 03 18_18h02m32s_006_](https://user-images.githubusercontent.com/1368405/76986957-ad089400-6942-11ea-81f0-4a0a41f719ee.png)
This is the content in the
/config/log/letsencrypt/letsencrypt.log
:Is this an issue with this image or with the base image or is my configuration wrong?
Is this issue related? https://github.com/jc21/nginx-proxy-manager/issues/180#issuecomment-599278001
Thank you!
Edit: A little bit more information: I also tried version 1.6.0, but it has the same issue. For both version: Connecting to my devices trough the manager using port 80 works fine. Connecting to them via 443 leads to a empty response.