You have set up Jellyfin, everything worked yesterday, and today the web interface spins forever or refuses to load. Before you assume the worst, most "jellyfin not working" cases come down to a handful of things you can check yourself in a few minutes. This guide walks through that self-check list first, then explains what a hands-on support session actually covers, how billing in 15-minute steps works, and how remote access is kept safe.
It is written for people who run their own servers: you know your way around a terminal, you just want a second pair of eyes when something refuses to cooperate.
Prerequisites
- A server running Jellyfin, Emby Server, Nextcloud or mailcow that you control (SSH or console access).
- Access to your service logs and your reverse proxy configuration.
- A Telegram account, in case you decide to book a session.
- An account on our site, so support hours and sessions show up under Support.
Step 1: Five checks before asking for help
These are the same basics a support engineer will ask about first, so doing them up front saves everyone time.
1. Read the logs
Open the Jellyfin log and look at the last lines before the failure. Errors about missing files, permissions, database locks or failed bindings usually point straight at the cause. Do the same for your reverse proxy and for Docker, if you run the server in a container.
2. Check the ports
Confirm the service is actually listening and reachable. If the web interface does not load, test locally first (for example with curl against the local address and port), then from outside. A port that answers locally but not remotely points to firewall, NAT or proxy configuration rather than to Jellyfin itself.
3. Look at certificates
If the page loads over plain HTTP but not HTTPS, or your browser warns about the certificate, the problem is in the TLS setup or the proxy, not in the media server. Check expiry dates and whether the proxy is serving the right certificate for the hostname.
4. Check disk space
A full disk breaks databases, logs and transcodes in confusing ways. Check free space on the volume that holds your configuration and cache, not only on the media volume.
5. Note your versions
Write down the versions of the server, the plugin or app, Docker (if used), the reverse proxy and the OS. A surprising number of problems are version mismatches, and having the numbers ready makes diagnosis much faster.
Step 2: What to send
When you contact us, include:
- the versions from step 1;
- the relevant log excerpts around the failure (not the whole file);
- screenshots of the error in the browser or app;
- a short description of what changed since it last worked (an update, a new plugin, a moved license, a proxy change).
Questions that fit in an e-mail or a ticket stay free. Standard e-mail and ticket support is included with every active subscription and for one month after buying a lifetime license, so start there if your question is simple.
Step 3: Book a session when you want hands-on help
If you would rather have someone look at the server with you, buy support hours on the Technical support page. The hours appear in your account under Support.
From your account, book a session by choosing a free time slot at least 12 hours ahead. You can move the session up to 2 times, or cancel it up to 24 hours before it starts.
Step 4: How the session runs
The session takes place on Telegram. When needed, we use remote control of your server. You stay in control the whole time and can stop the remote access at any point. That combination, chat first and remote control only when it helps, keeps the session focused and keeps you in the driver's seat.
Step 5: Understand the billing
Billing is in 15-minute steps: only the time actually used is subtracted from your balance. Whatever is left stays in your account for 12 months and can also be used for development work later. You can see your remaining hours in your account under Support. Invoices are issued by Stripe and are available in your account.
Step 6: Know what support covers
A session covers things like:
- installing and configuring our Emby and Jellyfin plugins, Nextcloud apps and mailcow tools on your server;
- diagnosing problems with Emby Server, Jellyfin, Nextcloud, mailcow, reverse proxies, Docker and the Linux system around them;
- moving a license to a new server, upgrades and backups before a big change;
- a quick review of your setup with written recommendations.
If a request turns into building something new rather than fixing or configuring what exists, it becomes development work. Your remaining hours can be used for that too.
Tips and troubleshooting
- Do the five checks first. Logs, ports, certificates, disk and versions resolve a large share of "not loading" cases before any session is needed.
- Change one thing at a time. If you changed a proxy rule and updated a plugin in the same evening, you will not know which one broke it.
- Take a backup before big changes. Upgrades and migrations are much calmer with a recent backup, and a backup review is a legitimate reason to book a session.
- Keep the balance in mind. Because billing is in 15-minute steps, a short focused session for one specific problem is often enough. Leftover time does not disappear after the session.
- Use the free channels for simple questions. E-mail and tickets are the right place for quick questions; hours are for hands-on work.
- Reschedule early. You can move a session up to 2 times, but plan changes at least 24 hours ahead so the slot is not lost.
More background material is available in our knowledge base, and common questions are answered in the FAQ. If you are unsure whether your case needs a session, just contact us.
Conclusion
Most "jellyfin not working" problems are solved with logs, a port check, a certificate check, a disk check and a note of your versions. When that is not enough, a support session gives you a second pair of eyes on Telegram, remote control only when it helps and only while you allow it, and billing in 15-minute steps so you pay for the time you actually use. Start with the self-checks, then book hours on the Technical support page if you want company on the server.