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
Describe the bug
I have two chain and two nodes for each. They're using the same Port and WsPort and within different magic. I can start nodeB after nodeA's running. And NodeB can also receive data although no connections showed on Console. There should be port conflict, right?
To Reproduce
Steps to reproduce the behavior:
Run Node A for A chain.
Make the same Port and WsPort for Node B.
Run Node B for B chain.
Expected behavior
Node B can run and blocks can be received and increase but no connections and peers are showed on Console.
Screenshots
91a865e7eed5a40e45a282d2aa292f50.mp4
Platform:
OS: [e.g. Windows 10 x64]
Version [latest]
The text was updated successfully, but these errors were encountered:
Describe the bug
I have two chain and two nodes for each. They're using the same Port and WsPort and within different magic. I can start nodeB after nodeA's running. And NodeB can also receive data although no connections showed on Console. There should be port conflict, right?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Node B can run and blocks can be received and increase but no connections and peers are showed on Console.
Screenshots

91a865e7eed5a40e45a282d2aa292f50.mp4
Platform:
The text was updated successfully, but these errors were encountered: