SOLVED: Server ignoring config settings

[bepis]

Hi I just installed jellyfin 10.8.13 on Alpine Linux and whenever I try to run it, I get this message:

The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings.

But when I checkout "etc/conf.d/jellyfin" I see the option there in the opts field:

supervisor=supervise-daemon
datadir="/var/lib/jellyfin"
cachedir="/var/cache/jellyfin"
logdir="/var/log/jellyfin"
opts="--nowebclient"

I can run jellyfin by explicitly adding the command myself or by installing jellyfin-web but I'm concerned somethings not right if the config file is not being used

[tmsrxzar]

what is the output of "ps aux | grep jellyfin" ?

[bepis]

Outputs "3665 root 0:00 grep jellyfin"

[tmsrxzar]

Outputs "3665 root      0:00 grep jellyfin"

jellyfin is not running, according to that

try this again

what is the output of "ps aux | grep jellyfin" ?

... when jellyfin is running

[bepis]

If I set the option explicitly and run it I get: "3702 root 0:06 jellyfin --nowebclient"

[tmsrxzar]

alright

the goal of the exercise is to see what jellyfin's arguments are when it's started by the system
in order to determine whether or not the log line is there regardless of --nowebclient
because either it's not starting from that config or jellyfin just spits that out when there is no webclient, regardless of arguments

[bepis]

Hmm I'm probably mis-understanding the config file then. Right now it's not setup to start automatically and I figured it used the configuration file even when starting manually

[TheDreadPirate]

If you modify the systemd file, that only affects when you start jellyfin via systemctl.

[bepis]

Awesome thank you