github euzu/tuliprox v2.2.3

latest releases: v3.2.0, v3.1.8, v3.1.7...
9 months ago

2.2.3

  • variable resolving for config files now for all settings
  • hls reverse proxy implemented
  • dash redirect implemented (reverse proxy not supported)
  • !BREAKING CHANGE! channel_unavailable_file is now under custom_stream_response,
  • New custom streams user_connections_exhausted and provider_connections_exhaustedadded.
custom_stream_response:
  channel_unavailable: /home/m3u-filter/resources/channel_unavailable.ts
  user_connections_exhausted: /home/m3u-filter/resources/user_connections_exhausted.ts
  provider_connections_exhausted: /home/m3u-filter/resources/provider_connections_exhausted.ts
  • input alias definition for same provider with same content but different credentials
- sources:
- inputs:
  - type: xtream
    name: my_provider
    url: 'http://provider.net'
    username: xyz
    password: secret1
    aliases:
    - name: my_provider_2 
      url: 'http://provider.net'
      username: abcd
      password: secret2
  targets:
  - name: test

Input aliases can be defined as batches in csv files with ; separator.
There are 2 batch input types xtream_batch and m3u_batch.
XtreamBatch:

- sources:
- inputs:
  - type: xtream_batch
    url: 'file:///home/m3u-filter/config/my_provider_batch.csv'
  targets:
  - name: test
#name;username;password;url;max_connections;priority
my_provider_1;user1;password1;http://my_provider_1.com:80;1;0
my_provider_2;user2;password2;http://my_provider_2.com:8080;1;0

M3uBatch:

- sources:
- inputs:
  - type: m3u_batch
    url: 'file:///home/m3u-filter/config/my_provider_batch.csv'
  targets:
  - name: test
#url;max_connections;priority
http://my_provider_1.com:80/get_php?username=user1&password=password1;1;0
http://my_provider_2.com:8080/get_php?username=user2&password=password2;1;0

The Fields max_connections and priorityare optional.
max_connections will be set default to 1. This is different from yaml config where the default is 0=unlimited

  • added two options to reverse proxy config forced_retry_interval_secs and connect_timeout_secs
    forced_retry_interval_secs forces every x seconds a reconnect to the provider,
    connect_timeout_secs tries only x seconds for connection, if not successfully starts a retry.

Don't miss a new tuliprox release

NewReleases is sending notifications on new releases.