Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess

<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now

    • BlueÆther@no.lastname.nzOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      7 days ago

      the thing is I always use the network name. Once I used the IP I couls go back to using plex.<mylastname>.TLD

          • FreedomAdvocate@lemmy.net.au
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            1
            ·
            edit-2
            7 days ago

            You’re using the wrong address, that’s how it’s user error.

            If you just use the Plex app you wouldn’t have this issue either. Were you watching media on your Plex server machine through a browser instead of just opening Plex, and you typed in a url in the browser? Plex say to always just use app.plex.tv as it takes care of it all for you so things like this don’t happen.

            There isn’t even a debate here though - it’s an issue with the way your network is set up, not with Plex. Plex’s networking is far more advanced and better technically than jellyfins.

            • BlueÆther@no.lastname.nzOP
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              7 days ago
              • No where on the network page does it say to use app.plex.tv when you have a custom domain with ssl certs
              • I wanted to cast to a dumb TV with a chromecast, the macos app doesn’t seem to support that
              • if it was my network it would still not work, but it is again with no changes to the local network or to plex settings
              • Plex is seeing a local IP in the logs when accessed via a FQDN