2024-08-12, 12:59 AM
Just keep in mind that hosting your own media server on a VPS, if you need to do a lot of transcoding or other CPU intensive tasks such as media scanning frequently and whatnot, a shared plan would make the overall experience worse since you would suffer slowdowns unless you pay for a plan with a dedicated CPU, which can be significantly more expensive.
Another thing to consider is that sometimes some of the CPUs that VPS providers use are not that great at transcoding and depending on your provider you don't even get to choose which one your virtual machine will use. Also, storage can be very expensive to rent. There are ways to expose your own local storage to said VPS but at that point it may be better to simply host within your own network exposing Jellyfin through a reverse proxy.
The amount of fees I had to pay monthly and how they would stack over a year made me reconsider, and decided to foot the electric bill myself while providing my own server too.
Another thing to consider is that sometimes some of the CPUs that VPS providers use are not that great at transcoding and depending on your provider you don't even get to choose which one your virtual machine will use. Also, storage can be very expensive to rent. There are ways to expose your own local storage to said VPS but at that point it may be better to simply host within your own network exposing Jellyfin through a reverse proxy.
The amount of fees I had to pay monthly and how they would stack over a year made me reconsider, and decided to foot the electric bill myself while providing my own server too.
Server specs => OS: Debian 12 | GPU: Arc A380 | CPU: Ryzen 5 5600X | 64GB RAM | 56TB
