Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Disney+ on ROKU

Hello everyone,

We're having issues accessing Disney+ on ROKU.The Disney+ menu loads but none of the movies. In the log files, we get the typical XG error:

For other services, we had to put in web exceptions using matching URLs with URL patterns. It can get messy. Any ideas? 

2020-01-13 13:41:38
Invalid Traffic
Denied
 
0
PortA1
 
10.4.9.226
52.54.201.142
57563
443
TCP
0
01001
 


This thread was automatically locked due to age.
Parents
  • Hi  

    This is probably because of the way the streaming content is being delivered.

    I added the below to the Web Exceptions on the XG:

    And in helpfulness here they are in plaintext:

    ^[A-Za-z0-9.-]*\.disney-plus\.net/

    ^[A-Za-z0-9.-]*\.disneyplus\.com/

    ^[A-Za-z0-9.-]?\.search-api-disney\.svcs\.dssott\.com/

    Adding the above exceptions, I have no problem accessing Disney+ streaming services on any device regardless of brand/model.

    Thanks!

    KingChris
    Community Support | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

  • Thanks for the URL patterns but they aren't working in my case. Digging in a bit deeper, I noticed that my connection to Disney+ on ROKU and Apple TV are being dropped via IPS. This is what the log shows:

    Time

    Log comp

    Action

    User name

    Src IP

    Dst IP

    Signature ID

    Signature name

    Category

    Platform

    Victim

    Firewall rule

    Message ID

    Live PCAP

    1/20/20 7:59

    Signatures

    Drop

     

    23.62.6.171

    10.3.1.33

    1060130022

    FILE-OTHER Nullsoft Winamp Player Computer Name Handling Buffer Overflow

    file-other

    Windows

    Client

    19

    7002

    Open PCAP

    Any ideas on how to fix this?

  • Hi  

    It appears that you are using 1 of the default IPS policy that are provided in the build.

    The best way to fix this is to create a custom IPS policy and ensure that you do NOT select this signature ID in your customer IPS policy.

    Alternatively pinging this IP address shows that it resolves to Akamai which is a CDN.  You could create a blank firewall rule with a destination of this network/IP address without any scanning and IPS applied to it.  This will resolve the above.

    Thanks!

    KingChris
    Community Support | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

Reply
  • Hi  

    It appears that you are using 1 of the default IPS policy that are provided in the build.

    The best way to fix this is to create a custom IPS policy and ensure that you do NOT select this signature ID in your customer IPS policy.

    Alternatively pinging this IP address shows that it resolves to Akamai which is a CDN.  You could create a blank firewall rule with a destination of this network/IP address without any scanning and IPS applied to it.  This will resolve the above.

    Thanks!

    KingChris
    Community Support | Sophos Support

    Sophos Support VideosKnowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question use the 'This helped me' link

Children