Swiftfin loads posters but will not play: verify the server URL scheme

Preserve the successful catalogue stage

If Swiftfin signs in and loads posters but a video never starts, record those as separate results. Catalogue requests and media delivery can fail differently. Keep the exact client build, server version and first visible playback error before changing settings.

Use one known authorized item that plays through the server’s ordinary supported route. Keep the same viewer account for comparison. A different user or a different file can introduce another reason for the result and remove the useful baseline.

Inspect the actual HTTP or HTTPS endpoint

Swiftfin’s common-issues page documents a case where an HTTP address for an HTTPS server permits browsing through redirects while media requests fail. Compare the saved scheme with the server owner’s actual endpoint, including any required subpath or port.

Do not change a secure endpoint to plain HTTP as a generic experiment. Obtain the correct route and preserve the old entry’s identity privately. A browser automatically redirecting an address is not proof that every client request will follow the same path.

Make an authorized direct-path comparison

The project’s guide uses a direct IP-and-port comparison to distinguish a domain or proxy route where appropriate. Perform that only on a network where the server is actually reachable and with the owner’s supported access arrangement. A private address cannot be made reachable from arbitrary mobile data by typing it into the client.

Keep the same media item and account. If a direct supported route works while the named endpoint fails, preserve that contrast for the administrator. It narrows the path question without proving that every proxy or certificate setting is correct.

Review the relevant log before a broader reset

The project distinguishes login and ordinary application log routes in its current issue guide. Inspect the one relevant to the failing stage and retain a redacted reproduction. Remove tokens and private endpoint details before sharing a screenshot or file.

Once the corrected supported endpoint is configured, test the known video and its required tracks. The expected outcome is an understood media-delivery route, not simply a page of posters. It does not establish a universal codec fix or justify deleting the server’s library when the evidence concerns an address mismatch.

Related reading

• Swiftfin on Apple devices: connect the actual Jellyfin server
• Swiftfin player engine: compare the feature you need on the installed build

Questions answered

Sources & further reading

Official references for the subjects discussed. Service terms and device software can change.

• https://github.com/jellyfin/Swiftfin/blob/main/Documentation/common_issues.md