2024-03-24, 01:19 AM
It would be nice to know what os you're running.
My first suggestion is to point jellyfin not to the m3u that threadfin is using to load the m3u, but instead point it to the saved .xml file threadfin creates after you've made the edits.
So for example, with my docker instance of threadfin that location is at localipaddress:port/xmltv/threadfin.xml?username=username&password=password.
You can fine the location for this in the threadfin web ui by clicking the hamburger icon (three horizontal line) and then server information.
You will also need to go into the threadfin settings and check the web authentication, m3u authentication, xml authentication, and api authentication boxes to set up a username and password.
My first suggestion is to point jellyfin not to the m3u that threadfin is using to load the m3u, but instead point it to the saved .xml file threadfin creates after you've made the edits.
So for example, with my docker instance of threadfin that location is at localipaddress:port/xmltv/threadfin.xml?username=username&password=password.
You can fine the location for this in the threadfin web ui by clicking the hamburger icon (three horizontal line) and then server information.
You will also need to go into the threadfin settings and check the web authentication, m3u authentication, xml authentication, and api authentication boxes to set up a username and password.