How to reset the login password

[chaptergy]

If you have forgotten your password and need to reset it here is how you do it. This depends on what database you are using. If you have two docker containers one of which is a database, you are using MySQL, if you just have the single npm docker container, you probably use the SQLite database. Since November of 2021, the example docker-compose file is using SQLite, prior to that is was MySQL.

SQLite (default since November 2021)

Step 1

Run these commands on the machine running the docker container containing the database but replacing <container-name> with the name of the docker container containing your npm instance (It will most likely be something like nginxproxymanager_core):

docker exec -it <container-name> sh
apt update && apt install sqlite3 -y
sqlite3 /data/database.sqlite

You have now entered the SQL mode, where you set the status of all users to deleted:

UPDATE user SET is_deleted=1;
.exit
exit

Step 2

If your NPM container has been running, restart it. If it has not been running, start it now.

Step 3

You have now created an admin user you can login with by accessing your NPM in the browser and logging in with the default login information:
login: admin@example.com
pass: changeme

Step 4

You can now either just use this user, or you can re-enable the old account and use the new account to change the password of the old one. To re-enable it, once again execute the following commands:

docker exec -it <container-name> sh
sqlite3 /data/database.sqlite

Replace <container-name> again, as in step 1. Then set all users to not deleted by running:

UPDATE user SET is_deleted=0;
.exit
exit

MySQL (default prior to November 2021)

Step 1

Run these commands on the machine running the docker container containing the database but replacing <container-name> with the name of the docker container containing your database (It will most likely be something like nginxproxymanager_db_1):

docker exec -it <container-name> sh
mysql -u root -p

You will have to enter the root password of your database. You have set it in your docker-compose file through the MYSQL_ROOT_PASSWORD variable. Then continue entering the following commands:

USE npm;
UPDATE user SET is_deleted=1;
quit
exit

Step 2

If your NPM container has been running, restart it. If it has not been running, start it now.

Step 3

You have now created an admin user you can login with by accessing your NPM in the browser and logging in with the default login information:
login: admin@example.com
pass: changeme

Step 4

You can now either just use this user, or you can re-enable the old account and use the new account to change the password of the old one. To re-enable all previously disabled users, once again execute the following commands:

docker exec -it <container-name> sh
mysql -u root -p

Replace <container-name> and enter the root password again, as in step 1.

USE npm;
UPDATE user SET is_deleted=0;
quit
exit

^{Based on comment by talesam}

[telometto]

A lifesaver!

[stealthdave]

I was able to use this to get access to Nginx Proxy Manager, but when I logged in, none of my existing proxies showed up. After a little investigation, I discovered that this is because we are creating a second user and all of the proxies were owned by the first user. Luckily, there is an easy fix which is updating the own_user_id to the new user, which in my case was 2, for the host and stream tables. Assuming your new user id is 2, run the following SQL statements.

UPDATE dead_host SET owner_user_id=2;
UPDATE proxy_host SET owner_user_id=2;
UPDATE redirection_host SET owner_user_id=2;
UPDATE stream SET owner_user_id=2;

This will update the tables to be owned by the new user.

[GregoryRudinsky]

Thanks for adding this comment. Should I be concerned about a weird message when accessing SSL CERTIFICATES:

Cannot read properties of null (reading 'avatar')

[littlewhitefox]

you can try

UPDATE certificate SET owner_user_id=2;

[tiagojulianoferreira]

Just collaborating with the thread, I retrieved the ACLs for the new account using:

UPDATE access_list SET owner_user_id=2;

[sirjmann92]

Lifesaver! Freaked out when I logged in and saw all of my stuff missing with the avatar error. I had deleted the original user so I could re-use the credentials so I was worried it would be unrecoverable. Glad I was wrong. Thanks for the help!

[alekshnl]

Alternatively you can use the admin@example.com account to reset the password in the users section. After completion don't forget to delete the admin@example.com account again.

[TK-3375]

When I reach step 3 it says that there is no "relevant user found" when I try to login (either with my useraccount, or the default one). Ideas ?

[RubenSibon]

Have you really restarted the docker container? I.e.: docker-compose restart?

[TK-3375]

I use portainer but I guess it's the same. Yes I have stopped and restarted the container (the entire server too, to be safe). No luck

[Blackwidow-sudo]

yes i can confirm that: Step 4 & 5 didn't work for me either. I get the same response.

[TK-3375]

yes i can confirm that: Step 4 & 5 didn't work for me either. I get the same response.

For whatever reason i tried again and it worked... I have no idea what changed since i first tried. I guess a few restarts helped somehow

[Blackwidow-sudo]

oh ok. Well i just deleted the data folder. I had no proxies set up anyway.

[mzagozen]

An alternative that does not require creating a new user and losing any data is to just update the password hash for the user. The passwords are hashed with bcrypt. You can use Python to create a new hash:

$ python -c 'import bcrypt; print(bcrypt.hashpw("password".encode("utf-8"), bcrypt.gensalt()).decode("utf-8"))'
$2b$12$tMOjHhjExkb8d/EMrHOOy.WA0WAznst6WZyt7a1828FUOvEb9NhtW

Then you can install sqlite3 in the container like in Step 1 and update the hash for any user:

UPDATE auth SET secret = '<hash>' WHERE user_id = <admin-user-id>

[thunermay]

Nice idea! How do you get the correct user id?

UPDATE:
SELECT id, email FROM user; should to the trick. Just look up the user by the email and set the hash accordingly (column nickname optionally is also available)

[1lIiiIl1]

[TobiasGdot]

your problem seems to be, you haven't followed the whole instruction nor read through the other comments ;)
Use the new account to reset the password of the old one or you gonna have to update the owner ids of the tables holding the content

[IMNotMax]

For those who, like me have this password issue in Nginx Proxy Manager ADD-ON in Home Assistant, here some information.
1/ First, have a SSH access to your HA server (Advanced SSH & Web Terminal is great with Protection Mode DISABLED !)

2/ Ssh your HA and type : docker ps to find the NPM container name

Welcome to Home Assistant OS.
Use ha to access the Home Assistant CLI.

**docker ps**

CONTAINER ID   IMAGE                                                              COMMAND                  CREATED          STATUS                PORTS                                                                                                                          NAMES
110c2ac207ed   ghcr.io/hassio-addons/nginxproxymanager/aarch64:1.0.1              "/init"                  5 minutes ago    Up 5 minutes          0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp                                           addon_a0d7b954_nginxproxymanager
fa23a1250422   homeassistant/aarch64-addon-mariadb:2.6.1                          "/init"                  22 minutes ago   Up 22 minutes                                                                                                                                        addon_core_mariadb
567c019a872f   zigbee2mqtt/zigbee2mqtt-aarch64:1.35.2-1                           "/sbin/tini -- /dock…"   3 hours ago      Up 3 hours            0.0.0.0:8485->8485/tcp, :::8485->8485/tcp                      

mine is addon_a0d7b954_nginxproxymanager

3/ Enter the container using docker exec -it addon_a0d7b954_nginxproxymanager sh
Now your are in the container, and NOW you can think of editing the DB... but mysql or sqlite are not installed...

4/ just type apk add sqlite
And now follow ALL the steps (copied from above and adapted)

5/ sqlite3 /config/database.sqlite to open the DB

6/ find your user id (usually it's 1 because you only have 1 user
SELECT id, email, is_deleted FROM user WHERE email='your-user-email-here'

7/ Change the is_deleted from 0 to 1 (this will force the admin@example - changeme user to be activated
UPDATE user SET is_deleted = 1 WHERE id = 1 (caution, put the id of your user, but usually it's 1)

8/ NOW, in home assistant, restart the add-on Nginx Proxy Manager and login with admin@example.com and changeme

9/ create a new admin user (DON'T FORGET THIS PASSWORD TOO !!!)

10/ logout

11/ Come back to your container via SSH and open the DB again (steps 2 to 5)

12/ Change is_deleted from 1 to 0 UPDATE user SET is_deleted = **0** WHERE id = 1 (if your user id is 1 of course)

13/ Restart the add-on in Home Assitant

14/ Log in with the new admin user you just created
NOW AND ONLY NOW you can change the password of your previous user (look in the Users tab).

15/ logout, and login with your old user and newly created password, and delete the admin user created in this procedure.

Hope this helps

NB: The update NGINX Proxy Manager Add-on (v1) does not rely on MariaDB anymore, that's why you have to edit the SQLite database inside the NginxProxyManager Container

[flippet]

The sqlite solution deleted all my proxy redirections and in the SSL section. Also saw an error "Owner:null" which wouldn't go away.

So at the end I had no other choice than deleting the entire deployment and creating it again from scratch.