mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #63] Redirect Issue #60
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#60
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 @GeneralLuzi on GitHub (Feb 2, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/63
Hi,
the following szenario I would like to achive:
All of the following should point to the same URL https://www.subdomain.domain.tld:
1) Szenarios for Proxy Host:
1a) Szenario: https://www.subdomain.domain.tld --> create Reverse Proxy Host inkl. SSL
1b) Szenario: http://www.subdomain.domain.tld --> without ssl --> Update Reverse Proxy from 1a) to Force SSL
2) Szenario for Redirect Host
2a) Szenario: http://subdomain.domain.tld -->create Redirect Host (point to URL from 1a)
2b) Szenario: https://subdomain.domain.tld --> update Redirect Host from 2a) to SSL + Force SSL
Testing:
1a) works as specified
1b) works as specified
2a) does not work: url is redirected to https://http//subdomain.domain.tld
2b) does not work - like 2a)
If if I try to disable "Force SSL" within the Redirect Host but it does not save this new setting. (the same as specifed for http/2 in #61 --> perhaps there should be a new issue opened?!)
I deleted the Redirect Host from 2) and created the a new one with SSL settings, but without "Forced SSL". Same picture.
Can some verify my observation? Or do I missunderstand something how to use this manager?
Thanks a lot!
@GeneralLuzi commented on GitHub (Feb 2, 2019):
update:
the relevant conf within redirection_host folder has the following specified:
This might cause this issue!
If I delete the scheme "https://" within my redirect, all desired things work. Perhaps it will be good to specify this somewhere in the GUI for other noobs like me ;)
Alternatively: replace https:// or http:// if it is present.
@jc21 commented on GitHub (Feb 18, 2019):
Regarding the location
https://http//subdomain.domain.tld, I just tested myself and couldn't replicate this outcome.TL;DR for below: please try again with the latest docker image.
To simplify the setup required, you just want to
subdomain.domain.tldto destinationwww.subdomain.domain.tldwww.subdomain.domain.tldto upstream server.When it comes to redirecting and SSL, when the destination http server supports both HTTP and HTTPS connections (as a Proxy Host does), your Redirection Host doesn't need to Force SSL because you'll want to leave that determination up to the destination. However if the destination server only supported HTTPS then you'd want to force SSL before it even got to the destination.
A redirection host will forward to the destination on the same protocol scheme requested, and if force SSL is on then it will redirect to that first.
Btw, when I say that the server supports HTTP and HTTPS I mean from an open port point of view, not from a Proxy Host configured to forward both point of view.
@mackcoding commented on GitHub (Feb 23, 2019):
I am having this issue as well. I want to redirect to an https but I get https://http//url. The URL is an IP address that requires https.
@jc21 commented on GitHub (Feb 25, 2019):
I'm going to need to see the configuration for these hosts.
data/nginx/proxy_hostfolder and attach that here, changing the domain name for privacy@toupou commented on GitHub (Feb 12, 2021):
I still have the same issue. forwarding to another domain adds https//www.
happy to provide any config files if needed
@chaptergy commented on GitHub (May 10, 2021):
Shortly after your comment PR https://github.com/jc21/nginx-proxy-manager/pull/883 was merged. I'm assuming this fixed the issue. If it did not, let me know and I can reopen the issue.
@rockpham commented on GitHub (Jan 5, 2023):
I am also having this issue with redirection hosts. Attached are some screenshots, I hope that it's useful.
Please kindly help!
@Cruv commented on GitHub (Jan 30, 2023):
I know this is a zombie issue but I am also running into this with the same exact result as the poster above me.
@rockpham commented on GitHub (Feb 22, 2023):
I got the redirection host working by using 301, instead of 308
@Barina commented on GitHub (Jul 29, 2024):
Issue still persist in v2.11.3 using 308 still getting double https:// on a redirection host.
@BaconFist commented on GitHub (Oct 18, 2024):
I found a solution. It's not an Issue with nginx-proxy-manager.
The problem is, that a permanent redirect is cached a Webbrowser.
You can test it using curl and check the
Location:headercurl -D - YOUR_URLI recommend changing HTTP Code to 307 Temporary Redirect to prevent this.
@Chaxiraxi commented on GitHub (Oct 27, 2024):
As discussed in this issue, I think this is not possible with Nginx Proxy Manager. See this reddit post