-
Notifications
You must be signed in to change notification settings - Fork 24
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
0.5.18: Windows: Starting up the program and checking if it connects with tor enabled and then with tcp enabled is not working #819
Comments
This is still an issue on 0.5.22 |
This is still an issue on 0.5.24 |
Tested on NextNet: version: 0.5.25 and this is still an issue |
Windows 11: |
Tested on v0.5.28 and issue is still prevalent |
When a user toggled Tor off and clicked cancel on the restart pop up and manually restarted the miner, on start up the user received a critical error pop up message. I clicked on the close Tari universe button and tried to open Tari Universe again but I got stuck on 43%. I needed to force quite Tari Universe and set Tor to true on visual studio to get Tari Universe up and running again. This is on a MacBook Air 13 inch M1 2020 on Testnet v0.5.28 |
Related to #874 |
This issue is resolved on Testnet 0.5.41 on a MacBook Air 13 inch M1 2020. |
"The problem is that we've got few tcp peers. You tried to connect when there wasn't tcp peers at all. It means you really hasn't been connected to the Tari network" |
Issue prevalent on 0.5.42 again on a MacBook Pro 13 inch M1 2020 Sonoma 14.5 |
Issue is resolved on Testnet v0.5.45. |
Still prevalent on Windows 11, app version: 0.5.49 but could be due to what @mmrrnn has stated in the above comment |
Issue is no longer prevalent on Windows 11, app version 0.5.56 |
Tested on App version 0.5.58, Windows 11 and this is still prevalent |
Tested on WIndows 11 on app version 0.5.60 and this is still an issue |
Tested on Windows 11, app version 0.5.61 and this is still aan issue |
Tested on Windows 11, app version 0.6.6 and this is still an issue as I am now stuck on 43%: |
@brianp hard fork issue? |
Tested on Windows 11, app version 0.6.16 and this is still an issue where I am still stuck at 43% |
Tested on Windows 11, app version 0.7.0 and this is still an issue where I am still stuck at 43% |
Tested on Windows 11, app version 0.7.0 and issue is still occurring:
|
Tested on Windows 11, app version 0.7.1 and issue is still occurring:
|
Works fine when other peers available |
Marking this as on hold until we make more dns/peer adjustments. I've discussed the changes with @leet4tari, and then I got busy with other things. So we'll come back around to this eventually. I'd say there's no need to keep testing it for now. Keep it as a known issue but problem lays outside of universe itself. |
User is stuck @ 43% initialization on Windows 11, app version 0.7.7 |
Describe the bug
As a user I find when I install the app, disable Tor, close the app, delete the node file and restart, I get stuck at
connecting network peers
for the past 35+ minutes.Additional info:
I checked on com.tari.universe and the node file had been addded again
To Reproduce
Test Starting up the program and checking if it connects with tor enabled and then with tcp enabled:
Expected behavior
On restart of the app, user should be be connected to the Tari network, the chain resynces and the user should be able to mine.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: