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

Pelican Egg Permission Issue – Breakdown #547

New Issue
Open
opened 2026-02-05 17:45:10 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 17:45:10 +03:00
Owner
Copy Link

Originally created by @OfficialShinu on GitHub (Jan 12, 2026).

Originally assigned to: @parkervcp on GitHub.

Current Behavior

Servers created through the Pelican panel fail to start after installation.
During pre-boot, Wings attempts to:
Update configuration files (e.g. server.properties)
Apply ownership to the server root directory
Startup aborts with permission errors.
WebSocket connection closes and the server is marked offline.

The issue occurs:
On fresh installs
Even when “Start server after install” is disabled
Without any manual file uploads
Manually running:
chown -R 999:999 /mnt/server
immediately resolves the issue.

Expected Behavior

Expected Behavior

Servers installed via the panel should:
Have consistent file ownership after installation
Start successfully without manual permission fixes

Wings should be able to:
Modify server.propertie
Chown the server directory during pre-boot
Egg install scripts should leave /mnt/server in a valid state for Pelican’s container user (999:999).

Steps to Reproduce

Steps to Reproduce
Create a new server using a Minecraft (Paper / Fabric) egg
Allow the installation to complete (no manual file uploads).
Attempt to start the server (or allow auto-start).
Observe the server failing during pre-boot with permission errors.
Inspect server files on the node:
ls -l /var/lib/pelican/volumes/<server-uuid>/
Notice files owned byroot:rootinstead of pelican:pelican.

Panel Version

1.0.0-beta30.

Wings Version

v1.0.0-beta21

Games and/or Eggs Affected

Minecraft (Paper / Fabric-based eggs)

Docker Image

ghcr.io/pelican-eggs/yolks:java_21 also happened with 17

Error Logs

https://logs.pelican.dev/bb972fd6

as extra info 
adding "chown -R 999:999 /mnt/server" at the end of the egg install script fixes it

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 @OfficialShinu on GitHub (Jan 12, 2026). Originally assigned to: @parkervcp on GitHub. ### Current Behavior Servers created through the Pelican panel fail to start after installation. During pre-boot, Wings attempts to: Update configuration files (e.g. server.properties) Apply ownership to the server root directory Startup aborts with permission errors. WebSocket connection closes and the server is marked offline. The issue occurs: On fresh installs Even when “Start server after install” is disabled Without any manual file uploads Manually running: `chown -R 999:999 /mnt/server` immediately resolves the issue. ### Expected Behavior Expected Behavior Servers installed via the panel should: Have consistent file ownership after installation Start successfully without manual permission fixes Wings should be able to: Modify server.propertie Chown the server directory during pre-boot Egg install scripts should leave /mnt/server in a valid state for Pelican’s container user (999:999). ### Steps to Reproduce Steps to Reproduce Create a new server using a Minecraft (Paper / Fabric) egg Allow the installation to complete (no manual file uploads). Attempt to start the server (or allow auto-start). Observe the server failing during pre-boot with permission errors. Inspect server files on the node: `ls -l /var/lib/pelican/volumes/<server-uuid>/` Notice files owned by` root:root `instead of` pelican:pelican.` ### Panel Version 1.0.0-beta30. ### Wings Version v1.0.0-beta21 ### Games and/or Eggs Affected Minecraft (Paper / Fabric-based eggs) ### Docker Image ghcr.io/pelican-eggs/yolks:java_21 also happened with 17 ### Error Logs ```bash https://logs.pelican.dev/bb972fd6 as extra info adding "chown -R 999:999 /mnt/server" at the end of the egg install script fixes it ``` ### 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 added the not confirmed label 2026-02-05 17:45:10 +03:00
OVERLORD commented 2026-02-05 17:45:15 +03:00
Author
Owner
Copy Link

@OfficialShinu commented on GitHub (Jan 12, 2026):

adding chown -R 999:999 /mnt/server at the end of the scripts of the egg fixed it
putting it in the /etc/pelican/config.yml under docker doesn't work cause when starting wings it removes/overwrites it

@OfficialShinu commented on GitHub (Jan 12, 2026): adding `chown -R 999:999 /mnt/server ` at the end of the scripts of the egg fixed it putting it in the /etc/pelican/config.yml under docker doesn't work cause when starting wings it removes/overwrites it
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 not confirmed
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#547
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?