starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Incorrect handling of request timeout #347

New Issue
Closed
opened 2026-02-05 17:28:38 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 17:28:38 +03:00
Owner
Copy Link

Originally created by @TheRealTrip on GitHub (May 24, 2025).

Current Behavior

If a node containing servers is brought down then the owners of that server will no longer be able to use Pelican effectively (Described in this discord thread) the timeout is very long for when it gives up on trying to talk to the node - roughly 2 minutes I think - before it just gives up and displays what it can. Resulting in endless loading which feels like the whole frontend has gone down.

Expected Behavior

The frontend should be much more robust to uncooperative nodes and have much shorter timeouts and/or query the nodes status before trying to query the node so that the frontend just doesn't bother if the node is offline.

Steps to Reproduce

Add a new node to Pelican as usual
Add at least one server to the node
Stop wings on the node
Try use the Web UI

Panel Version

v1.0.0-beta21

Wings Version

v1.0.0-beta13

Games and/or Eggs Affected

N/A

Docker Image

No response

Error Logs

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @TheRealTrip on GitHub (May 24, 2025). ### Current Behavior If a node containing servers is brought down then the owners of that server will no longer be able to use Pelican effectively (Described in [this](https://discord.com/channels/1218730176297439332/1375443421585608794) discord thread) the timeout is **very** long for when it gives up on trying to talk to the node - roughly 2 minutes I think - before it just gives up and displays what it can. Resulting in endless loading which feels like the whole frontend has gone down. ### Expected Behavior The frontend should be much more robust to uncooperative nodes and have much shorter timeouts and/or query the nodes status before trying to query the node so that the frontend just doesn't bother if the node is offline. ### Steps to Reproduce Add a new node to Pelican as usual Add at least one server to the node Stop wings on the node Try use the Web UI ### Panel Version v1.0.0-beta21 ### Wings Version v1.0.0-beta13 ### Games and/or Eggs Affected N/A ### Docker Image _No response_ ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD commented 2026-02-05 17:28:42 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (May 26, 2025):

You can configure the timeouts for node requests in the panel settings. For some requests the timeout is even forced to 1.

In my local dev environment I only have offline nodes and multiple servers and everything loads fine. So this is a "niche" problem. There are probably some other (server-side) factors that slow down the panel and/ or the requests that are specfic to your configuration.

@Boy132 commented on GitHub (May 26, 2025): You can configure the timeouts for node requests in the panel settings. For some requests the timeout is even forced to 1. In my local dev environment I only have offline nodes and multiple servers and everything loads fine. So this is a "niche" problem. There are probably some other (server-side) factors that slow down the panel and/ or the requests that are specfic to your configuration.
OVERLORD commented 2026-02-05 17:28:45 +03:00
Author
Owner
Copy Link

@TheRealTrip commented on GitHub (May 27, 2025):

Interesting you can't reproduce - I have the timeouts you spoke about at their minimum values. I'll try and recreate on a fresh ubuntu install and see if it happens again.

@TheRealTrip commented on GitHub (May 27, 2025): Interesting you can't reproduce - I have the timeouts you spoke about at their minimum values. I'll try and recreate on a fresh ubuntu install and see if it happens again.
OVERLORD commented 2026-02-05 17:28:46 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Jun 3, 2025):

#1413 will add lazy loading to the server list (when using Grid).
This should help improve responsiveness and loading time of the server list.

@Boy132 commented on GitHub (Jun 3, 2025): #1413 will add lazy loading to the server list (when using `Grid`). This should help improve responsiveness and loading time of the server list.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#347
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?