SOLVED: Docker http 500 when trying to start jellyfin

[Jespor]

I've tried to restart my jellyfin container for the last 30 minutes, and cant figure out why it wont start.

In portainer i get http 500 alert, when ever i try to start it.
log: https://pastebin.com/zBgaiv5G

When i try to start it, it doesnt create any new log entries. So i have no idea how to figure out whats going on. any ideas?

[TheDreadPirate]

What is the output of "docker logs jellyfin" (assuming your container is called "jellyfin"). That will output the docker logs from before Jellyfin starts if something not jellyfin related is preventing the container from starting.

Also, can you share your docker compose with us?

[Jespor]

docker logs jellyfin gives the same output as the one i've put in the pastebin link. I dont really know what else to provide?
I've set up the container using docker run, so ive no compose file to share. I think i saw sometime that you could export the docker run commands but i dont remember, do you know?

---

Error response from daemon: failed to add interface vethb28b6c2 to sandbox: error setting interface "vethb28b6c2" IP to 172.17.0.4/16: cannot program address 172.17.0.4/16 in sandbox interface because it conflicts with existing route {Ifindex: 5 Dst: 172.17.0.0/16 Src: 172.17.0.1 Gw: <nil> Flags: [] Table: 254 Realm: 0}
Error: failed to start containers: jellyfin

I get the above, when i try "docker start jellyfin"

[TheDreadPirate]

It sounds like something is borked with the docker bridge network. How do you normally start jellyfin? With docker compose? Try switching to host networking? If you do, you will need to allow port 8096 in the host firewall.

[Jespor]

I used to have it on the host network. I don't know why though..
I've tried to set it to the host network and back to the bridge network and tried starting it every time.

the below paste is from a "docker container inspect jellyfin"
https://pastebin.com/5HZa6mb3

Ill try setting it back to host and try again

[Jespor]

also healthcheck says:
Stopped for 3 hours with exit code 128

and is unhealthy

[TheDreadPirate]

Try switching it back to host networking. You will need to comment out the port publishing lines. On the host you will need to allow port 8096.

Code:

sudo ufw allow 8096/tcp

[Jespor]

okay, i've NO idea what i did, but its working now. i've done the same thing over and over for like an hour. changing it to bridge and back to host. Now it works. why? - No clue. what was wrong? - no clue

---

... living on the edge... i tried to change it back to the Bridge network... that works now too. WTF?! - I'm done computing for today, this shit is magic and makes no sense.

thanks for the help!