core-async

jmv 2025-05-12T20:27:55.523329Z

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:  -

jmv 2025-05-12T20:28:58.607139Z

the container is open on 8080 but ingress is happening on port 443 since it is https

jmv 2025-05-12T20:29:23.144629Z

is there a way to drop the ?port=...?

Jarrod Taylor (Clojure team) 2025-05-12T22:29:13.556909Z

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.

Jarrod Taylor (Clojure team) 2025-05-13T00:41:20.925609Z

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?

jmv 2025-05-13T00:42:06.969109Z

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.

jmv 2025-05-13T00:48:17.855339Z

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)

Jarrod Taylor (Clojure team) 2025-05-13T00:54:53.361559Z

So it looks like you are hitting the monitor at http`s` which isn’t compatible with ws:// it would want wss://

Jarrod Taylor (Clojure team) 2025-05-13T01:20:51.500509Z

It is not configurable at the moment. Let me sleep on that one, and I’ll circle back.

🙏 1
🙏🏻 1