fix: login doesn't work on first launch #63

Closed
opened 2026-04-05 19:45:39 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @imeesa on 9/17/2025

pre-pr:
logs are created with 0644, by root during the first laucnh setup stuff
that initial log is owned by root
relaunching the container chmod -R 777s the parent /app/storage directory, which means logs can be written to

if logs fail, the error goes all the way up to the login and users can't log in

post-pr:
logs are created with 0664, by root during the first launche setup stuff, but have the group as nginx because the setgid bit is set on /app/storage/logs, which is also owned by nginx now
log still owned by root, but nginx group members can still rw
relaunching the container still chmods, but the permissions are already set correctly on logs

*Originally created by @imeesa on 9/17/2025* pre-pr: logs are created with 0644, by root during the first laucnh setup stuff that initial log is owned by root relaunching the container chmod -R 777s the parent /app/storage directory, which means logs can be written to if logs fail, the error goes all the way up to the login and users can't log in post-pr: logs are created with 0664, by root during the first launche setup stuff, but have the group as nginx because the setgid bit is set on /app/storage/logs, which is also owned by nginx now log still owned by root, but nginx group members can still rw relaunching the container still chmods, but the permissions are already set correctly on logs
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pyrodactyl#63