localhost:8096: Opening Jellyfin's Web Interface

Jellyfin, the free media server, serves its web app and API on http://localhost:8096. That address only works on the machine running the server; from a TV, phone or laptop use the server's local IP with :8096. If the page will not load at all, the Jellyfin service has stopped or failed during startup.

Jellyfin network defaults
PortPurposeChange it in
8096HTTP web UI and APIDashboard, Networking
8920HTTPS, once a certificate is setDashboard, Networking
7359 UDPClient auto-discovery on the LANFixed

Updated

On first launch, localhost:8096 opens the setup wizard where you create the admin account and add libraries. After that it opens the sign-in page. Both come from the same server process, so either one appearing proves the port is fine.

Run Jellyfin with the right ports

Docker Compose with host networking

Host networking exposes 8096 and the discovery port without separate port lines. Adjust the media path to yours.

services:
  jellyfin:
    image: jellyfin/jellyfin
    network_mode: host
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /srv/media:/media:ro
    restart: unless-stopped

Check the service on Linux

The status line shows whether it is active, and the journal shows why it stopped.

sudo systemctl status jellyfin
sudo journalctl -u jellyfin -n 50

When the server will not start

Check the newest file in Jellyfin's log directory. Common startup failures are a missing ffmpeg build, a data folder the service account cannot write to, and another program already bound to 8096.

A media server is a home project; a site that promotes your band or photography is a different job, and We.Inc publishes that kind of site without any server in your living room.

How it works

  1. Start Jellyfin as a service, from the tray app, or as a container.
  2. Open http://localhost:8096 on that machine and finish the wizard.
  3. Find the machine's local IP address and test http://<ip>:8096 from another device.
  4. Allow port 8096 through the server's firewall if other devices cannot connect.

Tips

  • On Windows the tray app can show Jellyfin as running while the server underneath failed; the log folder shows the real reason.
  • In Docker, network_mode: host makes discovery on 7359 work; with bridged networking, publish 8096 and add devices by IP.
  • A blank white page after an upgrade is often a stale browser cache of the old web client. A hard reload clears it.

Frequently asked questions

What is localhost:8096?

It is the default address of the Jellyfin media server's web interface and API on the computer where Jellyfin is installed.

Why can my TV not connect to localhost:8096?

On the TV, localhost means the TV. Enter the server's local IP address with port 8096, for example http://192.168.1.20:8096, and make sure the firewall on the server allows it.

How do I enable HTTPS on 8920?

In Dashboard, Networking, provide a certificate file in PKCS #12 format and enable HTTPS. Many people instead keep 8096 internal and put a reverse proxy with a certificate in front of it.

How do I change the Jellyfin port?

Set a new local HTTP port number in Dashboard, Networking, save, and restart the server. In Docker it is often simpler to keep 8096 inside and map another host port.

Related: What is localhost, localhost refused to connect, localhost:8443, localhost:47990 (Sunshine).

Start for free or see all free tools. We.Inc is free to start, with no card needed. AI building is on paid plans from $20 a month.

More in Guides

Product

Who It's For

Features

Resources

Company

View Sitemap