[GH-ISSUE #658] Session expiring after manual install #469

New issue

Closed

opened 2026-02-26 02:33:18 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 02:33:18 +03:00

Owner

Originally created by @mfissehaye on GitHub (Sep 26, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/658

I installed Koel locally and I was able to run it correctly the first time. However in the second and third attempts the node packages installation could not complete and I copied node modules folder from previous installation and yarn built.

However everytime I login, an error log appears on the JavaScript console something like authorization error and the login screen shows up after redirection.

I checked out the users table in the database and the admin user's entry has its remember_token column set to null. I have learned from a previous experience in Laravel that the session expires automatically after login if remember_token is not set. This happens mostly when user is created with a seeder or from the tinker console.

What could be wrong?

My intention is to deploy the Koel app on server and I can't run the Koel:init script on server as the yarn stage requires certain amount of memory which my server doesn't fulfill. Is there an automated script to deploy the app to server?

Originally created by @mfissehaye on GitHub (Sep 26, 2017). Original GitHub issue: https://github.com/koel/koel/issues/658 I installed Koel locally and I was able to run it correctly the first time. However in the second and third attempts the node packages installation could not complete and I copied node modules folder from previous installation and yarn built. However everytime I login, an error log appears on the JavaScript console something like authorization error and the login screen shows up after redirection. I checked out the users table in the database and the admin user's entry has its remember_token column set to null. I have learned from a previous experience in Laravel that the session expires automatically after login if remember_token is not set. This happens mostly when user is created with a seeder or from the tinker console. What could be wrong? My intention is to deploy the Koel app on server and I can't run the Koel:init script on server as the yarn stage requires certain amount of memory which my server doesn't fulfill. Is there an automated script to deploy the app to server?

kerem closed this issue

2026-02-26 02:33:18 +03:00

kerem commented

2026-02-26 02:33:19 +03:00

Author

Owner

@phanan commented on GitHub (Sep 29, 2017):

You shouldn't even need node_modules – just copy the generated assets over. This must be a different problem altogether. Also remember_token is not used by Koel.

@phanan commented on GitHub (Sep 29, 2017): You shouldn't even need node_modules – just copy the generated assets over. This must be a different problem altogether. Also `remember_token` is not used by Koel.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#469

No description provided.

Rows
Columns