![]() I have also checked that I reach the world from inside the container, and it resolves DNS queries. The sub domain is pointing to the Nginx public IP, just to have mentioned that as well. I have, just to try, opened ALL ports to the VM running the container just to make sure it is not a network issue. The other SSL-enabled proxy hosts are working perfect over port 443 and HTTPS. Ports open are 80 and 443, both NATed to the Nginx Proxy Manager. I have, though, pasted in the error log underneath.Īnd since Nginx have very limited ways/options when doing this, it isn't so much I can do different. ![]() 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. This is the error message I am getting while trying. How come, that I suddenly won't be able to set up a new SSL certificate ? I've been trying with and without an enabled vHost in Nginx. I am doing the exact same thing this fourth time, and I run into the same error log every single time. The strangest thing, is that I have successfully enabled SSL certificates on 3 proxy hosts without any concerns so far. 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).
0 Comments
Leave a Reply. |