Today I lost the ability for any Chromium based browser to communicate with my Tablo. Firefox, Roku, Windows App, IOS, Tablo Tools, etc. all work but Chrome, Edge, and Brave do not.
Does anyone else have similar issues?
Initially i dont see a problem 
Have you searched if its that “privat network” issue Chrome was going to do then delayed? That is if its been recently updated.
Try developers tools and watch the network traffic for a possible clue.
Same here with Brave. I seem to recall doing a restart to update yesterday.
1 Like
On a :cough,cough: Chromebook: Google Chrome: Version 106.0.5249.112 (Official Build) (64-bit)
I do have chrome://flags/#block-insecure-private-network-requests set to disabled, not sure if it’s actually relavent.
[Private Network Access update: Introducing a deprecation trial - Chrome Developers]
Oddly it had to sync as though it hadn’t connected for an unreasonably length of time. My “Startup Section:” - Remember Last instead went to default Primetime, and remote quality went back up to 1mb.
But otherwise worked, watched Live TV. Have you confirmed it’s not a Windows thing?
1 Like
Disabling that got Brave working…
1 Like
Disabling did the trick for me too - Thanks!
If others are having this problem this is the link you can paste into your browser to disable:
chrome://flags/#block-insecure-private-network-requests
@bbaorbb @FlyingDiver I can’t recall exactly why or when I set this - but I remember setting some “experiments” so figured I should check to pass it on… just in case. I believe it was around the time with the CROS (or similar lettering) issue arose.
I just used Chrome my my Debian Linux and it works, which also has this flag set/disabled. Again, it starts syncing and goes to the default Prime TV as though it was the first time loading.
…
biggest take-away, Firefox continues working without issue. Giant-data mining-corporation-controled browser, again has issues. 
I’ll 
be watching you 
_
I had my.tablotv.com opened in Firefox, clicked reload and it was uneventful - it reloaded as expected.
@TabloSupport @TabloEngineering @TabloTV any comment or input on this? Is there really “a problem” or did we just stumble across some blip?
'Tis but a blip.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.