How do I get this working in Jellyfin?

[jlsans4]

I finally got docker working for my first time, I pulled this repository onto my local machine, but now I am unsure how to continue. There is a claim on a webUI but I don't see any way to get to it and I'm unsure how I can get a M3U file on. I can't seem to get Live TV working in terms of the schedule the way I currently have it. (M3U in jellyfin with multiple schedules that don't do anything, can't see anything when attempting to map channels either.)

[carlreid]

Please refer to the Jellyfin Live TV documentation: https://jellyfin.org/docs/general/server/live-tv/setup-guide

Both a HDHR and M3U URL is made available in StreamMaster:

1. Select Stream Groups:
   

2. You can find the HDHR, M3U, and XML EPG links here:
   

So by right clicking on one of those icons, and copying to clipboard.

If you have problems with Jellyfin's usage, I'd suggest opening a question on the relevant area.

[carlreid]

If you're running via Docker on your own machine, then I believe you should be able to see the interface at http://127.0.0.1:7095 or http://localhost:7095 to see the StreamMaster Web UI.

[jlsans4]

Yeah I'm running from Docker, I tried accessing it from localhost:7095 and 127.0.0.1:7095 as well as the machines IP but it keeps saying unable to connect

[carlreid]

Have you followed the documentation on Getting Started? Without more information I can't really be of help.

[jlsans4]

I have, I’ll try tweaking the docker-compose.yml to see if I can get anything working. I was using the yml provided in the GitHub repository so maybe I need to add some of the items from the getting started page to get it working.

[carlreid]

The README's example:

services:
  streammaster:
    image: ghcr.io/carlreid/streammaster:latest
    container_name: streammaster
    ports:
      - 7095:7095
    restart: unless-stopped
    volumes:
      - ~/streammaster:/config
      - ~/streammaster/tv-logos:/config/tv-logos

Should be enough anyway.

Check if the Docker ports are being exposed correctly, or look at the StreamMaster logs from the container if it might be an issue with StreamMaster.