You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just discovered a potential issue. I have websockets switched off on one of my production sites, and on a fairly regular basis, the site would suddenly hang. When I checked the browser console, I noticed that zones.js was spitting out 503's and 404's on trying to contact the server. Seemingly through a websocket.
Could it be, that zones.js doesn't read that websockets are turned off, and attempts to establish a socket connection anyways? That won't work for me, since I am running the production site on Cloudflare, and cannot enable websockets at this point.
The text was updated successfully, but these errors were encountered:
Oh, and sorry for not being able to attach a dump of the errors I was getting in the console. The browser tab died on me before I was able to investigate further. Also, I have removed zones.js from the production site to see if that will solve the issue. Will report back with my findings if any.
I just discovered a potential issue. I have websockets switched off on one of my production sites, and on a fairly regular basis, the site would suddenly hang. When I checked the browser console, I noticed that zones.js was spitting out 503's and 404's on trying to contact the server. Seemingly through a websocket.
Could it be, that zones.js doesn't read that websockets are turned off, and attempts to establish a socket connection anyways? That won't work for me, since I am running the production site on Cloudflare, and cannot enable websockets at this point.
The text was updated successfully, but these errors were encountered: