mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1906] Not resolving on my android phone whilst doing it perfectly on desktop #1389
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#1389
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 @zierbeek on GitHub (Mar 3, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1906
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When I visit the service on my desktop though a subdomain with wildcard cert, I get the service. for example the service on port 192.168.1.10. When I visit this website on my android phone, I don't get the service but I get redirected to my main domain and the service that's at the 192.168.1.1 being adguard home login page
Nginx Proxy Manager Version
V. 2.9.16
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I can visit the website though it's subdomain and I can acces my service.
Operating System
Ubuntu 20.04 LTS vm
Additional context
@zierbeek commented on GitHub (Mar 4, 2022):
narrowed down the issue. Has to do with the http subdomain not redirecting to the https domain. how can this be solved that the http domain is invisible?
@github-actions[bot] commented on GitHub (Feb 22, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@jbmfg commented on GitHub (Mar 26, 2024):
I have this issue for some of my hosts as well. Is there anything needed to investigate further?
@StepanKuklis commented on GitHub (May 31, 2024):
Hello I know this is old, but Google let me here and I suppose my solution could help other people. Ive got similar issue to yours. It was routing/nat issue. I suggest you run tcpdump and trace the packets from host to host. I dont understand myself how this can lead to https->http confusion of the browser, I think this could be some error-recovery mechanism present on mobile devices?
@github-actions[bot] commented on GitHub (Nov 30, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@ultraqwertz commented on GitHub (Feb 21, 2025):
In my case, the router was set as the primary DNS server in WireGuard, which was supposed to forward DNS requests to the correct server - an AdGuard server with the proper rewrite rule for the (wildcard) domain of the reverse proxy ("*.example.com"). However, this didn't happen. Once I manually added the IP address of the correct DNS server, everything worked perfectly.
@github-actions[bot] commented on GitHub (Oct 13, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍