-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
JSON-Error in Backend while generating SSL-Certificates #2796
Comments
smells like #2713 |
I seemingly have the exact same issue with a completely vanilla and by-the-books default install. Docker hello-world test works, NPM administration panel works, DNS domain works (can reach the Apache2 Ubuntu Default Page), but for the life of me I cannot get Test Server Reachability to work when trying to get an SSL certificate. Please help |
Lost cause |
How do you mean? Is NPM practically abandoned? |
idk what seems to be the problem, but the newer version of nginxproxymanager seems to throw this error, while older ( the one im running in my lab v2.9.18) seems to work fine. EDIT: Oh well.. just tested and yes, its not working on my end anymore :( |
I see... and you thought it might have to do with #2713 ? |
I just tried the following: Was reading up on #2011 and #3121, the first one helped, havent treid the new PR docker image that is the second one. |
that just yields an |
maybe youre on later veresions, than what i am right now, thats why its throwing you something else. might be worth looking into using caddy im not associated with caddy but seems pretty hassle free. only downside - no frontend :( |
I am on the version that was installed automatically by copy-pasting the docker-compose.yml text from the site today. |
2.10.4 |
I have the same issue. But it only does this for one of my domains, not all of them. When I try to test the server reachability I get another error And this error on the UI |
Thanks for this! Same error for me as everyone else from the "SSL tab" but from the Hosts tab> ssl tab> request new... |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
I am unable to create an SSL certificate for my websites. The API simply returns a 502-Error after a while, showing the message "Communication with the API failed, is NPM running correctly?".
In the Docker-Logs I can see that it fails with the following:
If I try a subdomain it fails with another JSON-Error:
I am using the following Compose within a Portainer-Stack:
I have no idea whats going on, especially because I haven't seen someone have this error before. Everything else works perfectly fine, just anything concerning SSL-Certs is not working. I've also tried previous versions, which result in the same error.
Nginx Proxy Manager Version
2.10.2 (and previous ones)
The text was updated successfully, but these errors were encountered: