2024-02-08, 07:45 PM
(This post was last modified: 2024-02-08, 07:48 PM by TheDreadPirate. Edited 2 times in total.)
I guess we should backup a bit. Google Cloud Shell is not meant to run a service out of it. Which you found out with the one hour inactivity issue. There are too many unknowns about what Google is doing that might be affecting how transcoding behaves that the CF tunnel is just masking, somehow. 90% certain that it is due to NAT issues since it looks like you only have private IPs in a Google Cloud Shell. Which a CF tunnel would help workaround, but not resolve.
If your goal is to run Jellyfin reliably, you need to move to another platform. There are cheap VPS services all over the place, you can use an old PC/laptop. Heck, I don't recommend it, but you can use a RPi if you don't need transcoding (but please avoid using an RPi).
Are any of these an option? All of them are better than a free Google Cloud Shell.
If your goal is to run Jellyfin reliably, you need to move to another platform. There are cheap VPS services all over the place, you can use an old PC/laptop. Heck, I don't recommend it, but you can use a RPi if you don't need transcoding (but please avoid using an RPi).
Are any of these an option? All of them are better than a free Google Cloud Shell.
Jellyfin 10.10.7 (Docker)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04.2 LTS w/HWE
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
4x WD Red Pro 6TB CMR in RAIDZ1
