You are here
marvdaluz - Tue, 2024/07/02 - 20:35
I installed my container following the default settings. But to access the container at the received address I always get error 503 service unavailable on port 12322 or I can't get to this page on when accessing through port 8096.
The Fiel server and WebDav access normally.
Can you help me locate where the problem is?
Thank you
Forum:
Tags:
I'm not the best on containers
But maybe I can get you putting out the data others will need.
Which/what container system is being used (I have never used TKL containers)?
What host is it running on?
Does the container service automatically expose all ports or is there a config file where you have exposed those ports? If there is a config file, can you share it?
Can you test from within the container that you have network connectivity?
Hmm, I'm not sure. I'm wondering it Jellyfin has crashed?
Hi marvdaluz, as per the subject, I suspect that Jellyfin may have crashed and/or not be running for some reason. I say that as our appliance has Jellyfin bound to localhost and reverse proxied via the Apache webserver that also runs the Webdev interface. A 503 error means "Service unavailable" - so for some reason teh reverse proxy can't connect to Jellyfin.
Also, thanks as always for dropping in Timmy and trying to help.
I don't have a Jellyfin server running ATM and will hopefully have a closer look myself ASAP. In the meantime, Jellyfin runs as a service. So you can check it's status like this:
If that reports as "active (exited)" or some other status that suggests it may not be running, try restarting it like this:
If that still doesn't work, please rerun the status command and share that. Also within 10 minutes of running the restart command, please give me the output of:
Hey there,
Hey there,
Found this thread after searching for a similar problem and it seems like I'm facing the exact same scenario
Running the first command you gave tells me the service does not exist
root@turnkey-jellyfin ~# systemctl status jellyfin
Unit jellyfin.service could not be found.
For context, I'm running the latest MediaServer LXC template on Proxmox
Thanks very much for reporting!
Thanks so much for reporting. I just had a quick look and for the v18.0 LXC build, you are absolutely right. :(
TL;DR fix it by manually reinstalling Jellyfin - like this:
FYI, I've had a poke around and I can see what has happened, although I still don't know why. The v18.0 build code definitely installs Jellyfin. And the jellyfin packages installed in published v18.0 ISO release - you can see the jellyfin packages listed on the manifest. That's not surprising to me, because we have some automated smoke testing that explicitly tests the Jellyfin login so it would have failed.
But when I checked the LXC build myself, the Jellyfin packages aren't installed!? Looking closer at the LXC build logs I can see the Jellyfin packages being uninstalled!?:
Note that the di-live, live-boot, live-tools & live-boot-initramfs-tools packages are all intentionally being uninstalled. They are only relevant in an ISO and are not relevant to LXC , but for some reason the jellyfin packages are also being uninstalled?! I'll have to have a closer look and work out how/why that is heppening.
So thanks again for bringing this to my attention.
Thanks for the quick answer !
Thanks for the quick answer !
Glad that report could help
The quick fix works just fine, thanks
Add new comment