Closed lakers4lyfe closed 2 years ago
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 (https://github.com/V4NSH4J/discord-mass-DM-GO/issues/308#issuecomment-1046011493), 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