[GH-ISSUE #1155] v4.2.2 stuck on loading screen #664

Closed
opened 2026-02-26 02:33:54 +03:00 by kerem · 6 comments
Owner

Originally created by @calvarado194 on GitHub (Dec 27, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/1155

Describe the bug
Upon loading the web client, whether on mobile or desktop, it stays stuck in the loading screen. No 500 errors are found in the developer tools, and no errors are being logged in storage.I've tried clearing cookies and logins, to no avail.

Environment

  • Koel version 4.2.2
  • OS: Server: Ubuntu 18.04
  • Browser: Firefox 71
  • PHP version 7.3.13
  • Node version 10.16.3

Additional context
Server is mounted on Apache 2.4

Originally created by @calvarado194 on GitHub (Dec 27, 2019). Original GitHub issue: https://github.com/koel/koel/issues/1155 **Describe the bug** Upon loading the web client, whether on mobile or desktop, it stays stuck in the loading screen. No 500 errors are found in the developer tools, and no errors are being logged in storage.I've tried clearing cookies and logins, to no avail. **Environment** - Koel version 4.2.2 - OS: Server: Ubuntu 18.04 - Browser: Firefox 71 - PHP version 7.3.13 - Node version 10.16.3 **Additional context** Server is mounted on Apache 2.4
Author
Owner

@phanan commented on GitHub (Dec 28, 2019):

By "stuck" do you mean it totally hangs, or does the loading animation still play?

<!-- gh-comment-id:569402577 --> @phanan commented on GitHub (Dec 28, 2019): By "stuck" do you mean it totally hangs, or does the loading animation still play?
Author
Owner

@calvarado194 commented on GitHub (Dec 28, 2019):

The loading animation still plays, but it stays playing forever.

I believe this is an issue with the web client, as I can confirm API keeps working thru the desktop app.

<!-- gh-comment-id:569439954 --> @calvarado194 commented on GitHub (Dec 28, 2019): The loading animation still plays, but it stays playing forever. I believe this is an issue with the web client, as I can confirm API keeps working thru the desktop app.
Author
Owner

@vmario89 commented on GitHub (Dec 28, 2019):

hi, i have similar scenario all the time. Because everything i want to open koel instance in desktop application or browser, sometimes i get the same "stucking" message similar to this screenshot:
https://user-images.githubusercontent.com/22930688/49013247-f6443b80-f173-11e8-8b49-999a6bdbdd48.jpg

it requires 15~20 seconds to "unstuck" and to display the albums/songs front view. after this long loading period Koel acts pretty and quick flawlessly.

I tried to inspect with Browser inspector and had a look in apache log files and the apachetop monitor. i re-viewed my web server vhost. looking to find some good settings to make it serving faster.

i already raised the php.ini memory to 512 mb

<!-- gh-comment-id:569444042 --> @vmario89 commented on GitHub (Dec 28, 2019): hi, i have similar scenario all the time. Because everything i want to open koel instance in desktop application or browser, sometimes i get the same "stucking" message similar to this screenshot: https://user-images.githubusercontent.com/22930688/49013247-f6443b80-f173-11e8-8b49-999a6bdbdd48.jpg it requires 15~20 seconds to "unstuck" and to display the albums/songs front view. after this long loading period Koel acts pretty and quick flawlessly. I tried to inspect with Browser inspector and had a look in apache log files and the apachetop monitor. i re-viewed my web server vhost. looking to find some good settings to make it serving faster. i already raised the php.ini memory to 512 mb
Author
Owner

@BrookeDot commented on GitHub (Apr 21, 2020):

For those having this problem can you upgrade to 4.3.0 and report back if the issue persist?

<!-- gh-comment-id:617434961 --> @BrookeDot commented on GitHub (Apr 21, 2020): For those having this problem can you upgrade to 4.3.0 and report back if the issue persist?
Author
Owner

@calvarado194 commented on GitHub (Apr 21, 2020):

It's been fixed as of v4.3.0. Thanks!

It's also worth mentioning that the bug appears related to Pusher support (I removed my Pusher credentials and everything went back to normal): It appears that Pusher went thru some large changes which broke backwards compatibility.

<!-- gh-comment-id:617459629 --> @calvarado194 commented on GitHub (Apr 21, 2020): It's been fixed as of v4.3.0. Thanks! It's also worth mentioning that the bug appears related to Pusher support (I removed my Pusher credentials and everything went back to normal): It appears that Pusher went thru some large changes which broke backwards compatibility.
Author
Owner

@BrookeDot commented on GitHub (Apr 22, 2020):

Glad it's working now! I'll go ahead and close this out.

<!-- gh-comment-id:617486352 --> @BrookeDot commented on GitHub (Apr 22, 2020): Glad it's working now! I'll go ahead and close this out.
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#664
No description provided.