[Bug]: Jellyfin not initializing

[taehas]

Panel Version

1.11.7

Wings Version

1.11.7

Service

Jellyfin

Modified

No, I did not modify the egg

Expected Behavior

Step 1 : Install Egg Step 2: Functions as normal

Actual Behavior

Step 1: Install Egg Step 2: Crashes

Steps To Reproduce

Install as normal, seems to have not create several folders/ not have access to them.

Install logs

https://pteropaste.com/s3z5/

[Ashu11-A]

Permission error, they probably changed the way Jellyfin is configured, as I had to do a Reverse Proxy on it, as the port couldn't be set, if I'm not mistaken

[Ashu11-A]

hmm, it looks like there's something wrong with your installation, since even Nginx didn't start up due to a lack of permissions	Terminal	APP

try reinstalling, if you still get an error, I'll look into it further

[taehas]

Fresh install, it did this the first few times I tried installing before reporting too.

[Ashu11-A]

oh

[Ashu11-A]

can you send me the installation log?

[taehas]

Here you go https://pteropaste.com/xjcp/

[Ashu11-A]

Everything looks fine to me, but there are parts of the log missing, but I think it's fine

I'm going to research the problem, as I can't reproduce it in any way

[Ashu11-A]

Fixed in #391003d

If it shows up again, let me know, but I believe this has been solved, I'm setting the permissions to “777” (allowing ALL users read/write/execute permissions), I think this is a special case, since I couldn't reproduce it, if possible, let me know the:

kernel version of the machine:

uname -r

version of your Docker running:

docker --version

[Ashu11-A]

If you could test other Eggs to see if this happens again, I'd appreciate it!

[taehas]

https://pteropaste.com/0qie

tried uninstalling and reinstalling, the script is on the right version. kernel is 5.10.0-31-amd64 Docker version 27.1.1, build 6312585

[Ashu11-A]

If possible contact me on Discord, my id: ashu11_a, I will ask you to give me access to your panel, a friend of mine tested it on an amd64 machine and it worked normally, your case is very special and I want to understand why the permissions are not properly defined

[drylian]

https://pteropaste.com/0qie

tried uninstalling and reinstalling, the script is on the right version. kernel is 5.10.0-31-amd64 Docker version 27.1.1, build 6312585

What is your virtualization system? or is it a dedicated machine? use the command below to find out

systemd-detect-virt

if it doesn't return anything use

sudo dmidecode -s system-manufacturer

[taehas]

https://pteropaste.com/0qie tried uninstalling and reinstalling, the script is on the right version. kernel is 5.10.0-31-amd64 Docker version 27.1.1, build 6312585

What is your virtualization system? or is it a dedicated machine? use the command below to find out

systemd-detect-virt

if it doesn't return anything use

sudo dmidecode -s system-manufacturer

virt is none and manufacturer is supermicro

[Ashu11-A]

Inconclusive result. The user claimed that other servers were also experiencing permission errors, and when installing as a regular user inside the Docker container, it worked 'normally.' I believe something external was overwriting the file permissions for another user. The write permissions remained the same, but since the 'owner' of the folders was different, it was not possible to create, edit, or delete files. Even after setting the owner of the /home/container folder to 'container' or adding the user 'www-data', it was not possible to change the installation behavior. At one point, the folder owner was a certain polkitd, but I'm not sure if that can be considered relevant.

[taehas]

Found a fix for this issue, due to the Pterodactyl config.yml flag check_permissions_on_boot being set to false it could not properly configure permissions upon boot. Simply set it to true and relaunch wings, and all should be functional.