xc/m3u api bug?

[aniel300]

am getting this error when trying to open the playlist, any thoughts?

[2024-11-21T13:23:12Z DEBUG m3u_filter::api::xtream_api] Paremeter action is empty!

[euzu]

yes, you try to access the playlist through the xtream api. But you are using the wrong url format. Xtream api needs an
action.

An example call is:
http://provider.tv/player_api.php?action=get_series&username=test&password=test&category_id=120

as you can see the action in this case is get_series

[aniel300]

any other m3u/xc playlist that i have added to this program works am not sure why this is not working

[euzu]

Do you mean other playlist from a real provider and not m3u-filter ?

It would be helpful if you give me more detail.

[aniel300]

could it be because the filter supports only http://serverurl:port/get.php?username=xxx&password=xxx and not http://serverurl:port/get.php?username=xxx&password=xxx&type=m3u_plus

[euzu]

what are you testing now? xtream or m3u?

[aniel300]

xtream

[aniel300]

it got in/ a little further but then gave this error

also getting this error in the logs btw [2024-11-21T17:37:37Z DEBUG m3u_filter::api::xtream_api] Cant find user!

[euzu]

your credentials are wrong

[euzu]

i have tested it with xtream and it worked.
I dont know how to reproduce this error.

[euzu]

why do you have the same playlists twice?
You can define multiple users for a target.
What is in the log when this error happens?
Do you have the right host and ports defined for the server in api_proxy.yml?

[aniel300]

1. 1 is for internal use and the the other one is for external use
2. how
3. [2024-11-21T20:47:14Z DEBUG m3u_filter::api::xtream_api] Cant find user!
4. that looks as follow

server:
- name: default
  protocol: http
  host: 0.0.0.0
  http_port: '8901'
  https_port: '443'
  rtmp_port: ''
  timezone: America/New_York
  message: xxx
- name: external
  protocol: https
  host: m3ufilter.xxx.top
  http_port: ''
  https_port: ''
  rtmp_port: ''
  timezone: America/New_York
  message: xxx

[euzu]

@aniel300 when you run the image in docker you cant use 0.0.0.0 or 127.0.0.1

[aniel300]

what can I use instead?

[euzu]

Your server config for default is wrong.
The lan-ip address of the server should be used.
I asume that you have in the docker-compose a port mapping 8901:8901. ( the server port 8901 to docker port 8901).
We name them Port-A:Port-B. In config.yml you need to use Port-B. In the api-proxy.yml Port-A.

In config.yml you use 0.0.0.0 In api-proxy.yml you use the lan-ip for default, domain url for external.

When your server has the lan ip f.e. 192.168.0.25. Than your default server ip is 192.168.0.25 and the port 8901 if configured so in docker-compose.
You should know some basics when working with docker.

[euzu]

use the webui for user .
The error means the credentials are wrong.

[aniel300]

they look like this #123 (reply in thread)

[euzu]

Your server config for default is wrong.
The lan-ip address of the server should be used.
I asume that you have in the docker-compose a port mapping 8901:8901. ( the server port 8901 to docker port 8901).
We name them Port-A:Port-B. In config.yml you need to use Port-B. In the api-proxy.yml Port-A.

In config.yml you use 0.0.0.0 In api-proxy.yml you use the lan-ip for default, domain url for external.

When your server has the lan ip f.e. 192.168.0.25. Than your default server ip is 192.168.0.25 and the port 8901 if configured so in docker-compose.
You should know some basics when working with docker.

[aniel300]

it doesn't matter if i use api: {host: 172.18.0.9, port: 8901, web_root: ./web} or api: {host: 0.0.0.0, port: 8901, web_root: ./web} i still get the same error. as for "You should know some basics when working with docker." idk what to say to that. am just a noob on this but i have been running docker and docker compose for few years now

[euzu]

@aniel300 no offense, it was just an advice.

It makes a difference. The config.yml is for starting the application. host in this case is the bind address for the server which should be 0.0.0.0. But the entry in api_proxy.yml is for the clients. They need an ip address to connect. This means you cant use 0.0.0.0 in api_proxy.yml.

What is you local lan ip of the server? Use this in api_proxy.yml

[aniel300]

this is debian remote headless server on a data center. idk what the lan ip is. this is my first time running into this

[euzu]

if you only have remote access than you dont need local server config. You can use the external.

[aniel300]

public ip and port also dosent play btw

[aniel300]

now the other app won't load it, i just realized it

[aniel300]

am getting these errors in the logs

[2024-11-22T18:50:11Z ERROR m3u_filter::api::m3u_api] M3uFilter error: Could not deserialize file "/data/external_xtream/m3u.db" - File not found /data/external_xtream/m3u.db
[2024-11-22T18:50:11Z ERROR actix_http::h1::dispatcher] stream error: request parse error: invalid Header provided

[aniel300]

this is the other player in question https://github.com/austintools/SFVIP-Player/releases

[aniel300]

m3u output works fine (kinda)

[aniel300]

i cant get this work even when bypassing traefik

[euzu]

@aniel300 i have tested this now with IPTV Player on windows and it works. I have pushed a new beta image, please update the image.
Before you ask , i have tested xtream api redirect and reverse.

[aniel300]

can u share ur configs, i still cant get it to work with xc api.

[aniel300]

m3u api does work/stream

[aniel300]

are testing within the same network, are u using internal networking and can u simulate using external network/public ip?

[euzu]

here is my config for xtream. This is only an example so dont think about the filter and names.

It is mandatory for xtream that input url, username and password are set correct.

source.yml

templates:
- name: MY_CHANS
  value: 'Group ~ ".*"'
sources:
- inputs:
    - type: xtream
      url: 'http://my-provider.com'
      username: testuser
      password: testuser.secret
      options: {xtream_info_cache: true}
  targets:
    - name: xtream
      publish: true
      filename:
      filter: "!MY_CHANS!"
      options: {ignore_logo: false}
      output:
        - type: xtream
      sort:
        match_as_ascii: true
        groups:
          order: asc
      mapping:
        - simple-mapping

api-proxy.yml

server:
- name: default
  protocol: http
  host: 192.168.0.81
  http_port: '8901'
  https_port: '8443'
  rtmp_port: '1935'
  timezone: Europe/Paris
  message: Welcome to m3u-filter
user:
- target: xtream
  credentials:
  - username: test
    password: test
    token: null
    proxy: reverse
    server: default
    epg_timeshift: null

[aniel300]

yes input xc info is set correctly. i keep getting this error [2024-12-03T14:27:09Z DEBUG m3u_filter::api::xtream_api] Cant find user!

[euzu]

You can name it as you like. But needs to match.

[aniel300]

yes it matches

[euzu]

Ok i will add some debug output for you and push an beta image, the log output will contain username and password.

[aniel300]

ok, i will try to sanitize it

[euzu]

no i mean this is for you to see if the username and password is passsed correctly to m3u-filter.

[euzu]

i have pushed a new beta image

[aniel300]

am getting this

[euzu]

but where is the error you mentioned?

[aniel300]

that is all i get. still i cant stream while using the xc api 😭

[euzu]

Can you explain me your complete setup ?

[aniel300]

config:

#   sec  min   hour   day of month   month   day of week   year
schedule: "0  0  8,20  *  *  *  *"
web_ui_enabled: false
web_auth:
  enabled: false
  secret: very.secret.secret
  issuer: m3u_filter
  userfile: user.txt
  threads: 8
api: {host: 0.0.0.0, port: 8901, web_root: ./web}
working_dir: ./data
update_on_boot: false

source:

  targets:
    - name: internal
      output:
        - type: m3u               
          #filename: iptv.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"
      options: {m3u_include_type_in_url: true, m3u_mask_redirect_url: true}     
    - name: external
      output:
        - type: xtream
          #filename: playlist.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"

api:

server:
- name: default
  protocol: http
  host: 172.18.0.1
  http_port: '8901'
  https_port: '443'
  rtmp_port: ''
  timezone: America/New_York
  message:
- name: external
  protocol: https
  host: m3ufilter.xxx.top
  http_port: ''
  https_port: ''
  rtmp_port: ''
  timezone: America/New_York
  message:
user:
- target: internal
  credentials:
    - {username: internal, password: internal, proxy: redirect, server: default}
- target: external
  credentials:
    - {username: external, password: external, proxy: redirect, server: external}

aside from this idk what else u would like to know. i have to take a nap now so i wont be able to debug or ts for few hours.

[aniel300]

config:

#   sec  min   hour   day of month   month   day of week   year
schedule: "0  0  8,20  *  *  *  *"
web_ui_enabled: false
web_auth:
  enabled: false
  secret: very.secret.secret
  issuer: m3u_filter
  userfile: user.txt
  threads: 8
api: {host: 0.0.0.0, port: 8901, web_root: ./web}
working_dir: ./data
update_on_boot: false

source:

  targets:
    - name: internal
      output:
        - type: m3u               
          #filename: iptv.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"
      options: {m3u_include_type_in_url: true, m3u_mask_redirect_url: true}     
    - name: external
      output:
        - type: xtream
          #filename: playlist.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"

api:

server:
- name: default
  protocol: http
  host: 172.18.0.1
  http_port: '8901'
  https_port: '443'
  rtmp_port: ''
  timezone: America/New_York
  message:
- name: external
  protocol: https
  host: m3ufilter.xxx.top
  http_port: ''
  https_port: ''
  rtmp_port: ''
  timezone: America/New_York
  message:
user:
- target: internal
  credentials:
    - {username: internal, password: internal, proxy: redirect, server: default}
- target: external
  credentials:
    - {username: external, password: external, proxy: redirect, server: external}

aside from this idk what else u would like to know. i have to take a nap now so i wont be able to debug or ts for few hours.

it is missing few things but i think i sent the most important part

[euzu]

@aniel300 how is your setup, you mentioned trafik? How does the client access m3u filter?
And another question your filter contains TR prefix, is that a country code?

[euzu]

i have used the server public ip. I have tested the reverse proxy mode, i can test with redirect too, wait.

[aniel300]

make sure to also use the new mask option

[euzu]

Yes everything works as expected

[euzu]

This is my test setup:

host1: windows inside docker
host2: caddy + m3u-filter inside docker, caddy port 8080
router: port 8080 forwarding to host2 port 8080

host1 docker windows running iptvapp -> url is http://external.domain.com:8080

everything works as expected

[aniel300]

ok so this is definly not a bug. i will keep trying things on my end as it sounds like an end user error, thank u for all the effort

[euzu]

After setup you should test first with curl.

curl "http(s)://my.external.ip/player_api.php?username=myuser&password=mypassword" fro xtream
curl "http(s)://my.external.ip/m3u?username=myuser&password=mypassword" for m3u

[aniel300]

ok let me test right now

[aniel300]

have u tried using ssl as well?

[euzu]

no, because i cant use port 443 on my router for testing. And using alternative port like 8443 does not work with letsencrypt.
i dont have a remote Server.

[aniel300]

ok. question why do i get this log for the internal user checking for the external target or the other way around? [2024-12-04T09:48:48Z DEBUG m3u_filter::model::api_proxy] checking user credentials on target internal for user external

[euzu]

it is a loop where all are checked, only a debug output what is checked.

[euzu]

i have added this for you, you can go back to release image. The beta image contains this test outputs.

[aniel300]

config should be like this right? api: {host: 0.0.0.0, port: 8901, web_root: ./web} idk what else to check

[euzu]

yes it is correct.
But why not test it first with caddy and without https. İf it works you know something is wrong with traefik config.

[euzu]

Or do not use caddy or trafik, first access m3u-filter on port 8901

[aniel300]

right now am bypassing traefik (am using my server public ip) and i still cant get it to play. am able to get the groups but not play

[aniel300]

Or do not use caddy or trafik, first access m3u-filter on port 8901

yes that is what am doing

[euzu]

when you use curl and get the playlist, what is inside the playlist?

[aniel300]

is using curl the same thing or similar as using a browser?

[euzu]

it prints the received content in console.

[euzu]

curl is a command-line tool and library used for transferring data to and from a server. It supports a wide range of protocols, including HTTP, HTTPS, FTP, SCP, SFTP, and more. The name stands for Client URL.

[aniel300]

i havent used it yet but with the browser if i go to http://xxx:8901/player_api.php?username=external&password=external i get {"user_info":{"active_cons":"0","allowed_output_formats":["ts","m3u8","rtmp"],"auth":1,"created_at":1701770943,"exp_date":1764842943,"is_trial":"0","max_connections":"1","message":"","password":"external","username":"external","status":"Active"},"server_info":{"url":"xxx","port":"8901","https_port":"443","server_protocol":"http","rtmp_port":"","timezone":"America/New_York","timestamp_now":1733306943,"time_now":"2024-12-04 05:09:03"}} and if go to http://xxx:8901/get.php?username=external&password=external i get what i would find inside a m3u file which looks as follow

#EXTM3U
#EXTINF:-1 tvg-id="123tv.de" tvg-name="DE| 123 TV" group-title=" DE | GERMANY" tvg-logo="http://myportal.live:8080/images/407b7ca2b0c98131d0e17cd3e510ab9a.png",DE| 123 TV (p:myportal)
http://xxx:8901/m3u-stream/live/external/external/1
etc

[euzu]

ok you have access to the server, you get the results as expected. Dou you have 2 outputs defibed on the target external?

[aniel300]

am yet to experiment with mapping

[euzu]

mapping is very powerful, you need to understand regexp captures

[aniel300]

am not yet ready to dive into it but am planning to learn it soon. however, i would like to fix this before

[euzu]

I thaught that it is working?

[aniel300]

yes some channels do work but not others

[euzu]

what channels? Ehat do they have in common. Are they all from same provider.?

Some providers look for header information.

[euzu]

m3u series on the fly is not supported by the m3u playlist. Its not a limitation from m3u-filter. It üs a limitation through m3u playlist itself.

[aniel300]

ok going to close this for the time being

[aniel300]

can u disable the extra logging for future betas?

[euzu]

it was temporary, i have removed it from the code. You can use the release image.

[aniel300]

i went back to m3u-filter-beta:2.0.10-beta because idk if the latest stable has all the new implementation from m3u-filter-beta:2.0.10-beta

[euzu]

the 2.0.10 has all implementations.

[aniel300]

right, that is what i figured. thank you for taking the time to ts with me and am sorry if i wasted ur time.

[euzu]

you are welcome,
If you like m3u-filter you can do some advertising for the project to gain a bigger user base.

[aniel300]

i will definitely do