Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Random heroku 403 forbidden errors #202

Open
VictorAny opened this issue Mar 8, 2018 · 11 comments
Open

Random heroku 403 forbidden errors #202

VictorAny opened this issue Mar 8, 2018 · 11 comments
Assignees
@joshdholtz

Comments

@VictorAny
Copy link

I recently created a boarding app and started getting emails from my beta users about a crash.
After looking at the website all I see is a REASON: <pre>FORBIDDEN <pre>.

Whats odd is that restarting the dynos on heroku resolves the issue but only for a certain amount of time until it happens again. I've now restarted it 4 times. It's strange since the application isn't being overworked. Memory usage is usually below 22% and throughput is <1rps. The dynos are Hobby Dev.

Any ideas?
@VictorAny
Copy link
Author

Actually it seems I have have set the APP_ID incorrectly. I fixed it and haven't been able to reproduce the failure.

@VictorAny
Copy link
Author

Nope..still randomly getting failures..

@nzeltzer
Copy link

Same.

@joshdholtz
Copy link
Member

joshdholtz commented Mar 29, 2018 •
edited
Loading

Do you happen to have any Heroku logs for what is causing this 403?

@nzeltzer
Copy link

I will ask about logs. For what it's worth, here's the error message that's printed to the boarding page itself:

Something went wrong, please contact the application owner: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 403 </title> </head> <body> <h2>HTTP ERROR: 403</h2> <p>Problem accessing /v2/providers/70630800/apps/309601447/testers. Reason: <pre> Forbidden</pre></p> <hr /><i><small>Powered by Jetty://</small></i> </body> </html>

@nzeltzer
Copy link

Here's an application log file.

@kuglemic
Copy link

kuglemic commented May 7, 2018

I have exactly the same issue.
Do you have any news on this?

I just rebooted all my dynos in the heroku dashboard for now, and it is working again.

Will investigate if the issue reappears and keep you updated if I find a solution.

@nzeltzer
Copy link

nzeltzer commented May 8, 2018 via email

@joshdholtz joshdholtz self-assigned this May 29, 2018
@biscottigelato
Copy link

@nzeltzer any tips for auto restarting heroku to work around this problem? Not a heroku expert here.

@siburb
Copy link

siburb commented Jan 25, 2019

This is still happening now on a newly created boarding site. Will try the auto-restarting.

@vrobel
Copy link

vrobel commented Mar 15, 2019

Do you think a 2FA account might have no issues with the authentication stale issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joshdholtz joshdholtz

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@vrobel @joshdholtz @siburb @kuglemic @nzeltzer @VictorAny @biscottigelato