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
[URGENT] Can't add cert to nginx #2442
Comments
I'm having same error. |
same |
same here, getting:
and
in the frontend, when i test the server reachability i get:
|
exactly the problem I have. I've got 14 days until a cert expires for one of my hosts, and I can't renew it. This error also has the added benefit of causing NPM to crash, needing a restart to get it back up and running. |
Same problem here |
+1 |
Here is also the same. |
+1 :( |
Same here, all my certs are expired... whoops... hopefully this gets fixed asap |
@andrewixl weird, while I can't test server reachability and there is an error shown while adding the certificate it's added and generated correctly. What's more, certificated are renewed correctly. |
@woj-tek Sadly, mind does not reach the point of creating the certificate as it crashes immediately after testing the connection. |
Can anyone recommend an older version that still works? |
Okay so I got it to work after some testing. As an FYI I use portainer to run the npm container. I followed these steps:
I did get an error on one subdomain mainly because that subdomain reached the limit for the day while troubleshooting. |
the line that seems to be causing the problem is and it was due to the site that was used for testing https://www.site24x7.com/tools/restapi-tester is having issue update: I might be wrong afterall, the aforementioned api does seem to be working
|
I too am having many of these same problems. I am able to request a new certificate but I can't successfully renew a certificate, additionally the testing of the server reachability is also broken. |
How can i do this? Npm is running as a docker container. NPM ist reachable as proxy host with Port 80 mapped to Port 81. So if i browse to npm..com the proxy host redirects it to npm-app:81, where npm-app is the name of the docker container. |
Opening ports 80 and 443 are the standard configuration for any NGINX server. This does not fix the issue at hand though. It still continues breaks in the same manor as I reported previously resulting |
Same here, any news/fix? Thanks. |
Hello, Same problem here. Does anyone have any information? Thank you Damien |
+1 i do have the same problem, impossible to generate nor renew ssl certificates using the webui |
I have the same issue. I was running Nginx as a Home Assistant Add-on and am now getting errors when I add or renew SSL certificates. I just setup an Nginx Proxmox LCX container which has exactly the same issue. Forwarded 80 and 443 to both IP's (the HA instance and the Nginx container) but always get an error. Is there anyone with a solution or an idea what might be causing this? |
I get the same thing, proxmox, lxc. Made sure to forward 80 and 443. |
Same issue - haven't been able to resolve this! |
From reddit:
https://www.reddit.com/submit?source_id=t3_yqi9f4
I get an error when I try to add a cert to nginx. When I test server reachability, I always get this error immidately: Communication with the API failed, is NPM running correctly?
I installed nginx with this docker-compose
There are no errors in the log when I start it up. I even rebuilt the container, same thing happens. When I do the test, the following lines are in the log:
But when I go to site24x7.com, and check my domain, it works fine. It shows the correct IP addresses from all countries. Using Cloudfare, un-proxied DNS. One "A" record that points to my IP address.
Finally, I have questions about what ports I should forward on my router. As I type this post, my current settings are forwarding both 80 and 443 to my NAS (192.168.0.2) on the same ports, 80 & 443. But to access my nginx admin panel, I go to 192.168.0.2:8881. I have tried forwarding incoming traffic on ports 80 and 443 to 8880, 8881, and 4443 (from the docker-compose), but I still get that same API failed error.
Could anyone help?
The text was updated successfully, but these errors were encountered: