Connect Jellyfin, Emby or Silo

Choose the service you actually use

Jellyfin, Emby and Silo connect your own permitted media library to Odyssey. They are grouped under Media server in the web source form, but have separate choices in the native app. The selected service determines how Odyssey interprets the connection.

You need a reachable server, permission to its library and the appropriate token or account details. Odyssey supplies no media and cannot grant access to a server you do not already control or have permission to use.

On the website

1. Open Manage player, sign into your player and choose Add source.
2. Set Connection type to Media server.
3. Enter a Display name and Server or source URL.
4. Under Choose your media server, select Jellyfin, Emby or Silo. Although these are displayed as tick boxes, the form keeps exactly one server selected.
5. Enter API key or access token. The web form also provides an optional User ID.
6. Choose Save source, then open or refresh the connected Odyssey device.

For Silo, the web form specifically expects its Jellyfin-compatible address and a user access token for the intended Silo profile. The ordinary Silo website login address and its compatibility-service address are not interchangeable.

In the native app: Jellyfin and Emby

1. Open Add a Source from initial setup, or Settings → Sources → Add Source.
2. Choose Jellyfin or Emby and enter the Source Name and server address.
3. Enter API Token.
4. For Jellyfin, supply User ID (optional) if needed. The app can normally resolve a user from a user access token.
5. For Emby, supply the exact Emby User ID for reliable watched-status and resume integration. Ask the server administrator if you do not know it.
6. Save the connection, wait for loading and test a known title.

The web form currently calls User ID optional for both services; the native Emby form explicitly explains its importance for watched status and resume progress. Supplying the correct user ID is the useful choice when setting up that behaviour.

In the native app: Silo

1. Choose Silo in the native source chooser.
2. Enter the Silo compatibility URL. Silo’s Jellyfin compatibility service must be enabled.
3. Complete Username # profile using the sign-in format required for the profile you want to browse.
4. Complete Password # PIN, adding the profile PIN in the required format when applicable.
5. Save. The app authenticates with the compatibility service and stores the returned access token and user identity for the connection.

Do not paste a Silo password into the website’s access-token field. These are deliberately different setup routes. Use the exact profile format supplied by your Silo administrator rather than guessing at a display name.

A worked example

You already watch your own library through Jellyfin and want the same library on Apple TV. Add the Jellyfin server using its reachable address, a suitable token and the correct user identity when needed. Name it “Home library”. After the catalogue appears, play one short item and check that the intended profile has access.

Now open the same Odyssey managed setup on an iPad. Check the active profile and network reachability before adding another copy of the server. A management connection and a working server connection are both needed; neither replaces the other.

Correct a connection without rebuilding everything

Use Edit on the existing managed source to correct its details. If you abandon the web form, choose Cancel. Avoid deleting a source merely because its token needs correction: replacing it can affect saved channel bindings.

The server cannot be reached: check the complete address, port, HTTP or HTTPS scheme and device network. The library loads but history does not behave as expected: confirm the server user identity, especially with Emby. Silo rejects the connection: check that its compatibility service is enabled and that the profile sign-in format is correct.

Can one connection expose every library? Only the content permitted by the server account and the Odyssey profile is available. Will connecting the server automatically publish a channel? No. Channel Studio has a separate save, review and publish workflow.