i'm trying to run the flow monitor in a k8s environment and it looks like the websocket port is different than the port i am binding to.
The page at https://<snip>/index.html requested insecure content from . This content was blocked and must
the server is configured to run on 8080:
- Visit: - the container is open on 8080 but ingress is happening on port 443 since it is https
is there a way to drop the ?port=...?
If you don’t specify a port when you start the monitor server, it defaults to 9998. The ?port= in the url tells the webapp where to open the websocket.
Specifying the websocket port was useful for doing local development, but not strictly necessary. Can you help clarify/generalize the problem statement for your usage in the k8s context?
i see. i’m deploying in a containerized environment so ingress is exposing port 80/443 and routing that to port 8080 on the backend. let me grab some errors i’ve seen in various configurations.
i re-dployed to use port 9998 on the backend. connecting with the default port:
[Warning] [blocked] The page at https://<snip>/index.html requested insecure content from . This content was blocked and must (main.js, line 1303)
So it looks like you are hitting the monitor at http`s` which isn’t compatible with ws:// it would want wss://
is that possible to configure? it looks hardcoded here: https://github.com/clojure/core.async.flow-monitor/blob/95710408ed3c357d2e64a326ffd5b720d55855cc/src/clojurescript/flow_monitor_ui/config.cljs#L10
It is not configurable at the moment. Let me sleep on that one, and I’ll circle back.