Skip to content
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

Unable to log in #180

Closed
mstuart3 opened this issue Mar 25, 2021 · 6 comments
Closed

Unable to log in #180

mstuart3 opened this issue Mar 25, 2021 · 6 comments

Comments

@mstuart3
Copy link

Problem/Motivation

Cannot login to web UI

Expected behavior

User and password accepted

Actual behavior

Login dialog reports "No relevant user found."
Software version is showing v0.0.0

@sinclairpaul
Copy link
Member

Assuming you are using the default credentials listed in the documentation, have you previously setup then removed the addon?

If so you may need to reset the database (assuming you do not need the data), which is documented at:

https://github.com/hassio-addons/addon-nginx-proxy-manager/blob/main/proxy-manager/DOCS.md#option-reset_database

@mstuart3
Copy link
Author

mstuart3 commented Mar 26, 2021

Oddly, I can log in using the default, but none of the configuration is present. Everything but the login is working as normal however.

@sinclairpaul
Copy link
Member

Then it appears something has happened to the database hosted by the MariaDB addon. Unfortunately I doubt there is anything we can do to help, unless you can restore the DB.

@john-arvid
Copy link

john-arvid commented Apr 25, 2021

Same problem here, I still have the Mariadb with the database intact.
Is there a way to recover or reset the password from either the mariadb or nginxproxymanager docker console?

nginxproxymanager is still working, just can't log inn. (using a password manager so the credentials are correct)

@john-arvid
Copy link

Never mind, found a solution here. Managed to reset the original user and get all the config back.
NginxProxyManager/nginx-proxy-manager#230 (comment)

But why did this happen?

@frenck
Copy link
Member

frenck commented Apr 26, 2021

That is a question we cannot answer, unfortunately.

Closing this issue as resolved for now.

@frenck frenck closed this as completed Apr 26, 2021
@github-actions github-actions bot locked and limited conversation to collaborators May 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants