When your address shows "This Jellyfin server is offline", the relay has no connection from your server's plugin. The page checks again every 30 seconds and opens Jellyfin as soon as the server is back. Go through these checks in order.
1. Is Jellyfin running?
Open Jellyfin at home, at its local address. If it doesn't open, start or restart Jellyfin (or the computer, NAS or container it runs on). The address works again about a minute after Jellyfin is back.
2. Is the plan active?
In your account, a server card marked Paused: no active plan can't connect. Check Manage billing for a failed payment or an ended subscription. See Billing.
3. What does the plugin say?
In Jellyfin, open Dashboard → Coursier and read the status at the top.
| Status | What to do |
|---|---|
| Remote access is on | The plugin is connected. If viewers still see the offline page, wait a minute and reload: the address may have just moved to another relay. |
| Remote access is off | Switch Turn on remote access on. |
| Connecting… or Reconnecting… | The plugin is trying to reach a relay. If it stays like this for more than a few minutes, go to step 4. |
| Reconnecting… with "No relay has free capacity right now" | Our relays are full for the moment. Nothing is wrong with your server: the plugin keeps trying every few seconds and connects as soon as there is room, usually after we add a relay. See When relays are full. |
| Not connected to Coursier yet | The server isn't linked to your account. Follow steps 4 and 5 of Set up with a new activation code. |
| Update Jellyfin | This Jellyfin version has a known security problem and is no longer allowed to connect. Update Jellyfin, then restart it. |
| Status unavailable | Restart Jellyfin. If you just installed or updated the plugin, a restart is needed. |
4. Can the server reach Coursier?
On the plugin's page, open Troubleshooting and select Test connection to Coursier.
| Result mentions | Likely cause |
|---|---|
| DNS / cannot resolve | The server can't look up our addresses. Check the DNS settings of the computer or container running Jellyfin. Ad blockers such as Pi-hole or AdGuard Home sometimes block new domains: allow *.watch.coursier.io and the Coursier domains. |
| HTTPS / certificate | The computer's date and time are wrong, or something on your network inspects HTTPS traffic (some antivirus, firewalls or company networks). Fix the clock, or exclude Coursier from inspection. |
| Cannot connect / timed out | Outgoing HTTPS (port 443) is blocked: check firewall rules on the computer, the router, or a VPN running on the server. Coursier only needs outgoing connections; no port has to be opened. |
When relays are full
Each relay keeps spare room so streams stay smooth. When every relay is close to full, we stop placing new servers on them until we add another relay. We are alerted the moment this happens.
- Servers already connected keep working. A server that reconnects (after a restart or a short internet outage) gets its own place back.
- A server connecting for the first time, or after moving relays, waits. The plugin shows "No relay has free capacity right now" and retries by itself; you don't need to do anything.
- New sign-ups and new servers are paused meanwhile: the front page and your account say so, and nobody is charged for a plan we can't serve.
5. Still offline?
- Restart Jellyfin.
- On the plugin's page, under Troubleshooting, select Renew server credential.
- As a last resort: Disconnect this server, generate a new activation code in your account, and connect again. Your address stays the same.
If nothing works, contact support with the result of the connection test.