mirror of
https://github.com/pelican-dev/panel.git
synced 2026-02-28 19:09:03 +03:00
Getting Timeout on Console Page #152
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @julian-piehl on GitHub (Sep 13, 2024).
Current Behavior
Sometimes when I open a console page or reload it, the loading bar on top twitches extremely and after some time nothing loads anymore because pelican gave me a timeout.
I'm still able to access the admin page.
In DevTools it looks like the UI is trying to start a websocket connection many times in a row (every request succeeds).
A screenshot of the DevTools Network Tab will follow as soon as I'm not in a timeout anymore and can access my console again...
Expected Behavior
I don't want to get a timeout from just opening the page or pressing F5 one or two times.
Steps to Reproduce
Open the pelican start page (not admin page) and select a server. Maybe press F5 or something.
Panel Version
1.0.0-beta8
Wings Version
1.0.0-beta4
Games and/or Eggs Affected
Satisfactory
Docker Image
ghcr.io/parkervcp/steamcmd:debian
Error Logs
No response
Is there an existing issue for this?
@parkervcp commented on GitHub (Sep 13, 2024):
get the panel logs please.
tail -n 150 /var/www/pelican/storage/logs/laravel-$(date +%F).log | curl -X POST -F 'c=@-' paste.pelistuff.com@julian-piehl commented on GitHub (Sep 13, 2024):
Panel Logs: https://paste.pelistuff.com/SdsY
DevTools:
@notAreYouScared commented on GitHub (Sep 13, 2024):
Created too far in the past. If I remember correctly the issue with that was your timezones are mixed.
@julian-piehl commented on GitHub (Sep 13, 2024):
Thought the same and checked it.
My computer, the server and the config (.env file) all have the same timezone.
@julian-piehl commented on GitHub (Sep 13, 2024):
Update: My Wings had the wrong timezone configured in
/etc/pelican/config.yml. Let's see if the error still persists or if that was the fix.@Boy132 commented on GitHub (Sep 16, 2024):
Either way this is not a bug but a configuration issue.
Next time please actually visit the Discord first and don't mindlessly tick off boxes.
@julian-piehl commented on GitHub (Sep 16, 2024):
Oh, sorry for not responding anymore. The panel is now working as intended, so I forgot about it 😅
Yes, this was a configuration issue resulting in a bug. If you have the timezone configured wrong, the panel shouldn't just make 50 requests in a row and get you in a timeout. A warning in the admin view, that the node has a different timezone than the Panel would be nicer instead of "You must be a hacker, we're going to send you into timeout". 😉