Adding a Custom Location to a proxy host takes it offline

[jricardooliveira]

Are you in the right place?

• Yes

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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

• I installed NPM from docker hub latest. I add a proxy host to forward traffic to a host on my network on port 8080. It works ok. I managed also to add a Letencrypt SSL certificate without any issue. I can reach my site with the domain name.
• If I try to add a custom location for instance for /myapp and point it to another IP on same network as previous and port 9090 it takes proxy host offline after saving

Nginx Proxy Manager Version
v2.11.1

This appears to have happened in the past. #929

Joao

[lug-gh]

#3512

[sueess86]

I am facing the same issue

[engkad]

Had the same issue, posted on reddit about it and using version 2.10.4 fixes it.

[gitwildnow]

I have the same problem with anything after v2.10.4. Running docker in a Ubuntu 20.04.6 VM. A custom location can't be saved regardless of how trivial it is. Revert to 2.10.4 and it works.

[AkshayRao27]

Please see if #3512 (comment) fixes the issue for you.

[fabiofrances]

I have same problem using version 2.11.1
error:
nginx: [emerg] "map" directive is not allowed here in /data/nginx/proxy_host/24.conf:53
nginx: configuration file /etc/nginx/nginx.conf test file

[gitwildnow]

Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline.

[AkshayRao27]

Fixed problem by pulling jc21/nginx-proxy-manager:github-pr-3478. I can add/edit/save locations now without taking the host offline.

How does one pull a specifc PR? My solution was to essentially do exactly this, but manually inside my install by navigating to, and editing that file. I didn't know that it was possible to deploy a specific PR ^^

[gitwildnow]

I edited my config.yml to include:
image: 'jc21/nginx-proxy-manager:github-pr-3478'
You can also pull directly with docker as in:
docker pull jc21/nginx-proxy-manager:github-pr-3478

[shanelord01]

I edited my config.yml to include: image: 'jc21/nginx-proxy-manager:github-pr-3478' You can also pull directly with docker as in: docker pull jc21/nginx-proxy-manager:github-pr-3478

I did this also but it bricked my config. I recommend others backup their /config and /etc/letsencrypt volumes before trying this so you can recover if things go wrong.

All working now though with the PR change in use.

[NazgulCoder]

this is insane. I'm facing the same issue, I'm not going to pull nginx-proxy-manager:github-pr-3478, i'll use custom configuration instead

[gitwildnow]

What do you mean by "custom configuration"? fwiw I'm still using github-pr-3478, waiting for NPM to release something newer than the January release that does not have this fixed merge in. Apparently the merge has been done but there's no new NPM yet.

[bibstha]

If you don't want to use the custom pr branch for security reasons, you can also use docker.io/jc21/nginx-proxy-manager:github-develop image

[tue-kyndal]

I have been struggling with custom locations for hours...what is going on whit this issue.
I don't what to brink my nginx..so ill wait for for a new release. Any news on this?

[dudefoxlive]

Has this been fixed in the latest update?

[gitwildnow]

Downloaded the new 2.11.2 release and now I can add/edit custom locations again.