mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1534] DNS probe error #1166
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1166
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PierreP94 on GitHub (Oct 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1534
Describe the bug
I am using last NPM version on Raspberry Pi official OS
I keep getting on every redirection (even on NPM itself)
DNS_PROBE_POSSIBLE
Containers are able to communicate. Everything has access to internet and all nslookup are working.
I believe that there is a bug since I don't see any possible solution (or problem :))
Regards
@chaptergy commented on GitHub (Oct 31, 2021):
Does this only happen for npm proxied pages? And does 'on every redirect' mean that the proxied pages are not available at all or only when a http redirect is sent? Or something else entirely?
When searching the web for this error it comes up with lots of results where the issue seems to be the router, especially if some form of wrt was installed. Have you checked whether that could be the issue?
@PierreP94 commented on GitHub (Nov 1, 2021):
Whatever I'm redirectig to, I'm getting DNS Probe error (even redirecting on google.com). I can still access to container with http:://localhost:port_of_container.
It's an ISP Router (Bouygues). I have found out that it's impossible to modify the DNS on the router but I have used dnsmasq to try to solve this issue without success.
@PierreP94 commented on GitHub (Nov 1, 2021):
Maybe the solution may come from DNSmask. I have tried different configuration and the result is now a bit different (it's going to the error without waiting), but I'm still not mastering this tool.
@PierreP94 commented on GitHub (Nov 24, 2021):
After weeks on it, It's still not working. I will try with other OS...
@PierreP94 commented on GitHub (Dec 19, 2021):
Keep getting same error on all OS....
I till have from inside the container npm ;
$ nslookup portainer
Server: 127.0.0.11
Address: 127.0.0.11#53
Non-authoritative answer:
Name: portainer
Address: 172.19.0.5
So I have no idea what is going wrong....
Some help would be great
@aj1322001 commented on GitHub (Jun 20, 2023):
Did you ever resolve this? I'm going through the same problem, its like the router grinds to a stop and no device can get internet access whatsoever... I changed the ip of my ubuntu server because I couldn't figure out what the cause was, however it seems as though it is NginX thats the root problem here... I've been on this for a couple days and I'm fed up!
@PierreP94 commented on GitHub (Jun 20, 2023):
Hello,
I have abandoned this setup, sorry :)
Regards
Le mar. 20 juin 2023, 20:34, aj1322001 @.***> a écrit :
@github-actions[bot] commented on GitHub (Mar 2, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 15, 2025):
Issue was closed due to inactivity.