TiVo Community Forum banner

Streaming from online.tivo.com doesnt work in chrome

5021 Views 10 Replies 9 Participants Last post by  diggler273
All of a sudden this morning online.tivo.com will not stream in chrome. I've deleted all my browsing data, ive tried two different computers with chrome. It works in safari, and in IE on the 2nd computer. When i try in chrome i get an error that says

We are unable to detect your TiVo streaming device from this location. If you are currently away from home, streaming video is not supported at this time.
1 - 11 of 11 Posts
upon further investigation chrome dev tools reveals

Access to XMLHttpRequest at 'http://(MYIP):49152/sysinfo/json/svcinfo' from origin 'http://online.tivo.com' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `private`.

After researching that i found this link
Chrome CORS error on request to localhost dev server from remote site

it went into a bit about how
"Chrome has implemented CORS-RFC1918, which prevents public network resources from requesting private-network resources - unless the public-network resource is secure (HTTPS) and the private-network resource provides appropriate (yet-undefined) CORS headers."

So basically a public network "online.tivo.com" cannot access my local network (where my tivo is) due to this new CORS-RFC1918 standard.

The is a fix to disable this behavior for now
chrome://flags/#block-insecure-private-network-requests

I set the first one "Block insecure private network requests." to disable. restarted chrome and now my online.tivo.com can stream shows again.

Hope this helps someone else.

See less See more
  • Like
Reactions: 5
upon further investigation chrome dev tools reveals

Access to XMLHttpRequest at 'http://(MYIP):49152/sysinfo/json/svcinfo' from origin 'http://online.tivo.com' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space `private`.

After researching that i found this link
Chrome CORS error on request to localhost dev server from remote site

it went into a bit about how
"Chrome has implemented CORS-RFC1918, which prevents public network resources from requesting private-network resources - unless the public-network resource is secure (HTTPS) and the private-network resource provides appropriate (yet-undefined) CORS headers."

So basically a public network "online.tivo.com" cannot access my local network (where my tivo is) due to this new CORS-RFC1918 standard.

The is a fix to disable this behavior for now
chrome://flags/#block-insecure-private-network-requests

I set the first one "Block insecure private network requests." to disable. restarted chrome and now my online.tivo.com can stream shows again.

Hope this helps someone else.
THANK-YOU!
The is a fix to disable this behavior for now
chrome://flags/#block-insecure-private-network-requests

I set the first one "Block insecure private network requests." to disable. restarted chrome and now my online.tivo.com can stream shows again.
This was perfect! Thanks. I guess we are re-opening a security vulnerability that Chrome was trying to keep closed by default... but within a private network... I'll risk it. :)
  • Like
Reactions: 1
This is the registry key I changed. It will only open up chrome to tivo.com. I added it manually, but put this in a tivo.reg text file and run it to enter it automatically.
Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Google\Chrome\InsecurePrivateNetworkRequestsAllowedForUrls]
"1"="online.tivo.com"
I googled that key and found all the Chrome registry options!
This is the registry key I changed. It will only open up chrome to tivo.com. I added it manually, but put this in a tivo.reg text file and run it to enter it automatically.
Code:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Google\Chrome\InsecurePrivateNetworkRequestsAllowedForUrls]
"1"="online.tivo.com"
I googled that key and found all the Chrome registry options!
Is this still working for you? I cannot get it to work even by disabling it globally in the chrome flags.
All of a sudden this morning online.tivo.com will not stream in chrome. I've deleted all my browsing data, ive tried two different computers with chrome. It works in safari, and in IE on the 2nd computer. When i try in chrome i get an error that says

We are unable to detect your TiVo streaming device from this location. If you are currently away from home, streaming video is not supported at this time.
Did it stream to your PC via Microsoft Edge?
I was actually able to get it to work again by rebooting the DVR. It's still pretty unstable though. Only works for about an hour or so before freezing
upon further investigation chrome dev tools reveals

Access to XMLHttpRequest at 'http://(MYIP):49152/sysinfo/json/svcinfo' from origin 'http://online.tivo.com' has been blocked by CORS policy: The request client is not a secure context and the resource is in more-private address space private.

After researching that i found this link
Chrome CORS error on request to localhost dev server from remote site

it went into a bit about how
"Chrome has implemented CORS-RFC1918, which prevents public network resources from requesting private-network resources - unless the public-network resource is secure (HTTPS) and the private-network resource provides appropriate (yet-undefined) CORS headers."

So basically a public network "online.tivo.com" cannot access my local network (where my tivo is) due to this new CORS-RFC1918 standard.

The is a fix to disable this behavior for now
chrome://flags/#block-insecure-private-network-requests

I set the first one "Block insecure private network requests." to disable. restarted chrome and now my online.tivo.com can stream shows again.

Hope this helps someone else.
This also solved same problem in Edge. just replace "Chrome" to "Edge"
This was perfect! Thanks. I guess we are re-opening a security vulnerability that Chrome was trying to keep closed by default... but within a private network... I'll risk it. :)
I have been trying to figure this out for months thank you so much for posting this.
1 - 11 of 11 Posts
Top