Heya, keep in mind this push is automatic to http://my.tablotv.com/ - if you check the ‘About’ section at the bottom of the Settings page, it should read HTML Application: 1.0.27.
Working just fine in Safari, but will not connect to the Tablo in the Safari Technology Preview. This isn’t a necessity I just wanted to let you know @TabloSupport@TabloTV
Not sure what is happening, my.tablotv.com is in a connecting loop. Click to live tv and see the guide fine, spinning circle on top with the word connecting…
Macbook Pro, tried with Chrome and Safari with same results
The new revision is not connecting to my Tablo, yet the beta site given to me a few weeks ago (to fix sound sync issues) still connects and functions OK. Not quite sure what is causing the hang up here?
http:// is what I’ve been using. I tried https:// and it doesn’t get quite as far, instead of the prime time page I get a blue bar across the top with Tablo and a spinning circle and connecting on the middle of the page.
For the Safari Tech Preview, it appears that there’s a newly enforced Content-Security-Policy for websocket connections. Easy fix, but I’d like to hear from MS Edge users. Can you check the console logs and see if the error when connecting looks like this: Refused to connect to ‘ws://X.X.X.X’ because it violates the following Content Security Policy directive: “default-src * data: blob:”. Note that ‘connect-src’ was not explicitly set, so ‘default-src’ is used as a fallback.
Apologies for the technical jargon – I’m hoping for some of the advanced users to chime in.
I have tried it both ways. Using the non-secure HTTP:// all I get is the “connecting…” and spinning wheel. If I use the secure HTTPS:// approach, it picks up the name of my Tablo (Monarch Tablo) and attempts to connect. The first pass takes about 25 seconds; subsequent passes time out after just a few seconds (5-8).
The previous beta address (given to me to test out the audio sync fix in Chrome) still works fine.
It’s trying to establish a websocket connection to the Tablo device (not a Nuvyyo server), but fails. Thanks for the error message, I’ll dig that one up.