Websockets and xhr fails in epi UI?

Jon Börjesson

Vote:

I have an editor that gets these errors in IE console when logging in to EPi:

I guess its a generic websockets/xhr issue and not an epi issue, but i thought thay maybe someone else here has seen this before and knows what's causing it?

#162845

Oct 18, 2016 8:20

Vote:

Can you paste some full error responses?

I'm seeing status 416 in the screenshot. Never seen that...

#163189

Oct 19, 2016 22:08

Daniel Ovaska

Vote:

Have you enabled websockets support?

http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/User-interface/websocket-support/

#163192

Oct 20, 2016 7:10

Joni Hietala

Vote:

If you are using Windows 7, then there isn't native Web Socket support available. You have to use Windows 8 or 10. From Episerver System Requirements for development: "Note: From CMS 9, Windows Server 2008/2008 R2 and Windows 7 are no longer supported."

#163471

Oct 21, 2016 8:18

Jon Börjesson

Vote:

Thanks for answers!

It seems to something with the corporate firewall or such. It works from an other connection.

#163472

Oct 21, 2016 8:28

David McDonald

Vote:

We are having a similar problem. Is there a direct link betweeen the 416 error and the web sockets problem? Is fixing the web sockets through the firewall the only solution?

#196863

Sep 13, 2018 16:19

David McDonald

Vote:

Never mind. The 416 errors DID turn out to be firewall issues. The custmer found it was an outgoing firewall issue that had to do with content/malware scanning. Didn’t show anything in the event log but somehow affected the traffic.

#196873

Sep 13, 2018 20:29