Try our conversational search powered by Generative AI!

Websockets and xhr fails in epi UI?


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?

Oct 18, 2016 8:20

Can you paste some full error responses?

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

Oct 19, 2016 22:08

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."

Oct 21, 2016 8:18

Thanks for answers!

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

Oct 21, 2016 8:28

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?

Sep 13, 2018 16:19

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. 

Sep 13, 2018 20:29
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.