-
Notifications
You must be signed in to change notification settings - Fork 168
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
Failed to authroize Discord user! Check your config.json and try again. #35
Comments
https://github.com/5andr0/PogoLocationFeeder/wiki make sure discord user is your actual email used to create the discord account. |
I'm getting the same error. (When i use yesterday got no 'Failed to authroize' error). |
I'm getting the same error too, why? |
I got the same error today |
same error,about some minute later from first run,just the channel pokesnipers is working。 |
check your emails as it asks about the IP being authorized before it works |
@txt3rob don't have any email asking about it, and i think everyone here already confirmed email too. |
I got the same error today, |
i have the same issue, i think the problem is that the system proxy is ignored. |
Same issue. |
same here. triplechecked the mail. this morning it worked |
Has anyone figured this out? |
same issue here. e-mail is already verified. However, i tried to login directly to the website, and it cant connect also. Based on that, I guess discord have connection problems atm? |
We appear to have been setting lots of fires under Discord's servers, and have worked with staff to mitigate these issues by switching to a dedicated feed system. Please update to the latest version -- additionally, a new release should be available within the next few hours. |
I get this message all the time after this night, this afternoon it was working perfectly.
Failed to authroize Discord user! Check your config.json and try again.
I know for sure that the account and credentials are ok. Do I need to use a token or something like that ?
I use the PokeMobBot
Thanks you
The text was updated successfully, but these errors were encountered: