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
It looks like the slackbridge container only listen on the hardcoded ipv4-only address 0.0.0.0
this makes it non functional on any ipv6 only host or cluster.
/ # netstat -pan Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:5858 0.0.0.0:* LISTEN -
If the container could listen on the backwards compatible ipv6 any [::]:5858, or on all ( *:5858 ) instead it would work on all clusters.
I have tried making it listen on various versions of :: [::] "::" "[::]" using the hostname config values, but in those cases it the container fails to start at all.
The text was updated successfully, but these errors were encountered:
It looks like the slackbridge container only listen on the hardcoded ipv4-only address 0.0.0.0
this makes it non functional on any ipv6 only host or cluster.
/ # netstat -pan Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:5858 0.0.0.0:* LISTEN -
If the container could listen on the backwards compatible ipv6 any [::]:5858, or on all ( *:5858 ) instead it would work on all clusters.
I have tried making it listen on various versions of :: [::] "::" "[::]" using the hostname config values, but in those cases it the container fails to start at all.
The text was updated successfully, but these errors were encountered: