HearthSim / Hearthstone-Deck-Tracker

A deck tracker and deck manager for Hearthstone on Windows
https://hsreplay.net/downloads/
4.76k stars 1.12k forks source link

Could not load HSReplay.net account status. Please try again later. #3876

Open Vovchik43432 opened 5 years ago

Vovchik43432 commented 5 years ago

Help pls I can not log in to your account in HS Deck Tracker "Connection refused: localhost:17781"

riQQ commented 5 years ago

Where is the error message shown? Is HDT whitelisted in your firewall? Does running HDT with administrative priviliges help?

Vovchik43432 commented 5 years ago

Where is the error message shown? Is HDT whitelisted in your firewall? Does running HDT with administrative priviliges help?

it doesn't work( This error appears in the browser ("Connection refused: localhost:17781"). Later in the application writes: "HS Replay Error Could not load HSReplay.net account status. Please try again later."

riQQ commented 5 years ago

Please provide the HDT log corresponding to this problem. See https://github.com/HearthSim/Hearthstone-Deck-Tracker/wiki/Reporting-Issues#hdt-log-files.

Vovchik43432 commented 5 years ago

Please provide the HDT log corresponding to this problem. See https://github.com/HearthSim/Hearthstone-Deck-Tracker/wiki/Reporting-Issues#hdt-log-files.

hdt_log.txt

riQQ commented 5 years ago

This is probably a firewall / anti virus issue. Check your settings there.

Error message from the log:

15:48:00|Info|HSReplayNetOAuth.Authenticate >> Authenticating with HSReplay.net...
15:48:00|Info|HSReplayNetOAuth.Authenticate >> [Helper.TryOpenUrl] https://hsreplay.net/oauth2/authorize/?response_type=code&client_id=[...]&redirect_uri=http://localhost:17781/&scope=fullaccess&state=[...]
15:48:01|Info|HSReplayNetOAuth.Authenticate >> Waiting for callback...
15:48:06|Info|HSReplayNetOAuth.Authenticate >> Authentication complete
15:48:06|Error|HSReplayNetOAuth.UpdateToken >> Could not update token, we don't have a code or redirect url.
15:48:06|Info|HSReplayNetOAuth.Authenticate >> Claiming upload token if necessary
15:48:06|Error|HSReplayNetOAuth.UpdateToken >> Could not update token, we don't have a code or redirect url.
15:48:06|Error|HSReplayNetOAuth.ClaimUploadToken >> Could not update token data
15:48:06|Info|HSReplayNetOAuth.UpdateAccountData >> Updating account data...
15:48:06|Error|HSReplayNetOAuth.UpdateToken >> Could not update token, we don't have a code or redirect url.
15:48:06|Error|HSReplayNetOAuth.UpdateAccountData >> Could not update token data
15:48:06|Info|ErrorManager.AddError >> New error: HSReplay.net Error
Could not load HSReplay.net account status. Please try again later.
Techn0core commented 5 years ago

It's not firewall / AV related.

I was proactive and already created an account and linked my blizzard account before I launched the deck tracker app, I think this path is untested. The cause is most likely cookies for both hsreplay.net and blizzard. To get around this you could clear all your cookies (which might be a pain) or:

  1. Sign out of hsreplay.net so you don't get instantly redirected to localhost and see error
  2. Copy the url from browser (starts with https://hsreplay.net/oauth2/authorize/........
  3. Open a different browser or incognito window and paste in url, should allow you to sign in to both hsreplay.net and blizzard and link with app
riQQ commented 5 years ago

Thanks for your reply. @azeier could you take a look at this

obsirallove commented 5 years ago

помогите пожалуйста ! Снимок экрана (31)

jpinto3488 commented 4 years ago

I confirm I am having same problem with the latest version, but maybe this problem is related with hsreplay.net and not with the app itself, see attached my network log, at some point hsreplay.net does a redirect to https://localhost, which of course throws an error.

This happens when on hsreplay.net you click the "login with battle.net" button. Cache cleared. 2020-04-01 163453

jpinto3488 commented 4 years ago

Update: I was able to make it work, just copy the localhost url you get in your browser, replace https with http and paste it on a clean firefox session, it will authenticate correctly.

jpinto3488 commented 4 years ago

ok, I just found out that this is indeed a browser issue, due to hsts settings saved on chrome for localhost domain, chrome was forcing all http://localhost to redirect to https://localhost. You can cleanup hsts chrome settings this way: https://superuser.com/questions/565409/how-to-stop-an-automatic-redirect-from-http-to-https-in-chrome