Nginx-proxy-manager: "Bad Gateway" at Login Page after Upgrading to 2.7.0

[Vocta1310]

Hi, I can't login anymore in configuration Panel after Upgrading to 2.7.0.
Before the Upgrade everything works great.

What can I do to fix this issue?

[jmeinicke]

my solution was to add the database env to my compose file and remove the config.json config file from mount into container

https://nginxproxymanager.com/setup/

[Havoc85]

Having the exact same Problem.

I'm using SQLite. Are there anywhere examples what database environment variables I have to add to my compose file and what removing the config.json fiel from mount into container means?

[Vocta1310]

Fixed with 2.7.1 - Thank You @jc21

[Havoc85]

Fixed also on my side with 2.7.1 :-). Thank you @jc21 .

[2Ben]

Seems not fixed for me on 2.7.1. I just did a docker pull to upgrade, should I do something else?
Edit: sorry it is actually fixed. Thanks @jc21 !

[stavros-k]

Does the container auto updates? I pulled new image, restarted the container but i'm still on 2.6.2

[Vocta1310]

@stavros-k - have you cleared your Browser Cache? Maybe that wrong information is stored in the cache ;)

[stavros-k]

@stavros-k - have you cleared your Browser Cache? Maybe that wrong information is stored in the cache ;)

Didn't think of that. But i just tried from incognito and still says 2.6.2

[Havoc85]

Didn't think of that. But i just tried from incognito and still says 2.6.2

I don't know if that was the question, but here a little insight of what I'm doing to update the nginx-proxy-manager docker container:

docker pull jc21/nginx-proxy-manager:latest
docker stop <id or name>
docker-compose up -d

Afterwards you can remove (all) old images with docker image prune -f

That's it. At least, if you're using docker-compose and if you're using "image: jc21/nginx-proxy-manager:latest" in it.

Hopefully that helps.

[stavros-k]

Didn't think of that. But i just tried from incognito and still says 2.6.2

I don't know if that was the question, but here a little insight of what I'm doing to update the nginx-proxy-manager docker container:

docker pull jc21/nginx-proxy-manager:latest
docker stop <id or name>
docker-compose up -d

Afterwards you can remove (all) old images with docker image prune -f

That's it. At least, if you're using docker-compose and if you're using "image: jc21/nginx-proxy-manager:latest" in it.

Hopefully that helps.

I'm on Unraid, so most of it its through GUI, but
i removed the docker (its like docker rm)
i did docker imager prune
re"installed" docker (its like docker run) (as repository i have jc21/nginx-proxy-manager but on docker run it says its pulling from :latest)
It didn't find available image so it pulled ALL layers from scratch.

On WebGUI it still says 2.6.2. Is there some way to check from console?
Maybe something in my config isn't compatible with 2.7.1 yet and this keeps it from upgrading?

Just made a new container on different ports and new config mapping, still 2.6.2.
I should probably start new issue , because i don't really have something that doesn't work, and its not relevant with this topic.

[MGoeppl]

2.7.1 works again for me ;)

[jc21]

It's very strange that the UI would report a different version than the one running in your docker instance. Perhaps hit the API directly with a command like this:

curl http://yournpmhost:81/api

and see what the version number being reported is. If it's not the one you're expecting then you definitely have the wrong image running. If it's different to the UI, then maybe the browser is aggressively caching however there is code in the frontend to reload the page if the backend version is different than the one the UI was expecting.

If you are using NPM to proxy the NPM admin site itself (as most of us do) you will want to make sure the Cache Assets option is not selected.

[stavros-k]

It's very strange that the UI would report a different version than the one running in your docker instance. Perhaps hit the API directly with a command like this:

curl http://yournpmhost:81/api

and see what the version number being reported is. If it's not the one you're expecting then you definitely have the wrong image running. If it's different to the UI, then maybe the browser is aggressively caching however there is code in the frontend to reload the page if the backend version is different than the one the UI was expecting.

If you are using NPM to proxy the NPM admin site itself (as most of us do) you will want to make sure the Cache Assets option is not selected.

Ok, now i feel very stupid -.- I'm on Unraid and i'm using the templates there. which is a different image "jlesage/nginx-proxy-manager" i was seeing the "j" in the start and the "nginx-proxy-manager" after and i was like "yea this is ok"
I'll have either to wait until this image is updated, or try to convert your docker-compose to plain docker, or install portainer
Unraid doesn't support docker-compose natively,

[LivingWithHippos]

I had this issue after moving the variables to the compose file and removing config.json.
As jmeinicke said the solution was removing from the docker compose the line mounting the file

    volumes:
      - ./config.json:/app/config/production.json

[mwip]

I can confirm that is is still an issue with 2.7.1.

Rocking a Raspberry pi and just did a

sudo docker-compose down
sudo docker-compose pull
sudo docker-compose up -d

The proxy works just fine, but I cannot log in.