This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Netflix "Watch Now" Streaming Not Working

Hi all,

Ever since I installed my Astaro Security Gateway (recently rebuilt with v. 7.2), I can't get Netflix "Watch Now" to stream. When I pull up Netflix and attempt to stream a movie, I view the HTTP proxy log and see an entry:

url="69.53.227.37/.../

I tried adding a host exception of 69.53.227.37, as well as a network exception for 69.53.227.0/24 in the HTTP proxy, but it still fails. What am I doing wrong?

Anyone else get Netflix to work?

This thread was automatically locked due to age.

Parents

0 RFCat_vk_01 over 17 years ago

Hi,
do you have "bypass proxy for streaming" ticked?

Ian M
Cancel
Vote Up 0 Vote Down

Cancel
0 bhall7 over 17 years ago in reply to RFCat_vk_01

Yes, that option is selected already.
Cancel
Vote Up 0 Vote Down

Cancel
0 Pestilent over 17 years ago in reply to bhall7

I am having the same issue. So far setting the "allow streaming content" and creating a http bypass rule has not helped. Anyone have any luck with this?
Cancel
Vote Up 0 Vote Down

Cancel
0 Pestilent over 17 years ago in reply to Pestilent

After watching the live log while trying to launch a "Watch Now" instance, I noticed that there was a filter action preceding the other errors. It seems that netflix initially requests data from http://netflix-888.vo.llnwd.net prior to initiating the stream. I created an http exception for both netflix.com and that url and "Watch Now" now works.

Hope this helps any others that ran into the same issue.
Cancel
Vote Up 0 Vote Down

Cancel
0 Pestilent over 17 years ago in reply to Pestilent

It turns out that the address that netflix makes the stream request from is dynamic.

In my testing I had blocked content from the following
http://netflix-314.vo.llnwd.net
http://netflix-888.vo.llnwd.net

I only tested with two movies (just enough to realize the url changed) so I am led to believe that the numeric contingent of the address is goign to change every time.

I ended up removing the URL exceptions I had and replacing them with "netflix" as the url. This seems to act as a catch all wildcard this far ( i have tested a few more movies since the initial issues).
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Pestilent over 17 years ago in reply to Pestilent

It turns out that the address that netflix makes the stream request from is dynamic.

In my testing I had blocked content from the following
http://netflix-314.vo.llnwd.net
http://netflix-888.vo.llnwd.net

I only tested with two movies (just enough to realize the url changed) so I am led to believe that the numeric contingent of the address is goign to change every time.

I ended up removing the URL exceptions I had and replacing them with "netflix" as the url. This seems to act as a catch all wildcard this far ( i have tested a few more movies since the initial issues).
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data