Cannot setup stream errors with Netflix (1.1.4.0) [SSL Handshake failed]

[psychonscious]

Hi everyone, I'm starting to experience occasional errors with Netflix where a few popups mentioning a stream initialization error occurs then the screen stays greyed out with nothing happening. I've tried restarting the app, which doesn't seem to help, and restarting laptop which will at least let me perform a few downloads before the problem occurs again. AP and D+ seem fine aside from some UI flickering on the AP GUI (which isn't impact usability). Anyway, attaching log file and I'll download latest release in a second to see if it helps.

 

[psychonscious]

Looks like the file didn't attach on first go around. Second times the charm

 

[DeepSpace]

There just was an update minutes ago, please try it.
https://forum.redfox.bz/threads/anystream-1-1-5-0.81351/

 

[psychonscious]

Just updated to 1.1.5.0 and the issue is still there, new log file for devs attached

 

[psychonscious]

A bit of additional info for the developers. Things appear to be working fine on my desktop, the issue only occurs with my Dell XPS 15 laptop

 

[RedFox 1]

Thank you for the log files

 

[Pete]

Hi everyone, I'm starting to experience occasional errors with Netflix where a few popups mentioning a stream initialization error occurs then the screen stays greyed out with nothing happening. I've tried restarting the app, which doesn't seem to help, and restarting laptop which will at least let me perform a few downloads before the problem occurs again. AP and D+ seem fine aside from some UI flickering on the AP GUI (which isn't impact usability). Anyway, attaching log file and I'll download latest release in a second to see if it helps.

We are aware of this one.
It appears that Netflix updated - some (?) - of their servers which changed some SSL properties and that is incompatible with the way AnyStream handles secure sockets layer.
The problem is, that only a few people are affected and we can't reproduce it.

We're currently experimenting with an alternative SSL implementation (the Windows on-board one) and are hoping, that will resolve the issue.

 

[Fred Berry]

Just in case you need an additional screenshot and log for this error...