unable to open the editor because a web socket request is hanging
See original GitHub issueIn Chrome and Firefox, I am unable to open the API editor (https://studio.apicur.io/apis/22450/editor) and I tried a few times today but the issue is persistent.
I believe that the web socket request is hanging.
wss://studio-ws.apicur.io/designs/22450
The UI shows the loading icon for a while and then “Lost Connection” error appears.
Can you please let help me on this?
Thank you.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:6 (1 by maintainers)
Top Results From Across the Web
NodeJS - What does "socket hang up" actually mean?
It means that socket does not send connection end event within the timeout period. If you are getting the request for cheerio via...
Read more >Troubleshooting connection issues | Socket.IO
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
Read more >WebSockets tutorial: How to go real-time with Node and React
Editor's note: This WebSockets tutorial was updated on 1/19/2021. ... network latency because the initial request is kept open indefinitely.
Read more >"WebSocket Unable to Connect” error message, what should I ...
Do not use a VPN. Connect to a proxy server that supports WebSockets. If these solutions don't work, open a support ...
Read more >Troubleshoot connection issues | Slack
When the Slack desktop app cannot connect, it may be because the settings for your ... Get in touch with your network administrator...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@EricWittmann Thank you for your help and clarification about studio.apicur.io. 👍
Hey everyone - thanks for reporting this problem. Sorry for the delay in response. Apparently whatever was causing the issue has resolved itself. I’ll look into the logs to see if I can find insight into what happened.
Also please remember that https://studio.apicur.io/ is intended to be an evaluation version of Apicurio Studio, and is not suitable for critical production workloads. You are more than welcome to continue using it in whatever capacity you choose, but just be aware that there aren’t any SLAs or anything like that. 😃