Fios - Scanning Channels Hung Up

Channels DVR Server TV Everywhere
#1

First time installing. Using Unraid Docker. Trying to setup TV Everywhere... So far the experience has been not good.. I have FIOS... put in my creds...and it just sat there trying to authenticate.. stopped it, restarted... tried again.. took about 3 tries but eventually it logged in... got to about 78 channels and it got hung up... stop it again...took another 3 tries... this time got to 136 channels and got hung up...

Is this normal...does it usually hang on a certain channel for 10-15 min..it seem to scan through the other channels very fast..

Thanks

#2

Some channels can take a while, but it should not be getting stuck. When you say you stopped and restarted, what exactly are you doing? Reinstalling the docker from scratch?

#3

No...Just restarting the Docker container..

#4

Can you open another browser, then check the DVR Log to see if it is still scanning. It is possible the live update is not working.

It is also worth upgrading to prerelease, by clicking the dropdown next to Check for Update and selecting the second option.

#5

Here are the last few lines of the log... At the moment the FIOS login is just spinning, doesn't log in...

2021/03/01 20:35:06.863693 [TVE] action=wait_for_page
2021/03/01 20:35:06.960380 [TVE] action=request type=Document method=GET url=https://ssoauth.verizon.com/sso/choice/tvpHandler.jsp
2021/03/01 20:35:07.838918 [TVE] action=request type=Document method=POST url=https://sp.auth.adobe.com/sp/saml/SAMLAssertionConsumer
2021/03/01 20:35:07.861399 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/completePassiveAuthentication
2021/03/01 20:35:07.861535 [TVE] action=authed
2021/03/01 20:35:07.861669 [TVE] action=wait_for_page done=true reason=auth_finished
2021/03/01 20:35:07.862625 [TVE] action=cookies num_domains=2 num_cookies=28
2021/03/01 20:35:07.863558 [TVE] action=error_response type=Document error=net::ERR_ABORTED
2021/03/01 20:35:07.863773 [TVE] action=error_response type=Document error=net::ERR_ABORTED

#6

It's supposed to show you what channel is being scanned. What browser are you using to set it up?

#7

I'm using Edge...The last time it tried to scan it got hung up on channel 136: Here are the logs from that point:

2021/03/01 20:15:23.680552 [TVE] Channel scan 128/206 NFL failed: notAuthorized
2021/03/01 20:15:23.699864 [TVE] Channel scan 129/206 MLBTV failed: notAuthorized
2021/03/01 20:15:23.718554 [TVE] Channel scan 130/206 CBSSPORTS failed: notAuthorized
2021/03/01 20:15:23.737714 [TVE] Channel scan 131/206 FS1 failed: notAuthorized
2021/03/01 20:15:23.756319 [TVE] Channel scan 132/206 FS2 failed: notAuthorized
2021/03/01 20:15:23.775104 [TVE] Channel scan 133/206 BTN failed: notAuthorized
2021/03/01 20:15:23.794503 [TVE] Channel scan 134/206 DEPORTES failed: notAuthorized
2021/03/01 20:15:23.831722 [TVE] Channel scan 135/206 FS-SOCCERPLUS failed: notAuthorized

#8

I finally was able to log in and it again go to channel 135 now: Here are the current logs:

021/03/01 20:43:51.762098 [TVE] Channel scan 128/206 NFL failed: notAuthorized
2021/03/01 20:43:51.781692 [TVE] Channel scan 129/206 MLBTV failed: notAuthorized
2021/03/01 20:43:51.800145 [TVE] Channel scan 130/206 CBSSPORTS failed: notAuthorized
2021/03/01 20:43:51.819823 [TVE] Channel scan 131/206 FS1 failed: notAuthorized
2021/03/01 20:43:51.838191 [TVE] Channel scan 132/206 FS2 failed: notAuthorized
2021/03/01 20:43:51.859198 [TVE] Channel scan 133/206 BTN failed: notAuthorized
2021/03/01 20:43:51.882714 [TVE] Channel scan 134/206 DEPORTES failed: notAuthorized
2021/03/01 20:43:51.901881 [TVE] Channel scan 135/206 FS-SOCCERPLUS failed: notAuthorized
2021/03/01 20:43:52.230942 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME
2021/03/01 20:43:52.231875 [TVE] action=navigate url=https://api.auth.adobe.com/api/v1/authenticate?reg_code=XXNRSRB&mso_id=Verizon&domain_name=adobe.com&requestor_id=fs2go&noflash=true&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2021/03/01 20:43:52.232424 [TVE] action=request type=Document method=GET url=https://api.auth.adobe.com/api/v1/authenticate
2021/03/01 20:43:52.371335 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/api/v1/authenticate
2021/03/01 20:43:52.442384 [TVE] action=request type=Document method=GET url=https://ssoauth.verizon.com/sso/VOLPortalLogin
2021/03/01 20:43:52.442559 [TVE] action=auth_domain domain=ssoauth.verizon.com
2021/03/01 20:43:53.471379 [TVE] action=wait_for_page
2021/03/01 20:43:53.567934 [TVE] action=request type=Document method=GET url=https://ssoauth.verizon.com/sso/choice/tvpHandler.jsp
2021/03/01 20:43:54.780723 [TVE] action=request type=Document method=POST url=https://sp.auth.adobe.com/sp/saml/SAMLAssertionConsumer
2021/03/01 20:43:54.910175 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/completePassiveAuthentication
2021/03/01 20:43:54.910243 [TVE] action=authed
2021/03/01 20:43:54.910317 [TVE] action=wait_for_page done=true reason=auth_finished
2021/03/01 20:43:54.911621 [TVE] action=cookies num_domains=3 num_cookies=39
2021/03/01 20:43:54.912873 [TVE] action=error_response type=Document error=net::ERR_ABORTED

#9

Logs dumps here are not useful. Please click Support > Submit Diagnostics and email support and we can have a closer look at what's going on.

#10

Okay. Will do. Thanks

#11

Did you ever get this worked out? As I am having the same issues.

#12

On Unraid Docker using Fios?
Did you try the latest prerelease version?