WebSocket connection returns abnormal close 1006

Get Support
1

I am trying to test a WebSocket endpoint using ApiDog:

ws://localhost:3060/ws/progress

However, the request does not reach the server and immediately fails with:

Could not connect to ws://localhost:3060/ws/progress
1006 (abnormal closure)

When I test the same endpoint with Postman, the request reaches the server and behaves as expected (returning 401 Unauthorized for invalid tokens).

Could you help investigate why ApiDog is unable to establish the WebSocket connection while Postman succeeds?

apidog.png
apidog.png1545×737 66 KB

2

postman.png
postman.png1531×553 49.7 KB

3

Hello! Are you making the WebSocket request from the web version or the client?

If you’re experiencing connection issues, you can try the following steps to troubleshoot:

  1. Switch network environments: If the WebSocket interface is accessible from external networks, try switching to a different network (e.g., mobile hotspot) to see if the connection works.
  2. Check proxy settings: If switching to a hotspot resolves the issue, it might be related to proxy configuration. Please refer to the twork proxy configuration - Apidog Docs](Network proxy configuration - Apidog Docs) to verify your settings.
  3. Verify request headers: If the issue persists even on the mobile hotspot, it may be due to additional headers (such as Origin, Cookie, etc.) that browsers automatically include in WebSocket requests. You can open your browser’s Developer Tools (F12), go to the Network tab, locate the WebSocket request, and copy all its headers into the Apidog client before retrying.