-
Notifications
You must be signed in to change notification settings - Fork 77
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
Unhandled exception in socket server rejected WebSocket connection: HTTP 404 #1024
Comments
Hi @JackUrb . Hope you are doing well. Our team have been doing very great with Mephisto for a while but we just encounter this error that blocking us from deploying the task. Hope you might have some ideas how to fix this issue as I have spent a few days on this but no luck at all |
I also tested with freshly latest version of mephisto. Still throwing error 404 |
Hi @jayhuynh, this is certainly an issue! We haven't used Heroku extensively any time recently, so it's certainly possible something has changed. One thing you may do - if you could try to open the heroku logs on heroku when the server launches. You may want to add an As Heroku's free model was removed, we've been looking to onboard alternatives in #1010 (fly.io) and also AWS App Runner. |
Figured out the issue - heroku has started to add random hashes to the ends of the app url, so we need to now query for those. Will put up a fix shortly. |
Thank you so much Jack. I'm excited to see your change 😄 |
@jayhuynh try the heroku-domain-query branch. If it works, I'll merge it in. |
I work for me as well. Well done @JackUrb 🥳 |
Issue Description
When I try to deploy my task with heroku + mturk sandbox it keeps thowring
Unhandled exception in socket server rejected WebSocket connection: HTTP 404
Already turn on
debug
flag but can't see much informationExpected Behavior
I worked fine a week or two ago. This is very simple task so I would expect it should be fine this time\
Current Behavior
Keep throwing WebSocket error 404 when
sending alive
afterheroku Scaling dynos
stepSteps to Reproduce
Screenshots
Environment
Additional Information
Possible Solution (Optional)
The text was updated successfully, but these errors were encountered: