search

Tzahi12345 / YoutubeDL-Material

Self-hosted YouTube downloader built on Material Design
MIT License
2.65k stars 276 forks source link

[BUG] Upgrading to 4.3 (`latest`) causes failure to login with existing users from 4.2 #721

Open burntcookie90 opened 2 years ago

burntcookie90 commented 2 years ago

Describe the bug Existing users no longer found

To Reproduce Steps to reproduce the behavior:

  1. Using docker-compose with the latest tag
  2. Open login page
  3. Prompt shows to create admin user (can dismiss this, still causes an issue)
  4. Attempt to login with either existing admin user, or the admin user you just created via the previous dialogue, it will fail.

Expected behavior Old users should still work.

Screenshots

> backend@1.0.0 start
> pm2-runtime --raw pm2.config.js

2022-07-30T00:11:54: PM2 log: Launching in no daemon mode
2022-07-30T00:11:54: PM2 log: [Watch] Start watching YoutubeDL-Material
2022-07-30T00:11:54: PM2 log: App [YoutubeDL-Material:0] starting in -fork mode-
2022-07-30T00:11:54: PM2 log: App [YoutubeDL-Material:0] online
2022-07-30T00:11:55.588Z INFO: Restarting server...
2022-07-30T00:11:55: PM2 log: App [YoutubeDL-Material:0] exited with code [1] via signal [SIGINT]
2022-07-30T00:11:55: PM2 log: App [YoutubeDL-Material:0] starting in -fork mode-
2022-07-30T00:11:55: PM2 log: App [YoutubeDL-Material:0] online
2022-07-30T00:11:56.979Z INFO: YoutubeDL-Material v4.3 started on PORT 17442
2022-07-30T00:12:20.748Z ERROR: User admin not found
Error: connect ECONNREFUSED 127.0.0.1:389
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
Error: connect ECONNREFUSED 127.0.0.1:389
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)

Environment

Ideally you'd copy the info as presented on the "About" dialogue in YoutubeDL-Material. (for that, click on the three dots on the top right and then check "installation details". On later versions of YoutubeDL- Material you will find pretty much all the crucial information here that we need in most cases!)

Additional context Reverting to 4.2 fixes the issue.

myrenyang commented 8 months ago

I faced the same issue, finally found the issue was in appdata/default.json, set "use_local_db" to false then restart solved the issue.