I am running newst stable versjon of Nginx Proxy Manager, in Docker on Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-110-generic x86_64).
The strangest thing, is that I have successfully enabled SSL certificates on 3 proxy hosts without any concerns so far. I am doing the exact same thing this fourth time, and I run into the same error log every single time. I've been trying with and without an enabled vHost in Nginx.
How come, that I suddenly won't be able to set up a new SSL certificate ?
This is the error message I am getting while trying. Since I am not using CLI/the job is fully automated by Nginx through the GUI, I cannot state what CLI parameters I am using. I have, though, pasted in the error log underneath.
And since Nginx have very limited ways/options when doing this, it isn't so much I can do different.
Ports open are 80 and 443, both NATed to the Nginx Proxy Manager. The other SSL-enabled proxy hosts are working perfect over port 443 and HTTPS.
I have, just to try, opened ALL ports to the VM running the container just to make sure it is not a network issue. This didn't change anything, of course. The sub domain is pointing to the Nginx public IP, just to have mentioned that as well.
I have also checked that I reach the world from inside the container, and it resolves DNS queries. I can see of the error log that something times out. I tried to ping, and it answers:
[root@docker-b0f8a23e65bf:/app]# ping letsencrypt.org
PING letsencrypt.org (18.192.76.182) 56(84) bytes of data.
64 bytes from ec2-18-192-76-182.eu-central-1.compute.amazonaws.com (18.192.76.182): icmp_seq=1 ttl=50 time=6.46 ms
64 bytes from ec2-18-192-76-182.eu-central-1.compute.amazonaws.com (18.192.76.182): icmp_seq=2 ttl=50 time=6.50 ms
64 bytes from ec2-18-192-76-182.eu-central-1.compute.amazonaws.com (18.192.76.182): icmp_seq=3 ttl=50 time=6.93 ms
^C
--- letsencrypt.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 4ms
rtt min/avg/max/mdev = 6.462/6.631/6.929/0.221 ms
[root@docker-b0f8a23e65bf:/app]#
Error log:
Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-26" --agree-tos --authenticator webroot --email "anders@buksa.org" --preferred-challenges "dns,http" --domains "emby.buksa.org"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by ConnectTimeoutError(, 'Connection to acme-v02.api.letsencrypt.org timed out. (connect timeout=45)'))
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
Have scratched my head over this for 2 weeks without having a single idea of what is going on here.
I did a lot of googling, and I came by another post with the same errors, and there it was said that it was too many failed faults within the hour. But I cannot see that this is the same problem.
Thanks for any help here.
