Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

p2p-enable-ws configuration option inconsequential / WS underlays not being added #4877

Open
lat-murmeldjur opened this issue Oct 24, 2024 · 2 comments
Labels
needs-triaging new issues that need triaging

Comments

@lat-murmeldjur
Copy link

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.

@lat-murmeldjur lat-murmeldjur added the needs-triaging new issues that need triaging label Oct 24, 2024
@lat-murmeldjur
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triaging new issues that need triaging
Projects
None yet
Development

No branches or pull requests

2 participants
@lat-murmeldjur and others