Preserve the complete address
Jellyfin’s networking guide describes a Base URL as a prefix under which the server is reached. In an illustrative installation, the authorised address could be https://media.example/jellyfin. The host name alone and the full address with /jellyfin are different inputs for this purpose.
Copy the complete address supplied by the operator into the client’s documented server field. Do not invent an address from the television name, remove a path because it looks untidy or assume that a port from an unrelated tutorial is used on this installation. Keep private host names out of public screenshots.
Do not make the browser result too broad
The official guide warns that client applications generally do not handle Base URL redirects implicitly, and gives Android TV as an example requiring the prefix in its Host setting. A browser reaching the right page can therefore coexist with an incomplete address in another client.
For a useful comparison, retain the same server and account, then record the exact stage reached in each application. A login form appearing after correcting the address is progress even if a separate account error follows. It changes the next question from server location to authentication.
Treat automatic discovery as another mechanism
Jellyfin documents local discovery separately from ordinary HTTP or HTTPS access. Its discovery broadcasts are confined to the local subnet. A server missing from a discovered list does not, by itself, establish that an approved manually supplied address is unusable.
Ask the operator which connection method is intended for the network you are using. Avoid broad network changes merely to make an automatic list populate. A remotely used address, a local address and a browser bookmark may serve different contexts even when they ultimately refer to the same authorised library.
Coordinate changes to the server prefix
Changing the server Base URL is an administrative change with client and proxy consequences, not a routine viewer reset. Jellyfin states that it requires a restart and warns that removing a previous prefix can leave old paths invalid. Agree the address with the operator before replacing working bookmarks across devices.
Keep the old and new address forms in a private change record, alongside the server and client versions. Confirm the intended library after reconnection, then check one permitted item. This guide diagnoses a documented address difference; it does not test your server, provide its configuration or guarantee third-party integration compatibility.
Questions about this guide
Does browser access prove every app can omit the Base URL?
No. Jellyfin documents client limitations in following Base URL redirects.
Does no automatic discovery result always mean the server is offline?
No. Discovery and direct access are separate mechanisms; discovery is local-subnet scoped.