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

No Relevant User #603

Open
floodwayprintco opened this issue Oct 5, 2024 · 3 comments
Open

No Relevant User #603

floodwayprintco opened this issue Oct 5, 2024 · 3 comments

Comments

@floodwayprintco
Copy link

Problem/Motivation

I cannot configure, because I cannot access the WebUI. Default login doesn't work.

Expected behavior

[email protected] and changeme should log me in.

Actual behavior

No relevant user.

Steps to reproduce

Install add-on, start it up, try to access web ui.

Proposed changes

I have seen there is a way to edit the database? Perhaps a clear instruction on how to 'reset' this add-on would help.

@alxis0
Copy link

alxis0 commented Oct 12, 2024

Hey, it looks like a recent pull request #474 removed the dependency on MariaDB/MySQL, and the add-on now utilizes the built-in SQLite database support.

To resolve your issue, you can take the following steps:

  1. Locate the SQLite Database:

    • Navigate to the following file path: /addon_configs/nginxproxymanager/database.sqlite.
  2. Delete the Database File:

    • Simply remove the database.sqlite file. This will reset the add-on default settings and allow you to configure it again with the default credentials.
  3. Reinstall add-on:

  • After deleting the file, reinstall the add-on, and you should be able to log in using the default credentials.

@justintrann
Copy link

Here is what I did to log in for the first time with [email protected] and changeme credential.

  1. Exec to nginxproxymanager container, ex: docker exec -it addon_a0d7b954_nginxproxymanager bash
  2. Remove SQLite Database: rm /opt/nginx-proxy-manager/config/database.sqlite
  3. Escape from the exec session then restart the container, ex: docker restart addon_a0d7b954_nginxproxymanager

@floodwayprintco
Copy link
Author

Thank you all. For me at least, the issue is resolved because I ditched it all and went with Tailscale. I thought VPN would be the complex option based on threads I've seen in the past.

Looking at this NGINX stuff though it seems this admin issue is pretty common headache people have so I still appreciate you helping out and I hope this thread helps someone in the future or gets the issue resolved in the UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants