GitHub user dosubot[bot] added a comment to the discussion: websocket connection to superset
<!-- Answer --> Your websocket pod is running, but the logs show no active connectionsâthis usually means the Superset frontend isn't connecting via websocket. Here are the most likely causes and fixes: - The websocket URL in your config is set to `ws://localhost:30089`, which won't work if Superset is running in Kubernetes or containers. The frontend needs a URL that's reachable from your browser, like `ws://<your-node-ip>:30089` or a DNS name exposed via NodePort, LoadBalancer, or Ingress. Update `GLOBAL_ASYNC_QUERIES_WEBSOCKET_URL` to use the correct external address. - Make sure your JWT secret (`GLOBAL_ASYNC_QUERIES_JWT_SECRET`) is at least 32 bytes and matches between Superset and the websocket server for authentication to work [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/async_events/async_query_manager.py). - Check your browser's developer console for websocket connection attempts and errors. If you see errors, they may point to CORS, authentication, or network issues. - The frontend will fall back to polling (manual refresh required) if the websocket connection fails. Confirm that `GLOBAL_ASYNC_QUERIES_TRANSPORT` is set to `'ws'` and the feature flag is enabled [source](https://github.com/apache/superset-frontend/src/middleware/asyncEvent.ts). - The pod logs showing `GET /` and `GET /favicon.ico` are likely health checks or misconfigured clients, not websocket connections. Once you update the websocket URL and confirm network access, you should see active channels/sockets in the pod logs when your browser connects. If you still have issues, try connecting to the websocket endpoint with a tool like `wscat` or a browser extension to verify connectivity. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=hallucination) | [Report đ](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ff42ac59-7ff9-467b-9f85-8073c80cd6d3?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34703) GitHub link: https://github.com/apache/superset/discussions/34703#discussioncomment-14106478 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
