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

Bad request to hashing server (expired key) #223

Open
YesThatAllen opened this issue Mar 30, 2017 · 10 comments
Open

Bad request to hashing server (expired key) #223

YesThatAllen opened this issue Mar 30, 2017 · 10 comments

Comments

@YesThatAllen
Copy link
Contributor

Here is what I would like to see new or change within PokeNurse

In the past few days I'm receiving this error message during login.

Error: operation timed out after 5675 ms, 5 tries with error: Bad request to hashing server

I've tried two separate keys, and two separate computers.

I am unable to log in.

This is my environment

  • OS and Version: macOS 10.12.x
  • Version of PokeNurse 2.3.0 release and a fresh build from develop's new pcrypt.
@hacknug
Copy link
Contributor

hacknug commented Mar 30, 2017

Are you sure those keys should work? I just logged in without any issues.

@vinnymac
Copy link
Owner

vinnymac commented Mar 30, 2017

I noticed that node-pogo-protos is now on v2.7.1 and we are v2.7.0. I pushed the latest version to develop if you want to give it a try. Otherwise this will just be another 'can't fix because pogobuf' type of thing.

@YesThatAllen
Copy link
Contributor Author

Good to know @hacknug

@vinnymac I tried develop, and had no luck. This is what I get on the console:

screenshot_4521

@Redarion
Copy link

Has your hash key expired?

@YesThatAllen
Copy link
Contributor Author

It seems that the keys I had both expired. I don't know if we can capture this fact & display it better... or if this issue will serve as the warning to others ;-)

@YesThatAllen YesThatAllen changed the title Bad request to hashing server Bad request to hashing server (expired key) Mar 30, 2017
@vinnymac
Copy link
Owner

vinnymac commented Mar 30, 2017

We could probably detect the error message and display something

Bad request to hashing server, you may be using an expired key. Contact your key provider or try a different key.

Other than that I don't think we can gather enough insight from the error.

@Redarion
Copy link

Don't know if possible but maybe we can also query the expiration date and get also a time reminder!

@hacknug
Copy link
Contributor

hacknug commented Mar 31, 2017

It is possible to do just that. I'll try to look into it and maybe we can avoid any other issues like this one.

@stayre
Copy link

stayre commented Apr 20, 2017

I am having this issue as well - newly purchased key, gave it 5 days from purchase as the last time I did it, it took a couple of days before it worked.
screen shot 2017-04-20 at 7 04 07 pm

Latest public release, MacOS 10.12.4

@hacknug
Copy link
Contributor

hacknug commented Apr 21, 2017

If you're encountering the same issue described in op, you're probably using an expired key or something like that (that's why the title says expired key)

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

No branches or pull requests

5 participants