[GH-ISSUE #2442] [URGENT] Can't add cert to nginx

kerem commented

2026-02-26 07:32:11 +03:00

Owner

Originally created by @engenharia-imediadata on GitHub (Dec 2, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2442

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

version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
container_name: 'nginx-proxy-manager'
restart: unless-stopped
network_mode: bridge
ports:
- '8880:80'
- '8881:81'
- '4443:443'
environment:
DISABLE_IPV6: "true"
volumes:
- /volume1/docker/nginx-proxy/data:/data
- /volume1/docker/nginx-proxy/letsencrypt:/etc/letsencrypt

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:

[11/9/2022] [12:47:29 PM] [SSL ] › ℹ info Testing http challenge for https://mydomain.xyz
Uncaught SyntaxError: Unexpected token < in JSON at position 5
FROM
./run: line 19: 406 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js
[11/9/2022] [12:47:31 PM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[11/9/2022] [12:47:32 PM] [Migrate ] › ℹ info Current database version: none
[11/9/2022] [12:47:33 PM] [Setup ] › ℹ info Logrotate Timer initialized
[11/9/2022] [12:47:33 PM] [Setup ] › ℹ info Logrotate completed.
[11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
[11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
[11/9/2022] [12:47:34 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
[11/9/2022] [12:47:34 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
[11/9/2022] [12:47:34 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[11/9/2022] [12:47:34 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
[11/9/2022] [12:47:34 PM] [Global ] › ℹ info Backend PID 434 listening on port 3000 ...
[11/9/2022] [12:47:35 PM] [Nginx ] › ℹ info Reloading Nginx
[11/9/2022] [12:47:35 PM] [SSL ] › ℹ info Renew Complete
QueryBuilder#allowEager method is deprecated. You should use allowGraph instead. allowEager method will be removed in 3.0
QueryBuilder#eager method is deprecated. You should use the withGraphFetched method instead. eager method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.

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?

Originally created by @engenharia-imediadata on GitHub (Dec 2, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2442 From reddit: [https://www.reddit.com/submit?source_id=t3_yqi9f4](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 >version: '3' services: app: image: 'jc21/nginx-proxy-manager:latest' container_name: 'nginx-proxy-manager' restart: unless-stopped network_mode: bridge ports: - '8880:80' - '8881:81' - '4443:443' environment: DISABLE_IPV6: "true" volumes: - /volume1/docker/nginx-proxy/data:/data - /volume1/docker/nginx-proxy/letsencrypt:/etc/letsencrypt 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: >[11/9/2022] [12:47:29 PM] [SSL ] › ℹ info Testing http challenge for https://mydomain.xyz Uncaught SyntaxError: Unexpected token < in JSON at position 5 FROM ./run: line 19: 406 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js [11/9/2022] [12:47:31 PM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [11/9/2022] [12:47:32 PM] [Migrate ] › ℹ info Current database version: none [11/9/2022] [12:47:33 PM] [Setup ] › ℹ info Logrotate Timer initialized [11/9/2022] [12:47:33 PM] [Setup ] › ℹ info Logrotate completed. [11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [11/9/2022] [12:47:33 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [11/9/2022] [12:47:34 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [11/9/2022] [12:47:34 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [11/9/2022] [12:47:34 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [11/9/2022] [12:47:34 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [11/9/2022] [12:47:34 PM] [Global ] › ℹ info Backend PID 434 listening on port 3000 ... [11/9/2022] [12:47:35 PM] [Nginx ] › ℹ info Reloading Nginx [11/9/2022] [12:47:35 PM] [SSL ] › ℹ info Renew Complete `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0. But when I go to [site24x7.com](https://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](https://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](https://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?

kerem added the

bug

label

2026-02-26 07:32:11 +03:00

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@tayfunyasar commented on GitHub (Dec 2, 2022):

I'm having same error.

@tayfunyasar commented on GitHub (Dec 2, 2022): I'm having same error.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@hicbka commented on GitHub (Dec 5, 2022):

same

@hicbka commented on GitHub (Dec 5, 2022): same

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@RadioactiveTapir commented on GitHub (Dec 5, 2022):

same here, getting:

Uncaught SyntaxError: Unexpected end of JSON input
FROM
./run: line 19: 746 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js

and

QueryBuilder#allowEagermethod is deprecated. You should useallowGraphinstead.allowEagermethod will be removed in 3.0QueryBuilder#eagermethod is deprecated. You should use thewithGraphFetchedmethod instead.eager method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0.

in the frontend, when i test the server reachability i get:

Communication with the API failed, is NPM running correctly?

@RadioactiveTapir commented on GitHub (Dec 5, 2022): same here, getting: > Uncaught SyntaxError: Unexpected end of JSON input > FROM > ./run: line 19: 746 Trace/breakpoint trap (core dumped) node --abort_on_uncaught_exception --max_old_space_size=250 index.js and > QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 > `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 > QueryBuilder#omit is deprecated. This method will be removed in version 3.0 > Model#$omit is deprected and will be removed in 3.0.` in the frontend, when i test the server reachability i get: > Communication with the API failed, is NPM running correctly?

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@JNR8 commented on GitHub (Dec 6, 2022):

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.

@JNR8 commented on GitHub (Dec 6, 2022): 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.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Luizzz4727 commented on GitHub (Dec 8, 2022):

Same problem here

@Luizzz4727 commented on GitHub (Dec 8, 2022): Same problem here

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Flawioo commented on GitHub (Dec 8, 2022):

+1
Same problem, it is something truly important.

@Flawioo commented on GitHub (Dec 8, 2022): +1 Same problem, it is something truly important.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Repullsor commented on GitHub (Dec 8, 2022):

Here is also the same.

@Repullsor commented on GitHub (Dec 8, 2022): Here is also the same.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@oleggtro commented on GitHub (Dec 17, 2022):

Hate to be the one, but +1.

This seems to be a duplicate of #2439 and #2011 tho

@oleggtro commented on GitHub (Dec 17, 2022): Hate to be the one, but +1. This seems to be a duplicate of #2439 and #2011 tho

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@jaredatron commented on GitHub (Jan 28, 2023):

+1 :(

@jaredatron commented on GitHub (Jan 28, 2023): +1 :(

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@andrewixl commented on GitHub (Jan 30, 2023):

Same here, all my certs are expired... whoops... hopefully this gets fixed asap

@andrewixl commented on GitHub (Jan 30, 2023): Same here, all my certs are expired... whoops... hopefully this gets fixed asap

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@woj-tek commented on GitHub (Jan 30, 2023):

@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 commented on GitHub (Jan 30, 2023): @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.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@andrewixl commented on GitHub (Jan 30, 2023):

@woj-tek Sadly, mind does not reach the point of creating the certificate as it crashes immediately after testing the connection.

@andrewixl commented on GitHub (Jan 30, 2023): @woj-tek Sadly, mind does not reach the point of creating the certificate as it crashes immediately after testing the connection.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@jaredatron commented on GitHub (Jan 31, 2023):

Can anyone recommend an older version that still works?

@jaredatron commented on GitHub (Jan 31, 2023): Can anyone recommend an older version that still works?

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@andrewixl commented on GitHub (Jan 31, 2023):

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:

Ensure npm is port forwarded to port 80 and 443.
Delete all certs in the SSL Cert page.
Go into the console and delete the /etc/letsencrypt folder and recreate the folder.
Now here is where it might not be a fix for everyone, I went into portainer and had it pull the latest image and recreate the container.
Then I logged back in attempted to create a certificate and it worked fine.

I did get an error on one subdomain mainly because that subdomain reached the limit for the day while troubleshooting.
Hope this helps.

@andrewixl commented on GitHub (Jan 31, 2023): 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: 1. Ensure npm is port forwarded to port 80 and 443. 2. Delete all certs in the SSL Cert page. 3. Go into the console and delete the /etc/letsencrypt folder and recreate the folder. 4. Now here is where it might not be a fix for everyone, I went into portainer and had it pull the latest image and recreate the container. 5. Then I logged back in attempted to create a certificate and it worked fine. I did get an error on one subdomain mainly because that subdomain reached the limit for the day while troubleshooting. Hope this helps.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@hereisderek commented on GitHub (Feb 3, 2023):

the line that seems to be causing the problem is
site24x7

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

curl --location --request POST 'https://www.site24x7.com/tools/restapi-tester' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Cookie: 70fdde380e=5d08cdd28ddbeee5f6b75e45e848a857; _zcsr_tmp=e2340209-680e-46b3-9d85-0aa7ead254de; s247cname=e2340209-680e-46b3-9d85-0aa7ead254de' \
--data-urlencode 'method=G' \
--data-urlencode 'url=http%3A%2F%2Fmedia02.derek-dev.top%2F.well-known%2Facme-challenge%2Ftest-challenge' \
--data-urlencode 'bodytype=T' \
--data-urlencode 'requestbody=' \
--data-urlencode 'headername=User-Agent' \
--data-urlencode 'headervalue=None' \
--data-urlencode 'locationid=1' \
--data-urlencode 'ch=false' \
--data-urlencode 'cc=false'

@hereisderek commented on GitHub (Feb 3, 2023): the line that seems to be causing the problem is [site24x7](https://github.com/NginxProxyManager/nginx-proxy-manager/blob/fd30cfe98bba365e9630a791bdc86f01c08c6fa1/backend/internal/certificate.js#L1169) 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 ``` curl --location --request POST 'https://www.site24x7.com/tools/restapi-tester' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --header 'Cookie: 70fdde380e=5d08cdd28ddbeee5f6b75e45e848a857; _zcsr_tmp=e2340209-680e-46b3-9d85-0aa7ead254de; s247cname=e2340209-680e-46b3-9d85-0aa7ead254de' \ --data-urlencode 'method=G' \ --data-urlencode 'url=http%3A%2F%2Fmedia02.derek-dev.top%2F.well-known%2Facme-challenge%2Ftest-challenge' \ --data-urlencode 'bodytype=T' \ --data-urlencode 'requestbody=' \ --data-urlencode 'headername=User-Agent' \ --data-urlencode 'headervalue=None' \ --data-urlencode 'locationid=1' \ --data-urlencode 'ch=false' \ --data-urlencode 'cc=false' ```

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@timnolte commented on GitHub (Feb 25, 2023):

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.

@timnolte commented on GitHub (Feb 25, 2023): 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.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@gehrtd commented on GitHub (Apr 1, 2023):

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:
1. Ensure npm is port forwarded to port 80 and 443.

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.
So this way it is impossible to make Port 80 and Port 443 from the docker container public available. Right?

@gehrtd commented on GitHub (Apr 1, 2023): > 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: > > 1. Ensure npm is port forwarded to port 80 and 443. 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.<mydomain>.com the proxy host redirects it to npm-app:81, where npm-app is the name of the docker container. So this way it is impossible to make Port 80 and Port 443 from the docker container public available. Right?

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@JNR8 commented on GitHub (Apr 1, 2023):

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

@JNR8 commented on GitHub (Apr 1, 2023): 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

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@tiagovaz commented on GitHub (Apr 22, 2023):

Same here, any news/fix? Thanks.

@tiagovaz commented on GitHub (Apr 22, 2023): Same here, any news/fix? Thanks.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@rodgers-95 commented on GitHub (Apr 23, 2023):

Hello,

Same problem here.

Does anyone have any information?

Thank you

Damien

@rodgers-95 commented on GitHub (Apr 23, 2023): Hello, Same problem here. Does anyone have any information? Thank you Damien

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Reaster0 commented on GitHub (Jul 8, 2023):

+1 i do have the same problem, impossible to generate nor renew ssl certificates using the webui

@Reaster0 commented on GitHub (Jul 8, 2023): +1 i do have the same problem, impossible to generate nor renew ssl certificates using the webui

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Zetto12 commented on GitHub (Jul 18, 2023):

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?

@Zetto12 commented on GitHub (Jul 18, 2023): 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?

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Dvalin21 commented on GitHub (Nov 18, 2023):

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.

@Dvalin21 commented on GitHub (Nov 18, 2023): > 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.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@broomwalker commented on GitHub (Jan 3, 2024):

Same issue - haven't been able to resolve this!

@broomwalker commented on GitHub (Jan 3, 2024): Same issue - haven't been able to resolve this!

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 1, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Aug 1, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@woj-tek commented on GitHub (Aug 1, 2024):

@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.

So I got notification about this issue... Even though renewal worked I switched a while back to Caddy as adding new entry for other docker services is just soooo simple and ItJustWorks

@woj-tek commented on GitHub (Aug 1, 2024): > @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. So I got notification about this issue... Even though renewal worked I switched a while back to Caddy as adding new entry for other docker services is just soooo simple and ItJustWorks

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@tp1050 commented on GitHub (Aug 19, 2024):

I am having this very issue,

@tp1050 commented on GitHub (Aug 19, 2024): I am having this very issue,

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Dvalin21 commented on GitHub (Aug 20, 2024):

I am having this very issue,

What version do you have?

@Dvalin21 commented on GitHub (Aug 20, 2024): > I am having this very issue, What version do you have?

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@audas commented on GitHub (Nov 27, 2024):

@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.

So I got notification about this issue... Even though renewal worked I switched a while back to Caddy as adding new entry for other docker services is just soooo simple and ItJustWorks

Not with subpaths.

@audas commented on GitHub (Nov 27, 2024): > > @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. > > So I got notification about this issue... Even though renewal worked I switched a while back to Caddy as adding new entry for other docker services is just soooo simple and ItJustWorks Not with subpaths.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Silicon51 commented on GitHub (May 21, 2025):

So, there's a chance that you have my case: both piHole and NPM as docker containers.
Due to some weird behavior of DNS resolver NPM container do not have access to internet so cannot request for cert.
For me it log errors like Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/cloudflare/
Also I have error Failed to check the reachability due to a communication error with site24x7.com nginx proxy when in version 2.12.3 I use option "Test Server Reachability" from tab SSL Certificates.
How to solve it?
add following to your NPM docker compose:

dns:
  - 172.19.0.4 <<pihole IP adress>>
  - 1.1.1.1
  - 8.8.8.8

@Silicon51 commented on GitHub (May 21, 2025): So, there's a chance that you have my case: both piHole and NPM as docker containers. Due to some weird behavior of DNS resolver NPM container do not have access to internet so cannot request for cert. For me it log errors like `Failed to establish a new connection: [Errno -3] Temporary failure in name resolution')': /simple/cloudflare/` Also I have error `Failed to check the reachability due to a communication error with site24x7.com nginx proxy` when in version 2.12.3 I use option "Test Server Reachability" from tab SSL Certificates. How to solve it? add following to your NPM docker compose: dns: - 172.19.0.4 <<pihole IP adress>> - 1.1.1.1 - 8.8.8.8

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@oleggtro commented on GitHub (May 22, 2025):

Hey, so I know this isn't really a fix, but after waiting for ages to get this fixed I moved my infra over to caddy (https://caddyserver.com/).
Everything now works like a breeze, memory and storage usage are minimal and automatic SSL validation finally works.

PS: sorry for this blatant ad, but this is probably the most convenient option for the majority of users

@oleggtro commented on GitHub (May 22, 2025): Hey, so I know this isn't really a fix, but after waiting for ages to get this fixed I moved my infra over to caddy (https://caddyserver.com/). Everything now works like a breeze, memory and storage usage are minimal and automatic SSL validation finally works. PS: sorry for this blatant ad, but this is probably the most convenient option for the majority of users

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@timnolte commented on GitHub (May 22, 2025):

Hey, so I know this isn't really a fix, but after waiting for ages to get this fixed I moved my infra over to caddy (https://caddyserver.com/).
Everything now works like a breeze, memory and storage usage are minimal and automatic SSL validation finally works.

PS: sorry for this blatant ad, but this is probably the most convenient option for the majority of users

@oleggtro thanks for sharing this. I might have to do this. Right now having to constantly babysit certificate renewal is becoming a real pain. Let's Encrypt is also now discontinuing sending out certificate expiration warning emails so this is just going to get worse. With there also being issues with the "auto" protocol handling NPM it is just becoming too much of a hassle.

@timnolte commented on GitHub (May 22, 2025): > Hey, so I know this isn't really a fix, but after waiting for ages to get this fixed I moved my infra over to caddy (https://caddyserver.com/). > Everything now works like a breeze, memory and storage usage are minimal and automatic SSL validation finally works. > > PS: sorry for this blatant ad, but this is probably the most convenient option for the majority of users @oleggtro thanks for sharing this. I might have to do this. Right now having to constantly babysit certificate renewal is becoming a real pain. Let's Encrypt is also now discontinuing sending out certificate expiration warning emails so this is just going to get worse. With there also being issues with the "auto" protocol handling NPM it is just becoming too much of a hassle.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 2, 2025):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Dec 2, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@abasworm commented on GitHub (Jan 29, 2026):

i have same issue, i use proxmox and docker.
when i ping to site24x7.com even with my laptop it's return request time out.

@abasworm commented on GitHub (Jan 29, 2026): i have same issue, i use proxmox and docker. when i ping to site24x7.com even with my laptop it's return request time out.

kerem commented

2026-02-26 07:32:12 +03:00

Author

Owner

@Silicon51 commented on GitHub (Feb 4, 2026):

i have same issue, i use proxmox and docker. when i ping to site24x7.com even with my laptop it's return request time out.

Didn't any solution from this topic helps?

@Silicon51 commented on GitHub (Feb 4, 2026): > i have same issue, i use proxmox and docker. when i ping to site24x7.com even with my laptop it's return request time out. Didn't any solution from this topic helps?

Rows
Columns

[GH-ISSUE #2442] [URGENT] Can't add cert to nginx #1715