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

Diagnostics screen reports outbound port is not working on both Testnet and Mainnet wallets version 5.3.3.0 #2445

Closed
KeithMyers opened this issue Mar 1, 2022 · 7 comments · Fixed by #2506
Assignees
Labels
Milestone

Comments

@KeithMyers
Copy link

Both wallets have been working fine after the new update. Diagnostics passed on both wallets. No changes to configuration files.
Rebooted the computer after 11 days and now both wallets show the error.
Rebooted several times and still shows the error.

Made many changes to the computers network firewall settings which were never activated before. Port forwarded ports 32748 and 32749 and no change in symptoms. Changed listen=0 to listen=1 in the config files. No change in symptoms.

Both wallets do in fact show outbound port activity. Diagnostics still failing.

Screenshot from 2022-03-01 09-35-46

Screenshot from 2022-03-01 10-15-05

Gridcoin wallets version 5.3.3.0 both for Testnet and Mainnet
Pulled from the PPA's via apt update

AMD 5950X
32GB RAM
512GB M.2 SSD
Ubuntu 20.04.4 LTS

@KeithMyers KeithMyers added the bug label Mar 1, 2022
@jamescowens jamescowens self-assigned this Mar 1, 2022
@jamescowens
Copy link
Member

The diagnostics use an external port testing service, portquiz.net, to verify the port is working, and this service appears to be totally down.

@jamescowens jamescowens added this to the Kermit's Mom milestone Mar 1, 2022
@jamescowens
Copy link
Member

We will probably need to change this to point to a different service if that service stays down. I also think that we can marked that test passed without interacting with that service if there are already successful outbound connections, since a working port is implied with successful outbound connections.

@KeithMyers
Copy link
Author

Sounds logical. A lot of unnecessary grief and spinning wheels for me on this issue that was not my fault or the hosts fault.

@KeithMyers
Copy link
Author

Closing as a known issue that is being worked on.

@jamescowens jamescowens reopened this Mar 1, 2022
@jamescowens
Copy link
Member

I am reopening this until we have a permanent, less dependent fix in place.

@RoboticMind
Copy link
Contributor

If some other service is going to be used in the future, it might be good to make it a startup option so it can at least be changed in situations like this

@jamescowens
Copy link
Member

Looks like portquiz.net is back up...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants