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
When using the public environment, if you start new nodes the environment works well, they are able to stablish transports and routes and make the apps work.
However, when nodes are restarted:
Each node re-stablish the previous transports, and they are reported as such by the cli
If you try to use an app, route-finder will report that there is no route available between the nodes, however the transports are there
If you try to re-stablish the old transports manually (skywire-cli --rpc $RPC_A node add-tp $PK_B for example) it will timeout during handshake, as opposed to what happens with fresh nodes
You can manually remove the old transports and add new ones, the result is the same as in 3)
The text was updated successfully, but these errors were encountered:
When using the public environment, if you start new nodes the environment works well, they are able to stablish transports and routes and make the apps work.
However, when nodes are restarted:
skywire-cli --rpc $RPC_A node add-tp $PK_B
for example) it will timeout during handshake, as opposed to what happens with fresh nodesThe text was updated successfully, but these errors were encountered: