-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Connection Websocket upgrade failed #524
Comments
Alright, I found my issue. I didn't have any consumers, because I just use HTTP Requests and don't need to listen to any events. Maybe it would be helpful if there is any check before if there are any consumers or not before running in "timeout". |
Instead of relying on the user to interpret the existing debug logs and badmatch error, send an explicit error message when no consumer could be found that we can use in the shard connection. See #524.
Instead of relying on the user to interpret the existing debug logs and badmatch error, send an explicit error message when no consumer could be found that we can use in the shard connection. See #524.
How did you manage to bypass the error? |
@kiddoshainingu on Nostrum latest, the error should change now into something like "No consumers were running nor did any start up in time...". I'd advise you to just spin up a dummy consumer for this purpose, just something like ```elixir
|
@jb3 Thank you very much ! Problem solved. 🙏🏾 |
Since switching to the latest master I get following repeating error when starting my application. This happens in Google Cloud and my local macOS system as well.
The text was updated successfully, but these errors were encountered: