You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that Trow uses Rocket, which does not support listening to multiple addresses in a single instance. The workaround described here might work tho: rwf2/Rocket#1581.
Otherwise the solution is to have multiple instances of rocket running (like I did here).
Describe the bug
When running a cluster with DualStack/IPv6 trow is not reachable as it only listens on
0.0.0.0
(all IPv4 interfaces).This could be mitigated by letting Trow/Rocket listen by default on
::
(actually all interfaces IPv4 and IPv6).Another workaround would be to allow the helm chart to set the
--host
flag.To Reproduce
Expected behavior
Trow is reachable at the configured domain through the ingress/directly via IPv6
Trow Info
Kubernetes
The text was updated successfully, but these errors were encountered: