Skip to content
New issue

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

New port settings are not applied. #581

jurijakimuk opened this Issue Mar 29, 2019 · 1 comment


4 participants
Copy link

commented Mar 29, 2019

Bug description
Sometimes new port settings are not applied and wallet tries to connect to the wrong old port.

To Reproduce
The wallet must have had changed the remote node and local node settings a few times prior to the test. This bug need more investigation as it appears randomly after a long usage of the wallet. The wallet must be switched to remote node.


  1. Run the wallet.
  2. Switch from remote node to CORRECT local node in the Settings.

Current behaviour
It's not possible. Wallet tries to connect to some unknown port that is NOT equal to the port in the Settings.

Expected behaviour
Wallet is connected to the port specified in the Settings.

Platform and build

  • Windows 10
  • x64
  • 4731, testnet

Zipped video

@jurijakimuk jurijakimuk added this to To do in Bright Boson 2.1 via automation Mar 29, 2019

@anatolse anatolse assigned Aleksandr-Starun and unassigned anatolse Apr 8, 2019

Aleksandr-Starun added a commit that referenced this issue Apr 8, 2019

@Aleksandr-Starun Aleksandr-Starun moved this from To do to Done in Bright Boson 2.1 Apr 8, 2019

@gingervik gingervik assigned jurijakimuk and unassigned gingervik Apr 9, 2019


This comment has been minimized.

Copy link
Member Author

commented Apr 10, 2019

OK on master, 4725.

Bright Boson 2.1 automation moved this from Done to Tested Apr 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.