Appears that if I can get headless-chrome updated to v109 on this Synology Package installation it would work. Only problem is it won't update chrome past v97.
I spun up a new updated TVE Docker Container that uses chrome v109 and it was able to authenticate local Fox, FS1 and FS2.
I lost FOX as well on FIOS. Any updates?
@mstras Server update resolved the original complaint from this thread. Make sure your server has updated and then I would suggest toggling the “experimental local tve” check box on the web ui off and then back on during prime time shows or national broadcasts.
I am not sure if this is still causing other folks problems, but I have this issue for Fox in the LA area. I have youtube tv, and toggling local channels off and then on works for abc, nbc, and cbs, and gives me the errors below for fox. I am running v 2023.01.23.1746 on an intel mac mini. I can log in via the same browser (chrome) in another tab, and successfully authenticate using my tv provider. Any thoughts?
2023/02/12 23:20:59.937896 [TVE] action=navigate url=https://www.foxsports.com/live
2023/02/12 23:20:59.969922 [TVE] action=request type=Document method=GET url=https://www.foxsports.com/live
2023/02/12 23:20:59.969946 [TVE] action=auth_domain domain=www.foxsports.com
2023/02/12 23:20:59.969953 [TVE] action=foxsportsauth step=start
2023/02/12 23:21:04.468869 [TVE] action=exception err=&runtime.ExceptionDetails{ExceptionID:1, Text:"Uncaught (in promise)", LineNumber:0, ColumnNumber:33636, ScriptID:"220", URL:"https://cdn.opecloud.com/ope-fox.js", StackTrace:(*runtime.StackTrace)(0xc001c78100), Exception:(*runtime.RemoteObject)(0xc001220480), ExecutionContextID:2, ExceptionMetaData:easyjson.RawMessage(nil)} value=Error: [object Object]
at https://cdn.opecloud.com/ope-fox.js:1:33637
2023/02/12 23:21:04.468938 [TVE] action=exception err=&runtime.ExceptionDetails{ExceptionID:2, Text:"Uncaught (in promise)", LineNumber:0, ColumnNumber:33636, ScriptID:"220", URL:"https://cdn.opecloud.com/ope-fox.js", StackTrace:(*runtime.StackTrace)(0xc001c78240), Exception:(*runtime.RemoteObject)(0xc0012205a0), ExecutionContextID:2, ExceptionMetaData:easyjson.RawMessage(nil)} value=Error: [object Object]
at https://cdn.opecloud.com/ope-fox.js:1:33637
2023/02/12 23:21:04.469270 [TVE] action=exception err=&runtime.ExceptionDetails{ExceptionID:3, Text:"Uncaught (in promise)", LineNumber:0, ColumnNumber:33636, ScriptID:"220", URL:"https://cdn.opecloud.com/ope-fox.js", StackTrace:(*runtime.StackTrace)(0xc001c78e00), Exception:(*runtime.RemoteObject)(0xc001220ea0), ExecutionContextID:2, ExceptionMetaData:easyjson.RawMessage(nil)} value=Error: [object Object]
at https://cdn.opecloud.com/ope-fox.js:1:33637
2023/02/12 23:21:09.431437 [TVE] action=tvejs msg="foxSportsSelect: path=/live"
2023/02/12 23:21:09.444058 [TVE] action=request type=Document method=GET url=https://www.foxsports.com/provider/register
2023/02/12 23:21:09.444084 [TVE] action=foxsportsauth step=register
2023/02/12 23:21:15.282113 [TVE] action=foxsportsauth event=page_ready
2023/02/12 23:21:15.371725 [TVE] action=tvejs msg="foxSportsSelect: path=/provider/register"
2023/02/12 23:21:15.371805 [TVE] action=tvejs msg="foxSportsSelect: pick mvpd"
2023/02/12 23:21:48.682772 [TVE] action=fox_station err=Cable provider authentication failed
I am in San Francisco area and cannot get FOX either. Access was mostly hit and miss with the Super Bowl likely changing the way the standard TVE works. Looks like all major events the networks kill off TVE access for that event and then restore it later. This has happened too many times for it to be a coincidence. You will have to use OTA to ensure access. Guess I will finally have to put that antenna up.
Lots of conversation in this thread, it appears, about the same issue. Seems fox broke everything for the Super Bowl. Updated to the 2023.02.13.0044 prerelease, and toggled local channels off and on to get fox back. I did not click the 4k feature (for now). Need to do more reading before enabling that.
Lost FOX(6002) after the Super Bowl. Will not authenticate with 4K off or on.
@mtnbkr60 this happened to me too and this morning I had to get it back by doing the following:
- uncheck the Local Networks via TV Everywhere option at the bottom of the server's settings page
- load your server in a secure tab/window of your browser: add "https://" at the beginning of the local URL
- check the Local Networks via TV Everywhere option
- accept the request from your browser to access your location
- wait until the local channels are added
What version of the server are you running?
2023.02.13.0044
OK, you're on the latest pre-release, same as my server.
To be honest, I have never seen the message "fox content missing" so this is new to me.
Sorry, I don't know what else to suggest.
Unless somebody else reading this has had the exact same issue and can explain how they resolved it, you should get the attention of the developers.
Try it 
2 Likes
All good now. Thx 
1 Like
So, weird thing. When I updated to pre-release "2023.02.13.0044" yesterday, I got fox back and everything worked. Today I realized I was missing nbc from all my recent refreshes. I tried toggling local channels off on and it failed. I updated to the latest pre-release "2023.02.14.0057", toggled local channels again, no luck. Then I realized I probably need to do the nbc.com/live auth dance. Did that, toggled local channels... again, and got nbc back. But now, what ever I do, i can't get fox to work again with the latest pre-release and I can't seem to figure out how to roll back to the older prerelease or the stable version. anyone else having issues with "2023.02.14.0057" not being able to load fox with yttv?
Apparently doing the "reset password to same password" and reauth'ing all channels, then unchecking and rechecking local channels fixed fox. Sorry to be so chatty about this, but it feels a little fragile at the moment, and I never know if its a bug or just one more thing I need to try.
Anyone having issues with this again? Mine started acting back up with what appears to be only Fox TVE. I have both YTTV & Xfinity login credentials, and it’s an issue for both.
I'm having the same issue. FOX has been gone for weeks. I've tried unchecking and re-checking and nothing
Try this after updating to the latest DVR prerelease version
(If you have more than one TVE Provider in Channels, repeat steps 1-4 for each Provider before doing step 5)
- Using a browser on your DVR server or device on your LAN in Private/Incognito mode go to https://www.fox.com/live/
- Sign in with your Provider and see if it shows and streams your local FOX station
- Unlink (sign out) from your Provider at the site and close the browser
- Do the update password trick to your TVE source by using Update Password under the gear dropdown next to your TVE source in the DVR web UI and just key in your existing Provider password to clear the chromedata folder
- Toggle the experimental TVE local option off and on and let it scan for locals
I'm getting authz 400 bad request error on my local Fox affiliate this morning. I can sign in with my provider and it redirects me to Fox35orlando.com and streams fine from a browser.
This channel's been working fine for months, I'm running latest DVR pre-release.