starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 00:36:03 +03:00

[GH-ISSUE #2181] [Bug]: Cannot log in on production even though credentials are correct (no password recovery option) #1113

New issue

Open

opened 2026-02-26 02:35:17 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 02:35:17 +03:00

Owner

Originally created by @richardt1984 on GitHub (Dec 19, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2181

Originally assigned to: @phanan on GitHub.

Read the Troubleshooting guide.

I have read and followed the Troubleshooting guide

Reproduction steps

Deploy Koel on a production server with a custom domain and HTTPS.
Complete installation and create an admin user.
Verify database connection works via php artisan tinker.
Verify user exists and password hash matches using Hash::check.
Open the Koel login page in an incognito browser.
Enter the correct email and password.
Submit the login form.

Expected behavior

After entering correct credentials, the user should be authenticated and redirected to the Koel dashboard.

Actual behavior

Login fails silently. The login page reloads or stays in place.
No error message is shown.
User is not authenticated even though credentials are correct.
There is also no “Forgot password” option available.

Logs

No relevant errors appear in storage/logs/laravel.log during login attempts.
Browser console also shows no errors.

Koel version

Latest version from the Koel GitHub repository (installed via git clone).

How did you install Koel?

Compiled from source

Additional information

Database connection works correctly.
User password hash is valid (Hash::check returns true).
Only one APP_KEY is present.
Caches cleared, sessions cleared, permissions fixed.
Services restarted.
Issue persists across browsers and incognito mode.

This behavior makes Koel difficult to trust in production, especially due to the lack of a password recovery option.

Originally created by @richardt1984 on GitHub (Dec 19, 2025). Original GitHub issue: https://github.com/koel/koel/issues/2181 Originally assigned to: @phanan on GitHub. ### Read the Troubleshooting guide. - [x] I have read and followed the Troubleshooting guide ### Reproduction steps 1. Deploy Koel on a production server with a custom domain and HTTPS. 2. Complete installation and create an admin user. 3. Verify database connection works via `php artisan tinker`. 4. Verify user exists and password hash matches using `Hash::check`. 5. Open the Koel login page in an incognito browser. 6. Enter the correct email and password. 7. Submit the login form. ### Expected behavior After entering correct credentials, the user should be authenticated and redirected to the Koel dashboard. ### Actual behavior Login fails silently. The login page reloads or stays in place. No error message is shown. User is not authenticated even though credentials are correct. There is also no “Forgot password” option available. ### Logs No relevant errors appear in storage/logs/laravel.log during login attempts. Browser console also shows no errors. ### Koel version Latest version from the Koel GitHub repository (installed via git clone). ### How did you install Koel? Compiled from source ### Additional information - Database connection works correctly. - User password hash is valid (`Hash::check` returns true). - Only one APP_KEY is present. - Caches cleared, sessions cleared, permissions fixed. - Services restarted. - Issue persists across browsers and incognito mode. This behavior makes Koel difficult to trust in production, especially due to the lack of a password recovery option.

kerem commented

2026-02-26 02:35:17 +03:00

Author

Owner

@phanan commented on GitHub (Dec 19, 2025):

Koel version
Latest version from the Koel GitHub repository (installed via git clone).
This behavior makes Koel difficult to trust in production.

I wouldn't install an app using the master branch and say it's not "production ready."

especially due to the lack of a password recovery option.

The password recovery option is only available if you configure a mailer. No mailer (default) means no email sending, which means no password recovery.

Now with all that done, I find it pretty weird that you have no error whatsoever. Try Preserve Log in Dev Tools Network tab. Also try setting APP_DEBUG=true in .env file.

@phanan commented on GitHub (Dec 19, 2025): > Koel version > Latest version from the Koel GitHub repository (installed via git clone). > This behavior makes Koel difficult to trust in production. I wouldn't install an app using the `master` branch and say it's not "production ready." > especially due to the lack of a password recovery option. The password recovery option is only available if you [configure a mailer](https://docs.koel.dev/guide/getting-started#configure-a-mailer). No mailer (default) means no email sending, which means no password recovery. Now with all that done, I find it pretty weird that you have no error whatsoever. Try Preserve Log in Dev Tools Network tab. Also try setting `APP_DEBUG=true` in `.env` file.

kerem commented

2026-02-26 02:35:17 +03:00

Author

Owner

@richardt1984 commented on GitHub (Dec 19, 2025):

Thank you for your response and clarifications. I understand your points regarding the master branch not being intended as production-ready and the requirement for a configured mailer to enable password recovery.

Regarding the login issue:

I have confirmed that the database connection works correctly and that the admin user’s password hash is valid (Hash::check returns true).

I have cleared caches, restarted services, and verified APP_KEY and APP_DEBUG settings.

Despite this, the login form reloads without authentication, and no errors are shown in storage/logs/laravel.log or the browser console, even when DevTools is used.

It seems that the login failure is not related to credentials, password hashing, or caching, and I cannot identify any relevant error messages.

Could you advise on the next steps for debugging why authentication is silently failing in this environment? For example, are there known issues with session handling, middleware, or HTTPS configuration that could prevent logins from completing?

Thank you for your guidance.

Best regards,
Richardt

@richardt1984 commented on GitHub (Dec 19, 2025): Hi Thank you for your response and clarifications. I understand your points regarding the master branch not being intended as production-ready and the requirement for a configured mailer to enable password recovery. Regarding the login issue: I have confirmed that the database connection works correctly and that the admin user’s password hash is valid (Hash::check returns true). I have cleared caches, restarted services, and verified APP_KEY and APP_DEBUG settings. Despite this, the login form reloads without authentication, and no errors are shown in storage/logs/laravel.log or the browser console, even when DevTools is used. It seems that the login failure is not related to credentials, password hashing, or caching, and I cannot identify any relevant error messages. Could you advise on the next steps for debugging why authentication is silently failing in this environment? For example, are there known issues with session handling, middleware, or HTTPS configuration that could prevent logins from completing? Thank you for your guidance. Best regards, Richardt

kerem commented

2026-02-26 02:35:17 +03:00

Author

Owner

@phanan commented on GitHub (Dec 19, 2025):

I actually now think that there’s something wrong with your server setup.
The fact that there’s no log whatsoever may be an indication that the
request doesn’t reach the application at all. Have you tried running
koel:doctor?

On Fri, Dec 19, 2025 at 21:49 richardt1984 @.***> wrote:

richardt1984 left a comment (koel/koel#2181)
https://github.com/koel/koel/issues/2181#issuecomment-3676576739

Hi

Thank you for your response and clarifications. I understand your points
regarding the master branch not being intended as production-ready and the
requirement for a configured mailer to enable password recovery.

Regarding the login issue:

I have confirmed that the database connection works correctly and that the
admin user’s password hash is valid (Hash::check returns true).

I have cleared caches, restarted services, and verified APP_KEY and
APP_DEBUG settings.

Despite this, the login form reloads without authentication, and no errors
are shown in storage/logs/laravel.log or the browser console, even when
DevTools is used.

It seems that the login failure is not related to credentials, password
hashing, or caching, and I cannot identify any relevant error messages.

Could you advise on the next steps for debugging why authentication is
silently failing in this environment? For example, are there known issues
with session handling, middleware, or HTTPS configuration that could
prevent logins from completing?

Thank you for your guidance.

Best regards,
Richardt

—
Reply to this email directly, view it on GitHub
https://github.com/koel/koel/issues/2181#issuecomment-3676576739, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5O3UULDX2UOBWGK5SCQQ34CRQG5AVCNFSM6AAAAACPRCPMR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZWGU3TMNZTHE
.
You are receiving this because you were assigned.Message ID:
@.***>

@phanan commented on GitHub (Dec 19, 2025): I actually now think that there’s something wrong with your server setup. The fact that there’s no log whatsoever may be an indication that the request doesn’t reach the application at all. Have you tried running koel:doctor? On Fri, Dec 19, 2025 at 21:49 richardt1984 ***@***.***> wrote: > *richardt1984* left a comment (koel/koel#2181) > <https://github.com/koel/koel/issues/2181#issuecomment-3676576739> > > Hi > > Thank you for your response and clarifications. I understand your points > regarding the master branch not being intended as production-ready and the > requirement for a configured mailer to enable password recovery. > > Regarding the login issue: > > I have confirmed that the database connection works correctly and that the > admin user’s password hash is valid (Hash::check returns true). > > I have cleared caches, restarted services, and verified APP_KEY and > APP_DEBUG settings. > > Despite this, the login form reloads without authentication, and no errors > are shown in storage/logs/laravel.log or the browser console, even when > DevTools is used. > > It seems that the login failure is not related to credentials, password > hashing, or caching, and I cannot identify any relevant error messages. > > Could you advise on the next steps for debugging why authentication is > silently failing in this environment? For example, are there known issues > with session handling, middleware, or HTTPS configuration that could > prevent logins from completing? > > Thank you for your guidance. > > Best regards, > Richardt > > — > Reply to this email directly, view it on GitHub > <https://github.com/koel/koel/issues/2181#issuecomment-3676576739>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB5O3UULDX2UOBWGK5SCQQ34CRQG5AVCNFSM6AAAAACPRCPMR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZWGU3TMNZTHE> > . > You are receiving this because you were assigned.Message ID: > ***@***.***> >

kerem referenced this issue

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

[PR #1113] [MERGED] Bump pusher/pusher-php-server from 4.0.0 to 4.1.0 #1582

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#1113

No description provided.

Rows
Columns