WebSocket Connection to wss://... Failed, Socket error changed endpoint to wss://...

[RathodDeven]

I have successfully deployed hubs cloud, and it was working fine until now. In console, it is showing socket endpoint changed error.
Why is this happening all of a sudden? How to solve this ?
Here is log from AWS EC2 instance

and here is console log

[alfainfotech]

I'm getting same 'Web Socket error... it worked fine for few days and all of sudden. Cant get to ADMIN not can do any changes... stuck up !!!

[pattersonbl2]

Would this be a custom client? After doing light research, it could be a cross-origin resource error. I would start troubleshooting around this topic.

[alfainfotech]

FYI: Yes this is custom client on AWs. 1st time I installed after few days I got error, after trying and not able to find any resource, I deleted the stack and re-installed. Again after few says same thing... and again I have to delete and re-installed brand new fresh stack. So far its been 4 days and working fine, but not sure when same error will take over again.
Plus I dont see I saw any CORS error on console. But you can keep an eye... Thx for follow up.

[jbshin-gemiso]

I also have the same issue. A custom client was being developed, but it was not applied to the hubs cloud.
No workaround was found. As in the case above, it suddenly happened to me while it was working fine.