Open PierreP94 opened 2 years ago
chaptergy
commented
2 years ago 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
2 years ago 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
2 years ago 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
2 years ago After weeks on it, It's still not working. I will try with other OS...
PierreP94
commented
2 years ago 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
1 year ago 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
1 year ago Hello,
I have abandoned this setup, sorry :)
Regards
Le mar. 20 juin 2023, 20:34, aj1322001 @.***> a écrit :
did you ever resolve this? im going through the same thing, its like the router grinds to a stop and no devices can get internet access at all... i changed the ip on my server because i could figure out what the issue was but now it seems as though it is NginX setup... been on this for a couple days and im fed up!
— Reply to this email directly, view it on GitHub https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1534#issuecomment-1599305886, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARHH2XXBN6OGIQEBDCDA5DDXMHUM5ANCNFSM5G5F675Q . You are receiving this because you authored the thread.Message ID: @.***>
github-actions[bot]
commented
4 months ago Issue is now considered stale. If you want to keep it open, please comment :+1:
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