-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No custom location possible! #3508
Comments
i have the same error as you in the picture. we definitely have the same problem. |
I am also facing this issue and done hello lot of googling, changing rule until i found this page. |
I also having the same error, some how the add_header cannot write to the conf file and it made the proxy stop. |
Running NPM on Unraid, ran into this problem on a fresh new install of the docker. Hosts were working fine on the old docker, but the same configuration under the custom location that previously worked immediately makes the proxy host go offline on the new one. |
The same problem is happening to me. |
I had a similar issue where teslamate-local.mydomain.com was working but teslamate-local.mydomain.com/grafana was showing a blank page that said "Not Found". #3512 (comment) is how I fixed it. |
Same issue with lasted version using portainer in Oracle Cloud |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
custom locations still don't seem seem to work for me on v.2.12.1 |
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
I cannot define a custom subpath. Today at noon everything still worked, but not anymore. I have reinstalled NPM, same error. What is the reason?
When I put it in like this, the entry goes offline. If I take it out, it works again. It seems to be a syntax problem. I can't explain it any other way
the npm container is in the same network as the apache2 container. [-> before it worked the same way. it also does not work if i replace "apache2" with the ip of the container]
Nginx Proxy Manager Version
v2.11.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The entry does not go offline
Screenshots
see above
Operating System
Debian with Docker
Additional context
no
The text was updated successfully, but these errors were encountered: