Trailing / custom location issue.

[CyaOnDaNet]

I have been using this nginx proxy manager for about 8 months and haven't made any critical changes in at least 3 months. I am unsure if this issue applies to any specific version as I don't think the circumstance that revealed this ever arose till today.

I am running the docker with the latest tag and its currently up to date. My router port forwards incoming 80 to host 1780 and incoming port 443 to host 17443. My docker port mappings are: -p '7818:8181/tcp' -p '1780:8080/tcp' -p '17443:4443/tcp'

I have a site (let's call it example.com) with force SSL enabled and it has custom locations. When you go to https://example.com it works. When you go to https://example.com/custom_location_1 or https://example.com/custom_location_2 it works no problem. When you go to http://example.com it correctly bumps it up to https://example.com. The problem arises when I try to go to http://example.com/custom_location_1. It incorrectly directs you to https://example.com:4443/custom_location_1. This happens on google chrome on windows and safari on iOS. For some reason, when it forces SSL on the custom location, the internal docker port gets added to the URL. Typically, I only use https links and I don't have very many custom locations so I never noticed the issue before. I'm not sure if its something as simple as adding a line of code to the custom configuration box, an oversight on my part, or something else entirely.

Let me know if you there is any more information I can provide to help diagnose where the issue lies. Thanks for the help.

[jlesage]

Hi and sorry for the delay. Could you provide the generated nginx config for this proxy host ?

[CyaOnDaNet]

9.conf.txt I redacted the external URL and internal IP's and ports. After some more testing, it does not appear to be an issue with forcing SSL like I originally thought but rather the lack of the trailing / in the URL. In my conf you will see a /synclounge and /newsletter location. If I go to either http://website.com/synclounge or https://website.com/synclounge it results in a faulty redirect of https://website.com:4443/synclounge/ . This is reproducible every time in Firefox for both /synclounge and /newsletter. Perhaps this is a misconfiguration on my end?