starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #2266] Test Server Reachability Details? #1617

New issue

Closed

opened 2026-02-26 07:31:47 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:31:47 +03:00

Owner

Originally created by @shanelord01 on GitHub (Sep 15, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2266

Hi - wondering if you could share details on how "Test Server Reachability" under SSL works?

I'd like to setup geo blocks on my firewall, but I'd like to allow this test through to ensure cert renewal works. Are there IP addresses I can whitelist?

Originally created by @shanelord01 on GitHub (Sep 15, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2266 Hi - wondering if you could share details on how "Test Server Reachability" under SSL works? I'd like to setup geo blocks on my firewall, but I'd like to allow this test through to ensure cert renewal works. Are there IP addresses I can whitelist?

kerem

2026-02-26 07:31:47 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@the1ts commented on GitHub (Sep 16, 2022):

Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https.
The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like.

@the1ts commented on GitHub (Sep 16, 2022): Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https. The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@shanelord01 commented on GitHub (Sep 16, 2022):

Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https. The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like.

Thanks. Unfortunately my domain is currently on Google Domains (not cloud) so no DNS Auth method.

@shanelord01 commented on GitHub (Sep 16, 2022): > Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https. The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like. Thanks. Unfortunately my domain is currently on Google Domains (not cloud) so no DNS Auth method.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@the1ts commented on GitHub (Sep 16, 2022):

@shanelord01 you can use cloudflare for DNS (cloudflare talk you through the process of changing NS records) and still use google domains to handle the domain registration side. Its what I do for a .app domain which is only available to register from google. Then you get the best of both worlds.

@the1ts commented on GitHub (Sep 16, 2022): @shanelord01 you can use cloudflare for DNS (cloudflare talk you through the process of changing NS records) and still use google domains to handle the domain registration side. Its what I do for a .app domain which is only available to register from google. Then you get the best of both worlds.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@shanelord01 commented on GitHub (Nov 16, 2022):

Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https.

The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like.

Thank you.

I unfortunately can't use DNS01 for my domains at the moment as domains.google.com doesn't support it and I will not use Cloudflare for personal reasons.

I have some hosts on Linode so I could use their DNS, but they still don't support DNSSEC.

I'll just manually toggle the geoblock off and on again at every renewal for now.

@shanelord01 commented on GitHub (Nov 16, 2022): > Companies and orgs don't like to give this information out as it can often change outside of their control, in some cloud providers for example. As to how it works, letsencrypt reach out to a specially formed url on http not https. > > The way around this is to use the DNS authentication method, that means your endpoints aren't hit by letsencrypt at all so can remain hidden as much as you need/want/like. Thank you. I unfortunately can't use DNS01 for my domains at the moment as domains.google.com doesn't support it and I will not use Cloudflare for personal reasons. I have some hosts on Linode so I could use their DNS, but they still don't support DNSSEC. I'll just manually toggle the geoblock off and on again at every renewal for now.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 9, 2024):

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

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

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 26, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 26, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1617

No description provided.

Rows
Columns