We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a change request
When a js-waku app is ran on HTTP (not HTTPS) and also not localhost connection-manager will silently fail to connect to any node.
localhost
This is visible when debug:waku* is enabled, but not in "production" setting
debug:waku*
waku:error:connection-manager Error dialing peer 16Uiu2HAmSve7tR5YZugpskMv2dmJAsMUKmfWYEKRXNUxRaTCnsXV - Error occurred during XX handshake: Error occurred while verifying signed payload: TypeError: Cannot read properties of undefined (reading 'digest') +0ms
Surface an error/warning about not using HTTPS and hence not being able to connect to any peers to the dev/user
The text was updated successfully, but these errors were encountered:
Let's confirm that full nodes advertise ws connection and not only wss.
ws
wss
In nwaku-compose - https://github.com/waku-org/nwaku-compose/blob/8abb2a474d9bf9f9acc5c3a8bc03c4eda015551d/run_node.sh#L36
nwaku-compose
Todo:
http
Sorry, something went wrong.
No branches or pull requests
This is a change request
Problem
When a js-waku app is ran on HTTP (not HTTPS) and also not
localhost
connection-manager will silently fail to connect to any node.This is visible when
debug:waku*
is enabled, but not in "production" settingProposed Solutions
Surface an error/warning about not using HTTPS and hence not being able to connect to any peers to the dev/user
Notes
The text was updated successfully, but these errors were encountered: