mirror of
https://github.com/pelican-dev/panel.git
synced 2026-05-04 18:00:48 +03:00
Critical error on Webserver on Pelican Panel Docker Image #173
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 @BlockyBlockling on GitHub (Oct 15, 2024).
Current Behavior
Im running into the following error using the new Pelican panel Docker image with the official Docker compose-
2024-10-15 15:45:13,304 CRIT Server 'unix_http_server' running without any HTTP authentication checkingAlso HTTP server is not starting. I think it is an error from the HTTP server
Ive found a message on Discord with a similar error but it seems to have happened with Podman and Redis as DB not SessionDriver file.
Full container logs including DB init in Log Section.
Expected Behavior
It shall start the Webserver or please refresh the compose file
Steps to Reproduce
Use the official docker compose and start it up
Panel Version
Wings Version
Games and/or Eggs Affected
No response
Docker Image
ghcr.io/pelican-dev/panel:main
Error Logs
Is there an existing issue for this?
@rmartinoscar commented on GitHub (Oct 15, 2024):
Hey i accidently broke Caddy a fix is coming up as well as a proper image tagging, the compose file should use
latestwhich will refer torelease/v1.0.0-beta10(known working code) instead ofmain(dev only).Here's the WIP
i apologize for any inconvenience.
@BlockyBlockling commented on GitHub (Oct 15, 2024):
Okay thanks for the fast response. Yep I guessed that would come soon but Im stunned to check out pelican and test the new image and find those bugs.
Can you make sure to reference the PR once created?
@BlockyBlockling commented on GitHub (Oct 15, 2024):
Pr for where the Issue came from: #626
To fix try to remove the
admin offfrom the CaddyfileAnd revert line 53 from the Dockerfile to
EXPOSE 80:2019EXPOSE 443@BlockyBlockling commented on GitHub (Oct 24, 2024):
I've tried out the newest image with the PR fix. But I'm still getting the same error.
But I was able to fix it myself while testing, by implementing this change: https://github.com/Supervisor/supervisor/issues/717#issuecomment-1050976569
Aka. Adjusting the supervisord.conf to this:
If you would approve that change I'm gonna create a PR
@parkervcp commented on GitHub (Oct 24, 2024):
This is all internal to the container so I never saw that as an issue. It's supervisord listening internally. There is no exposed access.
You are free to make the PR and I will review it.