Reset Credentials for Nginx Proxy Manager

Greetings,

I’m running HassIO v93.2 along with DuckDNS and LetsEncrypt from the Add-On Store.

I installed Nginx Proxy Manager and I keep getting the following (even after uninstall and re-install)

No relevant user found

How do I reset the credentials. I was never able to log in and it does not take my HA credentials either.

Thank you

Anyone know how to assist ?

Or should I wipe the SD card (which I had just done for other reasons) and re-build it? Seems overkill.

Have you tried initial username and pass?
[email protected] / changeme

3 Likes

Thank you serkank ! I’m in.

I did change it the first time and did log me briefly and changed my password and went out of town and could not log back in. (yes I know the credentials I used).

I didn’t think to try the default credentials since I had removed and re-installed it.

Is it a way to reset the password without reinstalling the addon?

1 Like

I have also found for the second time that my credentials have vanished from the proxy manager and i need to re-enter the admin ones then re enter all my web forwards. Is this normal, can anyone suggest why it is happening ?

After a recent full restore from snapshot, this is happening to me, too.
I can’t login with my usual credentials. I just get “No relevant user found”

If I login with: [email protected] / changeme , I can get into the admin panel but all of my settings are gone.

Nginx DOES appear to be working though, as I can get to my HA from my phone at https://XXX.duckdns.org (incognito mode). However the logs show that my certificates are about to expire and Nginx isn’t able to renew them:

[8/20/2020] [4:57:17 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [8/20/2020] [4:57:17 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [8/20/2020] [4:57:17 PM] [Global ] › ℹ info Backend PID 555 listening on port 3000 ... [8/20/2020] [5:05:00 PM] [SSL ] › ✖ error Error: Command failed: /usr/bin/certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Challenge failed for domain XXXXX.duckdns.org Attempting to renew cert (npm-12) from /etc/letsencrypt/renewal/npm-12.conf produced an unexpected error: Some challenges have failed.. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/npm-12/fullchain.pem (failure)

I also tried restoring just MariaDB and Nginx from an earlier snapshot, but I get the same results.

Any ideas are welcome.

1 Like

I’m also getting the error ‘No relevant user found’ Whilst I can grab the config and re-create, it would be nice to not have to do that and reset the password to my existing user.

Reinstalling the addon does not remove its data, at least if its installed in mariadb. You can uninstall the nginx proxy and then install phpadmin addon, use that to drop the database in mariadb, then reinstall the addon. There are very few settings in nginx proxy so dropping the whole thing and starting again is not too onerous. Make sure you have 443 and 80 forwarded from your router, I removed 80 because I thought it not secure, it is needed for SSL cert renewal using certbot from Let’s Encrypt. That was my initial problem, cert could not be renewed. Also If you cannot remember your password and [email protected] / changeme does not work try your email address because on a fresh install you are prompted to change that BUT YOU ARE NOT PROMPTED TO CHANGE PASSWORD so likely like my case it is still “changeme”. Hope this helps someone, I lost a few hours resolving this today, it should not work like this, uninstalling should drop the database and you should NOT need to install phpadmin to do that with all the risks that involves since you hass data is stored there too!

2 Likes

Thanks Scott. phpadmin followed by a reinstall of nginx proxy worked.

There is the way to reset credentials without add-on re-installing:

I used phpMyAdmin add-on to update “user” table.

2 Likes

I had same issue after I moved my HA instance and restored from backup I could not see any configured hosts. It uses some default SQLite database which is temporary. I backed up DB via phpMyAdmin in case of loss and re-installed addon + restored DB. Then I was not able to start any web it reported Offline. I realized all SSL certificates were somehow broken during backup restore and I need to re-create them. I use cloudflare so I generated them with Cloudflare for 15 years and after this I was able to enable site with SSL back.

I’m facing this problem for the second or third time already.

Did you find a solution to solve it?

@JBenson74 @smith844 @RogTP

I think I uninstalled and reinstalled and it picked up the details from my mariadb instance.

According to this issue: https://github.com/hassio-addons/addon-nginx-proxy-manager/issues/344

  • Disable watchdog in mariadb addon to prevent this from happening again.
  • Run this command to restore the credentials:
    docker exec -it addon_a0d7b954_nginxproxymanager cp /defaults/production.json /data/manager/

Seems to have been solved, we’ll see if it doesn’t happen again.

3 Likes

Good News (or maybe just pure luck haha)
I couldn’t log in to NGINX after restoring from a backup.

My credentials would return No relevant user found
The standard credentials [email protected] + change would return Bad Gateway

The solution was to just restart the MariaDB add-on and turn of the watchdog (but that might not even be necessary)

1 Like

exactly thee same issue here

Worked for me, thank you!! Also have to restart Nginx-proxymanager add-on after doing those step

This is STILL an issue, have todo that many times, ven when the configuration is working, the login is broken again and again … :expressionless:

1 Like

Just sharing a data point that I just had this happen to me on an instance of HA at a vacation home:

  • I try to access HA through WAN (after a few months) and it forwards me to a generic nginx proxy page.
  • I VPN in. I can access HA on LAN. I can’t login to nginx proxy manager with saved credentials. Default credentials work but all settings are wiped.
  • I reconfigure the settings for nginx proxy manager and am now able to access HA from WAN.