6 hours ago, alturismo said:

ok, tested here and working fine

 

as you see it also shows here 34400 on both in dash, while one is running on 34400 and the other on 34401

 

from the VPN terminal console, you see the 2 listeners ...

 

here the webgui's

 

so basically, your setup is looking fine, but somewhere must be something ... i can only confirm this way works as expected.

 

Delete everything, start from 0.

Doesnt working either.

 

Open passthroughtVPN, and watch configs, and needed to add new port there. 🤦🏼‍

 

many thanks @alturismo for make you loose time with this, and for your hard work!

My guide2go docker failed this morning, reporting hundreds of lines of:

 

[ERROR] Could not find requested programID. [SD API Error Code: 6000] Program ID: EP00003986

 

Any idea what could cause this?

3 hours ago, mihcox said:

Any idea what could cause this?

this is pretty sure not the g2g helpdesk  but to give a starter

 

3 hours ago, mihcox said:

[SD API Error Code: 6000] Program ID: EP00003986

SD schedules direct ... may just had a hickup, may try to a different time or run it manually in the xteve console

 

 

3 hours ago, mihcox said:

Program ID: EP00003986

or may this program is just moved, deleted, ... from SD lineup

 

as test if this is always happening with the same id, may edit your yaml and remove this one channel from your lineup to cross check and see what happens then ...

13 hours ago, alturismo said:

this is pretty sure not the g2g helpdesk  but to give a starter

 

SD schedules direct ... may just had a hickup, may try to a different time or run it manually in the xteve console

 

 

or may this program is just moved, deleted, ... from SD lineup

 

as test if this is always happening with the same id, may edit your yaml and remove this one channel from your lineup to cross check and see what happens then ...

Thanks for the assistance, just wanted to make sure guide2go itself wasn't causing the issues. I recreated a new yaml with the same info, and it seemed to work so unsure but working now.

 

Thanks again.

Does OVPN_Privoxy support routing other containers through its VPN?  I tried setting it up the same way I do for Binhex-SABnzbdVPN container with ADDITIONAL_PORTS variable and the port of the routed container but I cant seem to access the webUI.  If I switch the routed container back to Binhex-SABnzbdVPN it works but wont work with OVPN_Privoxy.  If it is supported, do I need to change anything?

1 hour ago, Aegisnir said:

If it is supported, do I need to change anything?

just map the ports in ovpn_privoxy

 

 

Hi, I just came back after 2 years. I used to have the xteve_zap docker using zap2it.

 

Why was it removed? What is the alternative now? Seems to be Schedules Direct with Guide2Go, but I'd rather not have to pay for the access.

1 hour ago, matmat07 said:

Why was it removed? What is the alternative now?

as the developer of zap doesnt like his app to be spreaded by others i removed it to respect him.

I'm using the plain vanilla xTeve docker... I'm pretty sure I have it all set up and working.  Curious to know if there is a way to have it buffer to the RAM rather than the drive the docker is installed too.  Just looking for any kind of performance boost I can get.

1 hour ago, hansolo77 said:

Curious to know if there is a way to have it buffer to the RAM rather than the drive the docker is installed too.

of course, like with any other docker just map /tmp/xteve > to your RAM, there are different opinions howto, i personally use subdirs in /dev/shm/ on the host therefore and map them.

 

sample on Unraid, user script to create my subdirs, i chown & chmod just to make sure they always work

 

/dev/shm/ as it results in max 1/2 Ram usage

 

docker mount

 

result

 

there are several tutorials in this forum, mainly when you look for plex transcode to Ram

I see.. Thanks!

 

I'm having another problem now that's actually more frustrating.  When I load up Plex and look at my guide, some of shows have the actual show art, where others are just like a screenshot grab of a character.  How do I fix that?

18 minutes ago, hansolo77 said:

When I load up Plex and look at my guide

what guide are you using ?

1 minute ago, alturismo said:

what guide are you using ?

 

I have 2 set up.  One is with dizqueTV and the other is OTA which grabs guide data from zap2it.

 

Just now, hansolo77 said:

I have 2 set up.  One is with dizqueTV and the other is OTA which grabs guide data from zap2it.

 

then i would look there and / or Plex Forums for your issues therefore, has nothing really todo with xteve and unraid

 

check your xml guide if it even has the data you would like to see and report in Plex Forums why its ignored (iof its in the xml included), this would be my approach now.

Sorry, it must be because it's 12:30am here.. I'm totally lost lol.  This whole thing is new to me.

Ok, now that I'm more awake, I figured out the problem.  Zap2It was not providing proper artwork.  When I went back to the website and clicked on various shows that were missing artwork in Plex, they were also missing in the Zap2It website.  So now I have to rethink the source.  Is there a popular recommendation?  For my needs, obviously I'm using Unraid and Plex.  xTeve is running in a docker.  I would prefer a "set up once and forget about it" automated system.

updated g2g Version coming now included for SD users to get program posters back.

 

need some manual hands'on, rename the cronjob.sh, the docker will generate a new one, redo your settings, either proxy pictures only or cache them locally, to start i would recommend to set 1 Poster size depending on your wish, SD has a 5k daily (24h) limit.

 

here a sample for Plex users, 2x3

 

 

here the final result with posters again (well, almost all )

 

 

Hi all.

 

Anyone had issues connecting to channels with the Xteve buffer active today?

 

Channels work fine as soon as I turn the buffer off or switch it to FFMPEG. any recommendations as to what could be causing the issue?

 

I assume the VPN part only works with the Xteve buffer and not FFMPEG or VLC?

Edited March 11, 20233 yr by enigma27

27 minutes ago, enigma27 said:

I assume the VPN part only works with the Xteve buffer and not FFMPEG or VLC?

depends what "VPN Part" you mean, actually any buffer will work the same way ... xteve, ffmpeg, vlc ...

 

so, in terms you use xteve behind a VPN Client, yes, all will work then.

 

29 minutes ago, enigma27 said:

Anyone had issues connecting to channels with the Xteve buffer active today?

 

and as there where no changes, i would suggest you rather look at your source, changes prolly came from there.

6 minutes ago, alturismo said:

depends what "VPN Part" you mean, actually any buffer will work the same way ... xteve, ffmpeg, vlc ...

 

so, in terms you use xteve behind a VPN Client, yes, all will work then.

 

and as there where no changes, i would suggest you rather look at your source, changes prolly came from there.

 

when I say VPN part I am talking about he quote from the author says "the buffer must be active otherwise the VPN is obsolete" but it doesn't say which buffer... is it specifically the Xteve buffer or will it still work with the FFMPEG buffer or VLC buffer.

 

Secondly as stated in my post channels work fine with the following

• Buffer set as FFMPEG
• Buffer set as VLC
• No buffer active

How can it possibly be the source?

 

Here is what the log says when trying to connect to a channel with Xteve buffer active and others

 

FFMPEG buffer - Works

 

2023/03/11 16:20:36 [xTeVe] Streaming Status:       Playlist: M3U - Tuner: 1 / 1
2023/03/11 16:20:36 [xTeVe] Streaming Status:       Buffering data from FFMPEG
2023/03/11 16:21:11 [xTeVe] Buffer:                 true [ffmpeg]
2023/03/11 16:21:11 [xTeVe] Buffer Size:            4096 KB
2023/03/11 16:21:11 [xTeVe] Channel Name:           Hub Premier 1 FHD
2023/03/11 16:21:11 [xTeVe] Client User-Agent:      VLC/3.0.18 LibVLC/3.0.18
2023/03/11 16:21:11 [xTeVe] Streaming Status:       Client has terminated the connection
2023/03/11 16:21:11 [xTeVe] Streaming Status:       Channel: Hub Premier 2 FHD (Clients: 0)
2023/03/11 16:21:11 [xTeVe] Streaming Status:       Playlist: M3U - Tuner: 1 / 1
2023/03/11 16:21:11 [xTeVe] FFMPEG path:            /usr/bin/ffmpeg
2023/03/11 16:21:11 [xTeVe] Streaming URL:          xxxxxxx
2023/03/11 16:21:11 [xTeVe] FFMPEG:                 Processing data
2023/03/11 16:21:11 [xTeVe] Streaming Status:       Receive data from FFMPEG
2023/03/11 16:21:12 [xTeVe] FFMPEG log:             [h264 @ 0x146f74e09780] non-existing SPS 0 referenced in buffering period
2023/03/11 16:21:12 [xTeVe] Streaming Status:       Buffering data from FFMPEG
2023/03/11 16:21:12 [xTeVe] Streaming Status:       Channel: Hub Premier 2 FHD - No client is using this channel anymore. Streaming Server connection has ended

 

and when Xteve buffer sent - Not Working

 

2023/03/11 16:33:59 [xTeVe] Buffer:                 true [xteve]
2023/03/11 16:33:59 [xTeVe] Buffer Size:            4096 KB
2023/03/11 16:33:59 [xTeVe] Channel Name:           Hub Premier 10 FHD
2023/03/11 16:33:59 [xTeVe] Client User-Agent:      VLC/3.0.18 LibVLC/3.0.18
2023/03/11 16:34:00 [xTeVe] Streaming Status:       Playlist: M3U - Tuner: 1 / 1
2023/03/11 16:34:00 [xTeVe] Streaming Type:         [TS]
2023/03/11 16:34:00 [xTeVe] Streaming URL:         xxx
2023/03/11 16:34:03 [xTeVe] Streaming Status:       HTTP Response Status [200] OK
2023/03/11 16:34:03 [xTeVe] Content Type:           
2023/03/11 16:34:03 [xTeVe] Content Type:           
2023/03/11 16:34:03 [xTeVe] [ERROR] Streaming error (Server sends an incompatible content-type) - EC: 4003
2023/03/11 16:34:03 [xTeVe] Streaming Status:       Client has terminated the connection

 

 

4 minutes ago, enigma27 said:

but it doesn't say which buffer...

 

20 minutes ago, alturismo said:

so, in terms you use xteve behind a VPN Client, yes, all will work then.

 

no sense to say which buffer works as ALL are working the same way  so yes, doesnt matter, the traffic just needs to run through the xteve docker which is then settled behind the VPN,

 

No Buffer just passes the source link to the client, so xteve is then "out of the chain" and thats why i say, no buffer = VPN obsolete ... i hope this makes it clearer for you.

 

5 minutes ago, enigma27 said:

How can it possibly be the source?

 

well, if all buffers would work exactly the same in terms of demuxing / remuxing we wouldnt need more then one

 

51 minutes ago, enigma27 said:

Anyone had issues connecting to channels with the Xteve buffer active today?

 

like this i have to assume it worked before "today", so, no change in xteve buffer lately, i asume your source stream changed and thats why you had to change to ffmpeg or vlc ... lets say as sample some HLS stream format, whatever your provider does ...

 

you see the error here

9 minutes ago, enigma27 said:

2023/03/11 16:34:03 [xTeVe] [ERROR] Streaming error (Server sends an incompatible content-type) - EC: 4003

 

ffmpeg and vlc are more "powerful" and can handle more input formats, while the xteve framebuffer is a bit faster overall ... but in the end, stay with ffmpeg if that works for you, my personal suggestion in your case now.

ok perfect thank you

 

Now i know the VPN works with other buffers I will just swap those out... Thank you

Has anyone upgraded to 6.12 rc2 and had success with this running? Just curious since it hasn't been updated in a while? I'm assuming it should still work fine, but wanted to check in with everyone else. 

2 minutes ago, sross44 said:

Has anyone upgraded to 6.12 rc2 and had success with this running? Just curious since it hasn't been updated in a while? I'm assuming it should still work fine, but wanted to check in with everyone else. 

1st, i wonder why these questions are coming at all ...

 

1/ you can easily rollback anytime ...

2/ you are just to lazy to check yourself and rather depend on others ...

3/ dockers are "own" systems which doesnt really rely on the host updates ....

 

and yes, its running like before and before and before ...

I keep getting a "Locked 423" error while trying to configure an OTA channel using Xteve-guide2go. I'm also having problems getting SD to give me a listing of channels, but that might be secondary issue.

 

2023/03/26 16:51:45 [G2G  ] Version: 1.1.3
2023/03/26 16:51:45 [URL  ] https://json.schedulesdirect.org/20141201/token
2023/03/26 16:51:46 [SD   ] Login...OK

2023/03/26 16:51:46 [URL  ] https://json.schedulesdirect.org/20141201/status
2023/03/26 16:51:46 [SD   ] Account Expires: 2023-04-02 00:42:37 +0000 UTC
2023/03/26 16:51:46 [SD   ] Lineups: 1 / 4
2023/03/26 16:51:46 [SD   ] System Status: Online [No known issues.]
2023/03/26 16:51:46 [G2G  ] Channels: 0
2023/03/26 16:51:46 [URL  ] https://json.schedulesdirect.org/20141201/lineups/USA-YTBE753-DEFAULT
2023/03/26 16:51:46 [G2G  ] Download Schedule: 14 Day(s)
2023/03/26 16:51:46 [G2G  ] Download Program Informations: New: 0 / Cached: 0
2023/03/26 16:51:46 [G2G  ] Download missing Metadata: 0
2023/03/26 16:51:46 [G2G  ] Create XMLTV File [/guide2go/TVguide.xml]
2023/03/26 16:51:46 [G2G  ] Clean up Cache [/guide2go/TVguide_cache.json]
2023/03/26 16:51:46 [G2G  ] Deleted Program Informations: 0
2023/03/26 16:51:46 [G2G  ] Version: 1.1.3
2023/03/26 16:51:46 [URL  ] https://json.schedulesdirect.org/20141201/token
2023/03/26 16:51:47 [SD   ] Login...OK

2023/03/26 16:51:47 [URL  ] https://json.schedulesdirect.org/20141201/status
2023/03/26 16:51:47 [SD   ] Account Expires: 2023-04-02 00:42:37 +0000 UTC
2023/03/26 16:51:47 [SD   ] Lineups: 1 / 4
2023/03/26 16:51:47 [SD   ] System Status: Online [No known issues.]
2023/03/26 16:51:47 [G2G  ] Channels: 0
2023/03/26 16:51:47 [URL  ] https://json.schedulesdirect.org/20141201/lineups/USA-YTBE753-DEFAULT
2023/03/26 16:51:47 [G2G  ] Download Schedule: 7 Day(s)
2023/03/26 16:51:47 [G2G  ] Download Program Informations: New: 0 / Cached: 0
2023/03/26 16:51:47 [G2G  ] Download missing Metadata: 0
2023/03/26 16:51:47 [G2G  ] Create XMLTV File [/guide2go/SATguide.xml]
2023/03/26 16:51:47 [G2G  ] Clean up Cache [/guide2go/SATguide_cache.json]
2023/03/26 16:51:47 [G2G  ] Deleted Program Informations: 0
2023/03/26 16:51:47 [G2G  ] Version: 1.1.3
2023/03/26 16:51:47 [URL  ] https://json.schedulesdirect.org/20141201/token
2023/03/26 16:51:47 [SD   ] Login...OK

2023/03/26 16:51:47 [URL  ] https://json.schedulesdirect.org/20141201/status
2023/03/26 16:51:47 [SD   ] Account Expires: 2023-04-02 00:42:37 +0000 UTC
2023/03/26 16:51:47 [SD   ] Lineups: 1 / 4
2023/03/26 16:51:47 [SD   ] System Status: Online [No known issues.]
2023/03/26 16:51:47 [G2G  ] Channels: 0
2023/03/26 16:51:47 [URL  ] https://json.schedulesdirect.org/20141201/lineups/USA-YTBE753-DEFAULT
2023/03/26 16:51:48 [G2G  ] Download Schedule: 14 Day(s)
2023/03/26 16:51:48 [G2G  ] Download Program Informations: New: 0 / Cached: 0
2023/03/26 16:51:48 [G2G  ] Download missing Metadata: 0
2023/03/26 16:51:48 [G2G  ] Create XMLTV File [/guide2go/Echoguide.xml]
2023/03/26 16:51:48 [G2G  ] Clean up Cache [/guide2go/Echoguide_cache.json]
2023/03/26 16:51:48 [G2G  ] Deleted Program Informations: 0
XTeve API
Before
Locked [423]
http://10.0.30.11:34400/api/
Locked [423]

 

Based on my rudimentary debugging, the Locked 423 seems to be occurring when the update xteve via API subroutine is called in the cron job. Ignore the weird entries above. I was using echo commands to try and figure where the code was breaking.

 

Do you have any idea what might be happening here?