Okay, it got farther along this morning. It wants to do a channel scan, but it finds no channels. I know the antenna works, because if I connect it directly to my TV, it works fine. I know the Tablo is connecting to the network because the app finds it fine.
Mine is working again on Roku and iOS.
Mine also working again on Roku and iOS. I wish the IT guys could explain what the heck is going on and when it will get fixed!
No. Stuck on the connecting screen for 2 days. Since the updates to the Tablo app, firmware, and Roku all had been working well. I was even headed to Best Buy to get a couple for Xmas gifts. Now itâs SNAFU.
This is not a good look for Tablo to fail 2 days in a row right before Xmas when people may be thinking of getting Tablos for gifts. I encountered the failure yesterday (Saturday) but I did not use Tablo today until after the server failure had resolved itself. Letâs see what happens tomorrow morning.
Iâm having second thoughts about getting one for my mother-in-law because now sheâs going to think I donât like her.
This is actually the 3rd day in a row that this has happened to me.
Grateful for this page and everyoneâs posts. You saved me a tear down of my home network (thinking it was local to me) and gave me moral support. My symptoms:
-
Began Friday Dec 19 in early AM hours and persisted apparently two days, hopefully solved now
-
Roku Tablo app remained completely unavailable at stuck screen of âConnecting to your Tabloâ with no workaround
Began to regret applying the new Tablo firmware the day prior to both my 4th Gen, 4 Tuner Tablos, thinking maybe the new firmware was at fault. After all, weâd already suffered a prolonged September outage for related back-end server offline fail. Why isnât that ticketâs patched solution helping us now?, I wondered.
Some with years of familiarity with app architecture may ask: What goal exactly are Tablo engineers seeking to solve for us end users, by forcing Tablo to phone home to server central before it allows a locally authenticated LAN client to access a local LAN DVR page? I might naively not recognize some security need that redundantly adds the burden of a fresh client authentication from server central but, clearly itâs not about monetization since weâre not paying a subscription fee, no monetary reason to require us to remotely authenticate each time we launch Tablo on Roku. Hope engineers recognize how vulnerable it is for in-home authenticated customers to not access our in-home hosted DVR.
Years ago, TiVo (by analogy) required in-home DVRs to connect back to a TiVo server each time the user in their livingroom tried to open a TiVo folder to select an in-home recording. That phone-home task and requirement were invisible to us end users until a bug in TiVo server connectivity suddenly prevented us from opening and viewing our in-home recordings, just hour-glassing instead. Eventually a fix rolled out or at least, the problem went away. Different in-home connectivity (TiVo was HDMI connected, not LAN connected, to TV or AVR) but TiVo forum participants, suffering prolonged, repeated fails that required this phone-home task, recognized TiVoâs client connectivity demands were simply overthought, needing a rethink.
Monday morning, my Tablo app opened just fine on at least two of my TVs! Havenât tried the others yet, but the last few days it was an all or nothinâ situation.
Well, the information collected is probably sold to the highest bidder. Nothingâs free these days!!!
The app is opening fine for me now, but now it just wonât play live TV. Iâm assuming playback will be much the same. Itâs like the Tablo is having problems processing and rendering the live TV signal.
Hi @BulletMagnetEd ,
Sorry youâre running into that.
If you havenât already, try the following:
- Reboot your Tablo and then close the app and relaunch it.
- If that fails, run a rescan. The key part of this is saving after rescanning.
These might resolve the issue.
@TimeComes , @Steve_McNally , @Rzy
Just to double-check, are you still not able to connect?
It was working for me again last night and this morning.
I keep getting an error after I pass the location screen then it find my zip code and then throws a failed to load network error. Connect to Ethernet and wifi just fine then to this spot every time it fails.
There have been some technical issues earlier today.
Contact them here:
Have you tried it today? Yesterday was a disaster.
I got past the ZIP code search today, but now it only goes to the Channel scan step. Then, it doesnât find any channels.
Any luck with this error? I am also a new user and see the same error Ethernet or WiFi trying to register in both an iPad and iPhone. (Private relay is off.)
The device was initially able to download firmware, and I still see it registering on my DHCP server after multiple resets, so I know it is getting an IP address.
I put in a ticket with support but have yet to hear anything back.
It still doesnât find any channels for me, unfortunately. If I had cable instead of OTA, Iâd be using my old HTPC with Windows 10 on it. That never gave me any problems, and I could upgrade it whenever I wanted.
