I finally ditched Netflix for Jellyfin, even on mobile – here’s how

I managed to give up Netflix completely, if you can believe it. After subscribing during my first week of college to immerse my head in some movies and shows while adjusting to three hours away from someone I knew in 2013, I have now canceled my subscription. Given the increasing costs of the service and my total lack of interest in the majority of productions (apart from a few comedy specials like “Uncle Stav”), it was time to cut ties.

In fact, the last thing I watched on Netflix was the 30-minute trailer for “GTA 6.” My subscription expired the next day. Now I’ve fully committed to Jellyfin, the open source media streamer that runs on something as small as the Geekom A8 mini PC. It takes a little more work than something like Plex, especially in terms of organization, but it’s completely free.

Born from Emby, another media server that has been forked since leaving open source, Jellyfin has been around since 2018. Now in version 12, there’s never been a better time to start using it. I even managed to get it working on the go, using a very cool alternative app on my phone that is served over the web with a custom domain. Surprisingly, it’s not as difficult as it seems to get started.

Jellyfin Material Considerations

Let’s talk about hardware first. You can upgrade Jellyfin’s hardware to meet your needs. Since it’s mainly my partner and I who regularly watch files of around 200 MB of various cartoons or “The X-Files”, the integrated GPU on the AMD chip of the Geekom A8 mini PC is more than enough to power everything. Even when transcoding on our TV, if I happen to encode something in a codec that isn’t natively supported, it’s agile enough to convert it to a format the TV app can accept. As I and others have discussed elsewhere, you don’t need the biggest PC you can find to power your server.

One aspect that has caused a huge headache in our household is storage. Choices about what should stay and what we could do without are the subject of regular conversations. That said, I store some shows in the cloud via one of the discrete subscriptions that I still don’t mind paying for.

With hardware prices exploding thanks to AI data centers, purchasing the right storage has become the most expensive part of managing Jellyfin operations. This is very much a “long term” conversation, but it’s incredibly annoying that the 5TB drive I bought in 2021 for around $100 now costs $600.

Configuring Jellyfin and Docker

With the hardware out of the way, running Jellyfin is incredibly easy, and mapping drives for the library is extremely simple. I use Ubuntu Server, but you can totally install Jellyfin on a regular operating system like Windows or macOS, as well as on all millions of versions of Linux. In my case I use the amazing Docker, which isolates Jellyfin in its own area on the PC and can be moved elsewhere if necessary.

One thing that tripped me up when getting started was Docker itself. Some applications can be launched simply via a command in the terminal, but I now prefer to use Docker Compose. This uses a YAML file to tell Docker exactly how to configure Jellyfin (or any other application), including drive mapping and other options that can get quite complicated when handled in the terminal.

The default Compose file provided by Jellyfin is more than sufficient, but sometimes going in blind can be a pain. What Jellyfin doesn’t tell you is how volumes are then mapped in Docker, somehow expecting you to already know that. Basically, when we see:

volumes:
-type: bind
   source: /path/to/media
   target: /media

Docker takes in the host file path and then creates its own in the container it will use next. It’s a mirror, so when adding media you just want to go to where you set the path in the comp file (/home/user/Videos/jellyfin/movies, for example). I’ve provided my commented version of the Compose file here if you want to use it as a template:

services:
  jellyfin:
    image: jellyfin/jellyfin #grabs Jellyfin
    container_name: jellyfin #names Jellyfin
    ports:
      - 8096:8096/tcp #Default Ports
      - 7359:7359/udp
    volumes:
      - /jellyfin/config:/config #Point the directory before the ":" to where you want config & cache stored
      - /jellyfin/cache:/cache
      - type: bind #As it says, binds the path to Docker
        source: /path/to/movies #replace /path/to/movies to the directory where media is stored
        target: /movies
      - type: bind
        source: /path/to/tv
        target: /tv
        read_only: true
      - type: bind
        source: /path/to/other/media
        target: /othermedia
        read_only: true
    
    restart: 'unless-stopped' 
    # Optional - alternative address used for autodiscovery
    environment:
      - JELLYFIN_PublishedServerUrl=http://example.com
    # Optional - may be necessary for docker healthcheck to pass if running in host network mode
    extra_hosts:
      - 'host.docker.internal:host-gateway'

Add essentials and explore other benefits of Jellyfin

With the custom Compose file and launched with the “docker compose -d“, follow the instructions and head to the server IP address you have it set up on, or if on your current computer, “localhost: (port you assigned).” Follow the on-screen instructions and you can now add media to your library. Pulling media you already own is a great way to get a head start, and there are plenty of digital sales or options for acquiring newer media. Simply place them, then head to the admin panel to search new media.

Although this is primarily for the home, Jellyfin is set up to allow for different users. My dad likes what I like, and having movies available that he wouldn’t otherwise have access to (like the Russian film “Stalker”) is handy. Just like Netflix, Jellyfin allows different profiles, which includes keeping your place while watching. Since I have full control, when my dad inevitably forgets the password I set, I can easily reset it for him without ever having to leave Jellyfin himself.

The TV application will also allow you to modify the fidelity of the stream, independently of the versions that I make available in the browser. This can be very handy when streaming 4K content over a not-strong enough connection, but Jellyfin also allows versioning. Some films I offer in 4K or 1080p, which the viewer can then switch between. Having full control of my collection is strangely empowering, especially compared to having to manage everything Netflix has to offer.

Nginx Proxy Manager is your key to going mobile

There are several ways to enable mobile access to Jellyfin, and I opted for a completely controlled method. I’m running a “headless” instance of Debian 13 on another mini PC (Geekom Air 11) – using SSH (Secure Shell), I control it through my main desktop and have Nginx Proxy Manager installed there. This integrates with a custom domain to direct Jellyfin from the local network to the wider web.

There are many options, including the simpler Caddy, but NPM works well for what I need and also provides Let’s Encrypt certificates to allow HTTPS to cover my connection securely. Nginx Proxy Manager requires ports 80 and 443 to be opened on your router, which is unfortunately different for each router. Be sure to consult the manual or an online guide to learn how to do this.

NPM also works through Docker, but since I configured the Debian web server during installation as a dope, I had to make some changes to the Docker Compose file to make it work. Rather than hosting on ports 80 and 443 internally, I changed them to 50080 and 50443, with 50081 acting as the admin panel. After that, I had to go to my domain registrar and create A records that pointed the domain to my public IP address.

I use Namecheap, but the concept is the same across the board. Find your public IP address, then add A records to your domain, two of which are required: @ And www. It should end up looking like this:

With this setup you can also add a subdomain, so for Jellyfin, either “jf.example.com” or “jelly.example.com”. Add another A record with your IP, then head to Nginx Proxy Manager.

Configuring Proxy Manager to access Jellyfin remotely

In NPM, choose Add a host under the “Proxy Host” setting in the “Hosts” menu. Enter the domain and subdomain you want it to point to. Make sure to turn on Block common exploits, Cache resourcesand above all, Websocket supportthat Jellyfin needs to function. Add a certificate in the “SSL Certificate” field and click Accept. If everything went well, it should now be online and pointing to your domain. Check it to make sure everything works.

If so, congratulations! Now you can log in to the official Jellyfin app or choose the much cleaner Streamyfin. The downside of Streamyfin, although it brings built-in casting and a much prettier user interface, is that there is no admin panel available. Instead, you will have to find it in the official app or browser UI.

If for some reason Proxy Manager gives you a headache, you can always use Cloudflare Tunnels. It’s a similar concept, except it presents itself as a Docker container on your network, redirecting Jellyfin’s local IP address to the wider web under Cloudflare’s oversight. The instructions for getting it working are all included by Cloudflare, but be warned: if you’re caught transmitting video through a public tunnel without the required paid service, Cloudflare may cut you off. That’s why I chose to move on to my own solution for now.

Gn tech

Logo