-
Notifications
You must be signed in to change notification settings - Fork 54
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
Error 500 - personal_access_tokens table remains empty #105
Comments
Hi, sorry for the delay, I haven't tried reproducing since I use MySQL. Does it still occur on the latest version ? |
Hi! No worries I also didn't have the patience or the time to test 😄 When I run From koel docker I get:
From postgres I get:
Maybe my previous mistake was that I tried to connect without seeing that error above, therefore login attemps might return code 500. Between every try, I do:
As for the settings, I use host Koel image: I use Postgres version 12. Everything is managed inside Portainer. |
Might be the same issue as koel/koel#1401 |
just
and
|
Isn't there a missing argument for the 'chown' call ? |
After installation I ssh inside the container and ran
php artisan koel:init --no-assets
which created a bunch of tables inside the database. I can see the default admin user inside theusers
table,personal_access_tokens
table is empty.When I try to log in I get error 500 and this is the log:
It looks like it cannot create the token or something - although the error is different maybe it is related somehow to #54 ?
Since artisan was able to create the tables I doubt it's a read/write permission issue, but to be safe I make the koel user a superuser.
I'm using Postgresql on a Pi 4. This pulled the latest docker version - not sure which one. If you need more info please ask.
The text was updated successfully, but these errors were encountered: