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
For 2), I can understand that you start with the one selected. It is a good strategy for performances. But you should then iterate on other addresses till you find one suitable.
This is why we have multiple addresses.
I've totally disabled IPv6 connection for now until I find a suitable solution for client-side WebSocket using IPv6. In the mean time, I've made the fix so that all Network Properties are tried on Push/Pull
The node I use has an IPv6 address in the Network information.
The model is here: https://gist.github.com/gnain/4d285501fa45d2195f97
The editor shows an error message:
The IPv6 address does not seem to be good. Should probably be (removing the scope):
ws://fe80:0:0:0:be5f:f4ff:fe21:74e2:9000/
The node also has a IPv4 address. It should try to reach the node through all the addresses till one is successful.
The text was updated successfully, but these errors were encountered: