I'm having a problem with Closed Captions on the Fubo VCL Bridge.
All the channels seem to work fine except two of them. Food Network and Travel Channel do not have CC when run through the VCL Bridge, but all of the other channels do have CC.
I also get CC on Food and Travel when I go through TVE.
What makes these 2 channels special?
Nothing makes these channels "special." The container simply provides what is shown in any web browser. When I went to fubo.tv in a web browser and went to Food Network it showed that "subtitles are not available." The next time after going back later subtitles were available, thus appears to be something on their side.
Keep in mind the stream from the docker comes from Fubo, while the TVE feed comes from discovery.com, so different feeds with different streams
Thanks for the explanation. I just checked, and the captions are back.
Was there a update on fubo? I can't seem to get it to stream but when I login to site it works.
Working as expected here.
The docker is working perfectly with the service.
Just replaced my Synology drives and fixed up my network configuration. Much nicer!!!
Unable to update container "/vlc-bridge-fubo": Error response from daemon: pull access denied for jgomez177/vlc-bridge-fubo, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
Message generated by watchtower overnight, has this project died?
It looks like @joagomez's repository is gone from Docker. I wonder if Fubo issued a C&D or takedown notice?
it's not on his github backup either... that's doesn't bode well
Unfortunately this is not a project that I will be able to continue/maintain moving forward. Hopefully someone will be able to take up the mantle. It’s been a great learning experience for me to get it to what it is
Does anyone know if the current instances will quit working soon? I have virtual NAS DRM instance that I fired up and I can't get that version of Fubo Project to work (worked previously when I last used it in January). I can access it via http://IP:7777 and it shows the HLS and MPEG links, but when I try and access that iteration I get
2024/04/28 18:40:28.814948 [ERR] Failed to start stream for ch9003: M3U: Could not fetch playlist from 192.168.0.9:7777: GET: http://192.168.0.9:7777/fubo/watch-hls/20450: 500 INTERNAL SERVER ERROR
2024/04/28 18:40:28.832772 [HLS] Couldn't generate stream playlist for ch9003-dANY-ip192.168.0.91: M3U: Could not fetch playlist from 192.168.0.9:7777: GET: http://192.168.0.9:7777/fubo/watch-hls/20450: 500 INTERNAL SERVER ERROR
Look at the Fubo Project docker log
THis is the only thing I see when looking at logs for this particular docker.
Also, logged into my mom's mountain cabin where I have a DVR setup and am having the same problem accessing channels. She's not up there currently, but this thorws a big wrench in my setup if FuboTV Project is discontinued as I rely on that to pull in NBC and FOX (she can't get OTA where she is in the mountains). 
Is Channels DVR able to get the lineup and display the channels?
Yes, I installed a Channels Server on the Virtual NAS and was able to import it in using Custom Channels. But whenever I go to access one of the channels, I get the above error.
What's odd is my regular server I am able to still access all the channels from Fubo Project (local instance of Fubo Project). But the virtual version of Fubo Project and now my mom's cabin are both offline. Only thing I can think of is that they haven't been used in the last 30 days (the virtual has been more like 4 months). I checked and both have the correct username and password.
OK, sorry I can't help any further since I no longer use Fubo.
When I used it with the HLS playlist it worked fine.
There is also a note somewhere in this thread about your docker PC needing an allowed IP address Internet IP). From my notes;
CHECK YOUR IP
so you can try a couple of things to verify your IP:
from the device hosting your docker run a simple curl command to verify your IP:
curl "https://api.fubo.tv/v3/location"
you'll receive an output similar to the following from the API that tells you if your network is allowed
{
"postal":"XXXXX",
"dma":"XXX",
"country_code":"USA",
"country_code2":"US",
"country_name":"united states",
"region_code":"XX",
"connection_type":"XXX",
"asn":"XXX",
"as_name":"XXX",
"ip_address":"XXX.XXX.XXX.XXX",
"display_name":"XXXXXXXX",
"network_allowed":true
}
You can also run this directly from the docker however curl is not loaded by default:
docker exec -it vlc-bridge-fubo ash
apk --no-cache add curl
curl "https://api.fubo.tv/v3/location"
If the network_allowed address is false, then Fubo believes you are behind a VPN
Updated my last post above this one.
Check the IP from your Virtual NAS Network at the cabin using https://api.fubo.tv/v3/location
See his post about the geo-location and HLS vs MPEG-TS playlists
Thanks @chDVRuser. I had already checked the Curl command and all was good on that front. The cabin issue was that the Docker was not active for some reason, but restarting it fixed that issue.
The virtual NAS was able to be resolved when switching to MPEG source vs. HLS. It's odd because the virtual server is all self-contained (same IP address for the Test Channels DVR Server and the Test FuboTV Project Docker).
Crossing my fingers that the Devs ( @tmm1, @maddox and @eric ) consider adding this solution within the server itself vs. a stand-alone source. Granted I know nothing about what that entails, but if possible, would be the most seamless solution outside of HDHR Tuner and TVE (and the 2nd best solution to get Fox and NBC into the server).
Crossing fingers.
