• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions This client isn't compatible with the media and the server isn't sending a compatible

     
    • 0 Vote(s) - 0 Average

    This client isn't compatible with the media and the server isn't sending a compatible

    I am running my local instance of jellyfin under a Cloudflare runner, and when I navigate into it with a domine name I get the following error >This client isn't compatible with the media and the server isn't sending a compatible media fo
    crazyjoker96
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2023 Sep
    Reputation: 0
    #1
    2023-09-02, 08:27 AM
    I am running my local instance of jellyfin
    under a Cloudflare runner, and when I navigate into
    it with a domine name I get the following error

    >This client isn't compatible with the media and the server isn't sending a compatible media format.

    But when I navigate with the IP and Port all works, any idea what is going wrong?

    I am running the server with the following docker configuration


    version: '3.5'
    services:
      jellyfin:
        image: jellyfin/jellyfin:latest
        container_name: jellyfin
        network_mode: 'host'
        volumes:
          - /media/nas/.jellyfin/config:/config
          - /media/nas/.jellyfin/cache:/cache
          - /media/nas:/media
        restart: 'unless-stopped'
    bitmap
    Offline

    Community Moderator

    Posts: 766
    Threads: 9
    Joined: 2023 Jul
    Reputation: 24
    #2
    2023-09-02, 11:05 AM
    This is related to playback, not networking. This message occurs when you're trying to play a piece of media correct? Are you using two different clients? For instance, web browser vs. mobile phone or web vs. TV or Roku?

    Different clients will be compatible with different media, which will cause the client to request for the server to transcode the media to a different format. The only other difference that could cause this in a local vs. remote situation is whether you have bandwidth limits set either globally outside the network or specifically for the user experiencing this issue.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    crazyjoker96
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2023 Sep
    Reputation: 0
    #3
    2023-09-02, 02:21 PM
    (2023-09-02, 11:05 AM)bitmap Wrote: This is related to playback, not networking. This message occurs when you're trying to play a piece of media correct? Are you using two different clients? For instance, web browser vs. mobile phone or web vs. TV or Roku?

    Different clients will be compatible with different media, which will cause the client to request for the server to transcode the media to a different format. The only other difference that could cause this in a local vs. remote situation is whether you have bandwidth limits set either globally outside the network or specifically for the user experiencing this issue.

    No it is happening on the same client, I am just passing through clouflare stunned when I use the domine name.

    I did not understand the solution that you are proposing it you are to.
    iEiEi
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2024 Feb
    Reputation: 0
    Country:Germany
    #4
    2024-02-28, 09:34 AM (This post was last modified: 2024-02-28, 03:09 PM by iEiEi. Edited 1 time in total.)
    Hello Forum,

    I ran into the same problem with Chrome Browser. Just installed Jellyfin out of the box in Ubuntu 22.04, set up everything needed and couldn't play any mp3-file in Chrome, but it works in Firefox. I tested all from my MacBook and then directly on the Ubuntu desktop, the same problem there.

    I just would like to use Chrome Browser for streaming my music archive to my 2 ChromeCast speakers.

    So what's wrong? Usually the Chrome Browser is able to play mp3-files without any special adjustments.

    Thanks for your help,
    Achim

    EDIT:
    I don't know why Chrome doesn't play the mp3 files directly, but if I connect to ChromeCast first and then try playback, it works. But I found out that there is no queue when I stream to ChromeCast. Unfortunately, this is then also unusable.

    That works like a charm:
    Currently I'm using Firefox for Jellyfin Web and the playback works fine, also the queue seems to be stably available. For streaming playback to the ChromeCast speaker group I use Mkchromecast.
    Actually Jellyfin is running with Ubuntu 22.04 on a small Mini-ITX equipped self-built NAS with 8 GB memory. I use this box mainly as a backup target and media center for my music archive – and of course as playground for Linux.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode