mirror of
https://github.com/pelican-dev/panel.git
synced 2026-05-04 18:00:48 +03:00
Installer timeouts the web server #250
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 @SirEndii on GitHub (Feb 5, 2025).
Current Behavior
Greetings.
After I have setup everything in the installer and I click the last button, the button shows a little loading circle. It seems that the frontend sends a form, but the installer takes a bit and does not respond in time.
This is a bit misleading, especially for users who aren't experienced with web development/hosting. I can now go to the main page, try to log in, but the installer isn't done yet in the background. I wait another minute and then everything works fine.
So the installer could need some love there. Maybe a little log too or progress bar what exactly it does currently.
Expected Behavior
No timeout, wait until it's done and show a "Install Success" or something similar
Steps to Reproduce
I installed the panel using docker compose, see https://github.com/pelican-dev/panel/discussions/967
Start the installer
I used mariadb
And the default options for the other settings
Click on install(Or whatever the name of the last button was)
And timeout(depending on the proxy configuration)
Panel Version
v1.0.0-beta17
Wings Version
not yet installed
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
@notAreYouScared commented on GitHub (Feb 27, 2025):
Without knowing exactly what environment you have, it's hard to know what step is holding it up.
Are you using sqlite? MySQL? MariaDB?
@SirEndii commented on GitHub (Feb 27, 2025):
I were using mariadb but on another host in a different country(we use a local datastore now)
So it took a while why I expected some loading screen or similar
i also already stated that I use mariadb in the steps
@notAreYouScared commented on GitHub (Feb 27, 2025):
So yeah, it would've been a latency issue, therefore taking more time than the default timeout for php/webserver.
Unless we change the webserver config to up the timeout, seems like a more isolated issue, and I have no interest in changing it.