[GH-ISSUE #1906] Not resolving on my android phone whilst doing it perfectly on desktop #1389

Open
opened 2026-02-26 07:30:46 +03:00 by kerem · 7 comments
Owner

Originally created by @zierbeek on GitHub (Mar 3, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1906

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

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:

  1. Setup a proxy host
  2. Set ip and port
  3. set ssl certificate
  4. save

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

Originally created by @zierbeek on GitHub (Mar 3, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1906 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> 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** <!-- What version of Nginx Proxy Manager is reported on the login page? --> V. 2.9.16 **To Reproduce** Steps to reproduce the behavior: 1. Setup a proxy host 2. Set ip and port 3. set ssl certificate 4. save **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> I can visit the website though it's subdomain and I can acces my service. **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Ubuntu 20.04 LTS vm **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
Author
Owner

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

<!-- gh-comment-id:1059331016 --> @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?
Author
Owner

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

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

<!-- gh-comment-id:1958514062 --> @github-actions[bot] commented on GitHub (Feb 22, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

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

<!-- gh-comment-id:2020345678 --> @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?
Author
Owner

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

<!-- gh-comment-id:2141564555 --> @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?
Author
Owner

@github-actions[bot] commented on GitHub (Nov 30, 2024):

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

<!-- gh-comment-id:2508787258 --> @github-actions[bot] commented on GitHub (Nov 30, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

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

<!-- gh-comment-id:2674622048 --> @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.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 13, 2025):

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

<!-- gh-comment-id:3395648358 --> @github-actions[bot] commented on GitHub (Oct 13, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
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#1389
No description provided.