-
Notifications
You must be signed in to change notification settings - Fork 642
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
Websocket error when sending DMs #308
Comments
Are you using any websocket functions or used op8 scraper on the same instance by any chance? |
I am not
…
On Feb 19, 2022 at 6:56 AM, <Vanshaj ***@***.***)> wrote:
Are you using any websocket functions or used op8 scraper on the same instance by any chance?
—
Reply to this email directly, view it on GitHub (#308 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AX27IGTJJFMJDYMBFS7F2A3U36HRDANCNFSM5OZRAQUQ).
Triage notifications on the go with GitHub Mobile for iOS (https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or Android (https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
After further investigation, it appears that after it cycles to the next token - and if the token is invalid - then it gets stuck in a loop, continuously giving that error. Once I checked the tokens using the token checker, and started doing it again, then it worked. It only worked until once again a token was invalid, then it once again started giving that error. |
When sending mass DMs, I continuously get this error. Occasionally 4 or 5 DMs will go through before it goes back to spamming this error. Tokens are in the correct format. I've tried with and without "use_proxy_for_gateway"
The error I'm getting is:
Websocket closed error while reading message from websocket: websocket: close 4004: Authentication failed
The text was updated successfully, but these errors were encountered: