NginxProxyManager / NginxProxyManager/nginx-proxy-manager
custom location causes ERR_TOO_MANY_REDIRECTS
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Issue:
using a custom location introduces a ERR_TOO_MANY_REDIRECTS error on my application (which works fine if I use the main forward host without location).
Context (optional):
- Trilium web server docker image
- Nginx proxy manager forwards to the docker container name "trilium" over HTTP
- There is no HTTPS involved whatsoever in my current setup
- All advanced configs in NPM are empty
- The custom location and main location settings in NPM for trilium are identical
- The custom location for "dummy-docker" is working just fine
- connecting Trilium to
192.168.1.52works - connecting Trilium to
192.168.1.52/triliumdoes not work
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker 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
Nginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
Screenshots
Operating System
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reproducing the difference between the main host and the /trilium custom location using the stated Docker and Nginx Proxy Manager setup, then compare the resulting behavior and available proxy details. Done means the custom location loads without ERR_TOO_MANY_REDIRECTS and the cause is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100