search

fastlane / boarding

Instantly create a simple signup page for TestFlight beta testers
https://fastlane.tools
MIT License
877 stars 191 forks source link

Random heroku 403 forbidden errors #202

Open VictorAny opened 6 years ago

VictorAny commented 6 years ago

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 commented 6 years ago

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

VictorAny commented 6 years ago

Nope..still randomly getting failures..

nzeltzer commented 6 years ago

Same.

joshdholtz commented 6 years ago

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

nzeltzer commented 6 years ago

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 commented 6 years ago

Here's an application log file.

kuglemic commented 6 years ago

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 commented 6 years ago

After searching through the Fastlane org's repos and looking at similar issues, it looks like this is an issue with iTunes Connect authentication going stale. For now, I've just set our dynos to restart every hour.

On Mon, May 7, 2018 at 2:54 AM Michael Kugler notifications@github.com wrote:

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.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/fastlane/boarding/issues/202#issuecomment-387016928, or mute the thread https://github.com/notifications/unsubscribe-auth/AE_CPfuwPHqGIJte-cvSOxX7BxV--v5pks5twBnPgaJpZM4SiOTi .

biscottigelato commented 6 years ago

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

siburb commented 5 years ago

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

vrobel commented 5 years ago

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