greymass / anchor

EOSIO Desktop Wallet and Authenticator
https://greymass.com/anchor/
MIT License
565 stars 217 forks source link

java error #1130

Closed bayzora closed 3 years ago

bayzora commented 3 years ago

image

I get this error when trying to log on from the wax web screen. please advise.

aaroncox commented 3 years ago

Which version are you using? We have been working to resolve this on certain versions, so if you're on an older version this may be resolved.

bayzora commented 3 years ago

This is the newest version 1.2.4. I can open the window but the interaction between the browser and the app is not linking. Not sure why. I even went as far as installing a fresh version over, but that didn't seem to do anything. So I am wondering if there is something in the cache that is preventing the connection.

aaroncox commented 3 years ago

This error happens when Anchor is unable to connect to a relay server, which is used to relay requests from dapps to your device.

Give this page a try and see if you're able to connect to the relay servers at all:

https://greymass.github.io/anchor-link-diagnostics/

I'm wondering if either something on your computer, or something on your network, is preventing you from reaching those servers and allowing the connection between you and our servers.

ngotrung42 commented 3 years ago

I met such error with version 1.2.4. When checking, the DNS connection error. How do I fix it? I uninstalled it again but it didn't work Screenshot_37

CardanoDur commented 3 years ago

Getting the same error in 1.2.5

Ran the diagnostics without an issue. It doesn't happen immediately, but after maybe 5 minutes in the background

Screenshot 2021-06-26 085955

aaroncox commented 3 years ago

We pushed an update out today that we hope resolves this (1.2.6). Feel free to update (Help menu -> Check for Updates), but want to continuing monitoring if this is resolved.

I'm going to close out this issue, but feel free to continue the discussion here:

https://github.com/greymass/anchor/issues/1139

CardanoDur commented 3 years ago

This issue is still happening in 1.2.6