-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Heroku application error: request timeout (503) #63
Comments
i had the same issue!! have you manged to fix it? |
Nope, it's so weird can't seem to find a way to fix it. |
did you ask Stephen Grider for help? i sent him an email right now... |
yes but no response yet |
i fixed it! it is not the best option but it works for small tests!! |
It works! Maybe in the future you need to add the ip-address of the heroku app server, but for development purposes this works great! Awesome that you found a fix! |
i could not find heroku ip because it is not constant, if you find please let me know! |
So after section 6 lecture: fixing heroku proxy issues I stumbled upon a problem when visiting the url for the /auth/google. It won't load and after ~30 sec it prompted this error from the heroku logs:
2020-02-26T18:45:15.118863+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/auth/google/callback?code=4/wwF92gsY8-IO9tMHD7KPQMvwEn15z5vikfpCpJxEDzzosONYHKqOMREg5nFrhRCExl_rrI8Hm_MuXZBu3qx6C_w&scope=email+profile+https://www.googleapis.com/auth/userinfo.profile+openid+https://www.googleapis.com/auth/userinfo.email&authuser=0&prompt=none" host=tranquil-ridge-16114.herokuapp.com request_id=76288616-519d-4e55-91ea-cccf707390a2 fwd="77.175.179.159" dyno=web.1 connect=0ms service=30001ms status=503 bytes=0 protocol=https
2020-02-26T18:45:16.734752+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=tranquil-ridge-16114.herokuapp.com request_id=2fe5e6f0-a04a-4ade-8a72-86bfb1eb9393 fwd="77.175.179.159" dyno=web.1 connect=1ms service=2ms status=404 bytes=394 protocol=https
anyone knows how to fix this?
The text was updated successfully, but these errors were encountered: