Failed to start Jellyfin (code=exited, status=217/USER)

[Zyperspace]

- Running Jellyfin 10.8.10
- Debian Repository on a Raspberry Pi 4 Model B 4GB

DISCLAIMER: I'm a total Linux noob and new to this.

Full explanation: Whenever I try to start Jellyfin.service, which it tries to automatically upon launching my Raspberry, I get a bunch of errors and messages. They are not exactly encouraging from what I can tell. It was working fine a week ago, then I tried to follow a Reverse Proxy guide, and halfway through I had to leave. Now, 5 days later, Jellyfin won't even start and I don't know why. Maybe I deleted or am missing something?

--------------------------------------------------------------------------------------------------
Active: failed (Result: exit-code) since [some time today]; 8 min ago
Process: 972 ExecStart=/opt/jellyfin/jellyfin.sh (code=exited, status=217/USER)
Main PID: 972 (code=exited, status=217/USER)
CPU: 3ms

: jellyfin.service: Failed with result 'exit-code'.
: jellyfin.service: Scheduled restart job, restart counter is at 5.
: Stopped Jellyfin
: jellyfin.service: Start request repeated too quickly.
: jellyfin.service: Failed with result 'exit-code'.
: Failed to start Jellyfin
--------------------------------------------------------------------------------------------------

I'm at a loss for what to do, have been poking about at various forums and threads I could find by searching, but nothing I could make use of or figure out myself. Thanks beforehand.

Log is attached:

  jellyfin20230702.txt (Size: 13.7 KB / Downloads: 64)

[skribe]

- Running Jellyfin 10.8.10
- Debian Repository on a Raspberry Pi 4 Model B 4GB

DISCLAIMER: I'm a total Linux noob and new to this.

Full explanation: Whenever I try to start Jellyfin.service, which it tries to automatically upon launching my Raspberry, I get a bunch of errors and messages. They are not exactly encouraging from what I can tell. It was working fine a week ago, then I tried to follow a Reverse Proxy guide, and halfway through I had to leave. Now, 5 days later, Jellyfin won't even start and I don't know why. Maybe I deleted or am missing something?

--------------------------------------------------------------------------------------------------
Active: failed (Result: exit-code) since [some time today]; 8 min ago
Process: 972 ExecStart=/opt/jellyfin/jellyfin.sh (code=exited, status=217/USER)
Main PID: 972 (code=exited, status=217/USER)
CPU: 3ms

: jellyfin.service: Failed with result 'exit-code'.
: jellyfin.service: Scheduled restart job, restart counter is at 5.
: Stopped Jellyfin
: jellyfin.service: Start request repeated too quickly.
: jellyfin.service: Failed with result 'exit-code'.
: Failed to start Jellyfin
--------------------------------------------------------------------------------------------------

I'm at a loss for what to do, have been poking about at various forums and threads I could find by searching, but nothing I could make use of or figure out myself. Thanks beforehand.

Log is attached:

There really isn't any helpful information here unfortunately. The context above says that the jellyfin service is failing to start, but the log you provided doesn't even contain a startup sequence that can help us to understand why.

It's possible that there is no startup sequence in the logs because the execution isn't even getting to that point. But you'd have to be able to troubleshoot the linux systemd process to figure out why. It might be that this is something a simple as a typo in the service configuration. You might be missing the executable entirely. There's really no way to say from the information that we have here.

I think it's safe to say that this isn't actually a jellyfin problem though. This is an issue with the way the service is configured, the OS is configured, or the Jellyfin packages are installed. Those would be my guesses for the most likely culprit.

If you can provide information about what you did when you followed that guide, it might provide some clues.

[Zyperspace]

- Running Jellyfin 10.8.10
- Debian Repository on a Raspberry Pi 4 Model B 4GB

DISCLAIMER: I'm a total Linux noob and new to this.

Full explanation: Whenever I try to start Jellyfin.service, which it tries to automatically upon launching my Raspberry, I get a bunch of errors and messages. They are not exactly encouraging from what I can tell. It was working fine a week ago, then I tried to follow a Reverse Proxy guide, and halfway through I had to leave. Now, 5 days later, Jellyfin won't even start and I don't know why. Maybe I deleted or am missing something?

--------------------------------------------------------------------------------------------------
Active: failed (Result: exit-code) since [some time today]; 8 min ago
Process: 972 ExecStart=/opt/jellyfin/jellyfin.sh (code=exited, status=217/USER)
Main PID: 972 (code=exited, status=217/USER)
CPU: 3ms

: jellyfin.service: Failed with result 'exit-code'.
: jellyfin.service: Scheduled restart job, restart counter is at 5.
: Stopped Jellyfin
: jellyfin.service: Start request repeated too quickly.
: jellyfin.service: Failed with result 'exit-code'.
: Failed to start Jellyfin
--------------------------------------------------------------------------------------------------

I'm at a loss for what to do, have been poking about at various forums and threads I could find by searching, but nothing I could make use of or figure out myself. Thanks beforehand.

Log is attached:

There really isn't any helpful information here unfortunately. The context above says that the jellyfin service is failing to start, but the log you provided doesn't even contain a startup sequence that can help us to understand why.

It's possible that there is no startup sequence in the logs because the execution isn't even getting to that point. But you'd have to be able to troubleshoot the linux systemd process to figure out why. It might be that this is something a simple as a typo in the service configuration. You might be missing the executable entirely. There's really no way to say from the information that we have here.

I think it's safe to say that this isn't actually a jellyfin problem though. This is an issue with the way the service is configured, the OS is configured, or the Jellyfin packages are installed. Those would be my guesses for the most likely culprit.

If you can provide information about what you did when you followed that guide, it might provide some clues.

I'm afraid I, rather embarrasingly, cannot reproduce the steps I've carried out. I will, however, start out by attempting to remove Jellyfin and start from scratch. Whether that is the source of my issue or not, will be revealed when I'm done with that. I will chime in again when I'm finished.

[Zyperspace]

[/quote]
I'm afraid I, rather embarrasingly, cannot reproduce the steps I've carried out. I will, however, start out by attempting to remove Jellyfin and start from scratch. Whether that is the source of my issue or not, will be revealed when I'm done with that. I will chime in again when I'm finished.
[/quote]

Oh dear, now I can't even get curl or wget to fetch Jellyfin for me... It just says "> Determining optimal repository settings. Sorry, we don't support the Debian  codename ' ' ."

I am so lost.

[skribe]

I'm afraid I, rather embarrasingly, cannot reproduce the steps I've carried out. I will, however, start out by attempting to remove Jellyfin and start from scratch. Whether that is the source of my issue or not, will be revealed when I'm done with that. I will chime in again when I'm finished.
[/quote]

Oh dear, now I can't even get curl or wget to fetch Jellyfin for me... It just says "> Determining optimal repository settings. Sorry, we don't support the Debian  codename ' ' ."

I am so lost.
[/quote]

I hate to be the bearer of bad news, but it's really starting to sound like your linux installation might be more fundamentally broken. You said you're pretty new to linux, so you may have changed some things that you shouldn't have. Nothing here gives me a very clear picture of what that might be, but that error looks like it's having trouble even identifying the distribution that you're using. I still think it's safe to say, though, that none of this is actually a jellyfin issue. I think your OS needs some troubleshooting. I would also say that if you're not super interested in learning all of the overhead to run your server on linux, Jellyfin also runs just fine on Windows, if you're more familiar with that OS. Use whatever OS you're most comfortable with.