[GH-ISSUE #1489] TypeError: e is null #853

Closed
opened 2026-02-26 02:34:27 +03:00 by kerem · 10 comments
Owner

Originally created by @SangeloDev on GitHub (Aug 28, 2022).
Original GitHub issue: https://github.com/koel/koel/issues/1489

Describe the bug
When trying to log into my clean install of koel, this happens:
image
I get a blank homescreen and this error.
If I have to provide you with logs, just tell me which ones an I'll upload them.
I am using the prebuilt binaries. Thanks a ton for the help :D

To reproduce
Steps to reproduce the behavior:

  1. Download prebuilt binaries (v6.0.5)
  2. Install koel like you normally would:
php artisan koel:init --no-assets
php artisan serve --port 7447
  1. Open up a browser and log in.
  2. Observe

Expected behavior
I can log in normally and go about importing/listening all my songs.

Environment

  • Koel version: 6.0.5
  • OS: Debian 11
  • Browser: Firefox 105.0b4
  • PHP version: 8.0
  • Node version v16.17.0
Originally created by @SangeloDev on GitHub (Aug 28, 2022). Original GitHub issue: https://github.com/koel/koel/issues/1489 **Describe the bug** When trying to log into my clean install of koel, this happens: ![image](https://user-images.githubusercontent.com/47925793/187099797-15afb6ff-a8b2-4fb2-b9d6-7d8f9f604a74.png) I get a blank homescreen and this error. If I have to provide you with logs, just tell me which ones an I'll upload them. I am using the prebuilt binaries. Thanks a ton for the help :D **To reproduce** Steps to reproduce the behavior: 1. Download prebuilt binaries (v6.0.5) 2. Install koel like you normally would: ```bash php artisan koel:init --no-assets php artisan serve --port 7447 ``` 3. Open up a browser and log in. 4. Observe **Expected behavior** I can log in normally and go about importing/listening all my songs. **Environment** - Koel version: 6.0.5 - OS: Debian 11 - Browser: Firefox 105.0b4 - PHP version: 8.0 - Node version v16.17.0
kerem closed this issue 2026-02-26 02:34:27 +03:00
Author
Owner

@phanan commented on GitHub (Aug 30, 2022):

Please follow the issue template and provide all necessary information. You're also encouraged to take a look at storage/logs/laravel.log.

<!-- gh-comment-id:1231747091 --> @phanan commented on GitHub (Aug 30, 2022): Please follow the issue template and provide all necessary information. You're also encouraged to take a look at `storage/logs/laravel.log`.
Author
Owner

@SangeloDev commented on GitHub (Aug 31, 2022):

Please follow the issue template and provide all necessary information. You're also encouraged to take a look at storage/logs/laravel.log.

I've updated my issue accordingly, sorry for not doing it in the first place.
Also, storage/logs/laravel.log is empty when this error occurs.

<!-- gh-comment-id:1233364796 --> @SangeloDev commented on GitHub (Aug 31, 2022): > Please follow the issue template and provide all necessary information. You're also encouraged to take a look at `storage/logs/laravel.log`. I've updated my issue accordingly, sorry for not doing it in the first place. Also, ``storage/logs/laravel.log`` is empty when this error occurs.
Author
Owner

@SangeloDev commented on GitHub (Sep 1, 2022):

Funnily enough, I can log in from the mobile app, probably because it only needs the backend. Don't know whether this could help or not, though.

<!-- gh-comment-id:1234644624 --> @SangeloDev commented on GitHub (Sep 1, 2022): Funnily enough, I can log in from the mobile app, probably because it only needs the backend. Don't know whether this could help or not, though.
Author
Owner

@phanan commented on GitHub (Sep 11, 2022):

I can't reproduce the problem, but why php artisan serve --port 7447?

<!-- gh-comment-id:1242919580 --> @phanan commented on GitHub (Sep 11, 2022): I can't reproduce the problem, but why `php artisan serve --port 7447`?
Author
Owner

@SangeloDev commented on GitHub (Sep 11, 2022):

I want to run koel on a different port because I have a lot of other services on my homelab. If that's an issue, I can try running a docker container for koel. I also use a reverse proxy

<!-- gh-comment-id:1242951098 --> @SangeloDev commented on GitHub (Sep 11, 2022): I want to run koel on a different port because I have a lot of other services on my homelab. If that's an issue, I can try running a docker container for koel. I also use a reverse proxy
Author
Owner

@SangeloDev commented on GitHub (Sep 11, 2022):

Quick update on the situation: Seems like it could be an NginX problem:
image
I can access koel directly from my IP address, which I cannot using my domain. I have now switched to docker as well.

<!-- gh-comment-id:1242960144 --> @SangeloDev commented on GitHub (Sep 11, 2022): Quick update on the situation: Seems like it could be an NginX problem: ![image](https://user-images.githubusercontent.com/47925793/189528856-2c2e91d0-e360-4863-abd9-4fe494f82db1.png) I can access koel directly from my IP address, which I cannot using my domain. I have now switched to docker as well.
Author
Owner

@gelokatil commented on GitHub (Sep 23, 2022):

Do you use nginx proxy manager with SSL?

<!-- gh-comment-id:1256664638 --> @gelokatil commented on GitHub (Sep 23, 2022): Do you use nginx proxy manager with SSL?
Author
Owner

@phanan commented on GitHub (Oct 7, 2022):

I doubt this is a Koel issue.

<!-- gh-comment-id:1271573527 --> @phanan commented on GitHub (Oct 7, 2022): I doubt this is a Koel issue.
Author
Owner

@Stolz commented on GitHub (Oct 22, 2022):

I'm having the same issue

<!-- gh-comment-id:1287800603 --> @Stolz commented on GitHub (Oct 22, 2022): I'm having the same issue
Author
Owner

@SangeloDev commented on GitHub (Oct 22, 2022):

I'm having the same issue

It ended up being a problem with NginX. I am using YunoHost that generates NginX configs for me, so I just regenerated the proxy config and it ended up working. I don't know though what exactly was the issue.

<!-- gh-comment-id:1287808617 --> @SangeloDev commented on GitHub (Oct 22, 2022): > I'm having the same issue It ended up being a problem with NginX. I am using YunoHost that generates NginX configs for me, so I just regenerated the proxy config and it ended up working. I don't know though what exactly was the issue.
Sign in to join this conversation.
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#853
No description provided.