Up graded google-chrome-beta from 91.0.4472.77-1to 92.0.4515.51-1 my.tablotv.com now just has the perpetual connecting rotating circle. I understand it’s a beta channel… but it’s on the way.
Thought my tablo was flubbed up (or ad/tracking blocking - all disabled). Yes cleared all site data and reset settings.
Loads in Firefox [beta] 90.0b6 | Google-Chrome 91 [stable] | Pale Moon 29 (forked from Mozilla’s Gecko).
Also dos not load in Microsoft Edge Dev Build 93 (again not a stable release).
Almost all areas have ended the various lock downs.
When possible almost everyone has come out of their caves into the sunshine and fresh air and resumed living like humans. Employees might have actually gone back to their normal work.
Correct… however it’s the Chrome 92 BETA that is causing the Tablo issue. Every earlier version of Chrome works fine.
Also, the OP states that it does not work with Microsoft Edge Dev Build 93 either; so yes, they are fundamentally the same. Beta=bad for Tablo, for now. lol
Actually Firefox works great for tablo, just have to spread things out. In the days of flash and DRM some streaming didn’t work in Firefox, so I just have Chrome opened for Amazon Video, and a tab for tablo.
I have not tried Chrome 92, but Chrome 91 is giving an issue notice, that clearly indicates there will be an issue when it is released to stable:
A site requested a resource from a network that it could only access because of its users’ privileged network position. These requests expose devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack, and/or information leakage.
To mitigate these risks, Chrome deprecates requests to non-public subresources when initiated from non-secure contexts, and will start blocking them in Chrome 92 (July 2021).
To fix this issue, migrate the website that needs to access local resources to HTTPS. If the target resource is not served on localhost, it must also be served on HTTPS to avoid mixed-content issues.
Given the (near) impossibility of trusted HTTPS on private / home networks, I suspect this change is going to cause a number of issues, not just for Tablo.
Using Chrome so little, I can access my router, by name or IP via HTTP no S - but is does not have mixed and access directly. Thought maybe it was an HTTPS only forced setting.
So maybe tablo can suggest user take up FIrefox and tweak their filters, screen and features to work with a browser which works with their device
There is probably a reason to not always automatically upgrade like a bunch of lemmings committing mass suicide. Especially since the CSRF has been around since at least 2001.
…or maybe tablo with load the “webapp.js” on the tablo and use it’s internal web server - so it could then be access without the need for internet! woohoo!
Other companies selling devices, advertised as accessible via browser - but suddenly not supporting browser access. Chrome is “recommended” and, currently, tablo is accessible via other browsers (for now).
If they come out with a “company app” for the devices sold to users relying on the web app? …or discontinue web app and obsolete access?
Nuvyyo has been and likely continue to be a leader, not a follower with DVR technology and the industry.
Ever use the Kasa(tp-link), Wyze, Alexa, Blink, etc app in a browser? Many of these don’t even have a stand alone PC app.
There are even companies with mobile apps that have deprecated various OS versions leaving a legacy app with no future features, enhancements or supporting new products.
Yes, off to another pointless off topic posting… tp-link, never had it, knew it up front. Alexa, try alexa.amazon.com . Data collection works best with proprietary software, it’s no secret. If you want to know when someone comes and goes from their house daily, you need control.
I’m aware of engineered obsolesce and companies, devices and technologies becoming defunct. Not functioning with one vendor’s browser doesn’t render tablo useless for PC users… who purchased it with that purpose.
