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
This is a bug report/feature request/support request/change request
Problem
If /dns4/127.0.0.1/tcp/8000/ws/p2p/16Uiu2HAkxcq84cB1gD1MH5XDQNm1vakvUzwoEhmLFtywF7YF3Hvm is used to dial - then error is thrown from websocket transport here
Works just fine if ``/dns4/localhost/tcp/8000/ws/p2p/16Uiu2HAkxcq84cB1gD1MH5XDQNm1vakvUzwoEhmLFtywF7YF3Hvm` is used.
Proposed Solutions
Since nwaku generates multiaddr with IP in it - we should be able to dial it without error.
Most straightforward solution can be to check for 127.0.0.1 and replace with localhost.
But we also need to check why this throw actually happens as there might be unintended consequences.
The text was updated successfully, but these errors were encountered:
This is a bug report/feature request/support request/change request
Problem
If
/dns4/127.0.0.1/tcp/8000/ws/p2p/16Uiu2HAkxcq84cB1gD1MH5XDQNm1vakvUzwoEhmLFtywF7YF3Hvm
is used to dial - then error is thrown fromwebsocket
transport hereWorks just fine if ``/dns4/localhost/tcp/8000/ws/p2p/16Uiu2HAkxcq84cB1gD1MH5XDQNm1vakvUzwoEhmLFtywF7YF3Hvm` is used.
Proposed Solutions
Since
nwaku
generates multiaddr withIP
in it - we should be able to dial it without error.Most straightforward solution can be to check for
127.0.0.1
and replace withlocalhost
.But we also need to check why this throw actually happens as there might be unintended consequences.
The text was updated successfully, but these errors were encountered: