starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #166] Strange Redirection issue on one network #145

New issue

Closed

opened 2026-02-26 06:30:45 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:30:45 +03:00

Owner

Originally created by @Veeau on GitHub (Jul 8, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/166

I have one strange redirection issue and it may be specific to the network I am on.

Current setup:
Proxy host - sub.domain.com > 192.168.1.249:8080

4g/other networks
Redirects to the guacamole correctly.

Work network
sub.domain.com > 192.168.1.249 on 80/443 depending if https used. and hits a broken page of the docker container on 80 or 443.

Replicated on IOS, Chrome, IE so I think it may be this network.

Edit:

Added a second host:
plex.domain2.com > 192.168.1.254:32400

when testing on work network same as above.

sub.domain.com > 192.168.1.249 on 80/443 depending if https used. and hits a broken page of the docker container on 80 or 443.
Long shot but any suggestions?

Originally created by @Veeau on GitHub (Jul 8, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/166 I have one strange redirection issue and it may be specific to the network I am on. Current setup: Proxy host - sub.domain.com > 192.168.1.249:8080 4g/other networks Redirects to the guacamole correctly. Work network sub.domain.com > 192.168.1.249 on 80/443 depending if https used. and hits a broken page of the docker container on 80 or 443. Replicated on IOS, Chrome, IE so I think it may be this network. Edit: Added a second host: plex.domain2.com > 192.168.1.254:32400 when testing on work network same as above. sub.domain.com > 192.168.1.249 on 80/443 depending if https used. and hits a broken page of the docker container on 80 or 443. Long shot but any suggestions?

kerem

2026-02-26 06:30:45 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@jc21 commented on GitHub (Jul 23, 2019):

So you're saying that you're trying to access sub.domain.com:80/443 and it is configured to send upstream to 192.168.1.249:8080 ?

sub.domain.com > 192.168.1.249 on 80/443 depending if https used

is that also sending upstream to 8080?

Personally, I don't have any issues connecting to NPM hosts either via http or https, with or without Squid proxy, Socks proxy or via a VPN. As long as the FQDN is part of public DNS you should be fine.

For some verbosity, you can look at the logs in your data mount and see if the hits are coming through the proxy host (proxy_host-*.log) or the default host (default.log)

@jc21 commented on GitHub (Jul 23, 2019): So you're saying that you're trying to access `sub.domain.com:80/443` and it is configured to send upstream to `192.168.1.249:8080` ? > sub.domain.com > 192.168.1.249 on 80/443 depending if https used is that also sending upstream to `8080`? Personally, I don't have any issues connecting to NPM hosts either via http or https, with or without Squid proxy, Socks proxy or via a VPN. As long as the FQDN is part of public DNS you should be fine. For some verbosity, you can look at the logs in your data mount and see if the hits are coming through the proxy host (proxy_host-*.log) or the default host (default.log)

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@chaptergy commented on GitHub (May 10, 2021):

Closing this, since there weren't any updates provided

@chaptergy commented on GitHub (May 10, 2021): Closing this, since there weren't any updates provided

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#145

No description provided.

Rows
Columns