You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using the docker container:
jc21/nginx-proxy-manager:2.10.3
with mariadb
yobasystems/alpine-mariadb:10.11.2
I was able to log in to npm perfectly fine until I upgraded to these two versions today.
I checked the db container, and the user is there, the bcrypt hash verifies against my password fine...
OK, I though to myself, I'll delete the user and the app will re-create the default admin.
Restarted npm after setting is_deleted
Nothing was created.
Tried logging in with default admin creds, got a CORS error this time.......?
Restored the user by reverting is_deleted to 0, nothing else in the db had changed, no default admin was created at all when npm restarted.
My guesses:
NPM is not connecting properly to mariadb(mysql)?
Not sure... any ideas are welcome.
Also, debugging is a chore... is there a recommended method to get verbose logs to print out as I'm sending requests etc.?
Beta Was this translation helpful? Give feedback.
All reactions