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
With latest bee, adding p2p-ws-enable: true does not result in websocket underlay appearing in /addresses endpoint.
Furthermore, even if the if option.wsEnabled conditions are removed, ws underlay still does not appear. Workaround involved removing tcp transport / listen address for tcp, which interestingly resulted in ws underlay appearing in /addresses endpoint.
The text was updated successfully, but these errors were encountered:
it's probably because of tcp.DisableReuseport() on the TCP transport and not having a different default port nor being able to specify a different port for WS through config
With latest bee, adding p2p-ws-enable: true does not result in websocket underlay appearing in /addresses endpoint.
Furthermore, even if the if option.wsEnabled conditions are removed, ws underlay still does not appear. Workaround involved removing tcp transport / listen address for tcp, which interestingly resulted in ws underlay appearing in /addresses endpoint.
The text was updated successfully, but these errors were encountered: