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

Bad Gateway for probot routes #24

Closed
riyadhalnur opened this issue Jul 19, 2019 · 2 comments · Fixed by #59
Closed

Bad Gateway for probot routes #24

riyadhalnur opened this issue Jul 19, 2019 · 2 comments · Fixed by #59
Labels
released

Comments

@riyadhalnur
Copy link

The /stats/ and /ping routes for a probot application return an HTTP 502 Bad Gateway status.

The application, in this case, is a lambda function triggered by AWS ALB - the routes forwarded are /, /probot, /probot/stats, and /ping. Only the /probot route works since it is handled directly by the handler in this module https://github.com/probot/serverless-lambda/blob/master/index.js#L31-L40.
This was referenced Jul 19, 2019
Merged
Closed
@gr2m
Copy link
Contributor

gr2m commented Feb 9, 2021

Starting with #59, no other routes will be exposed by default, you have to that yourself.

@gr2m gr2m mentioned this issue Feb 9, 2021
Merged
@gr2m gr2m closed this as completed in #59 Feb 10, 2021
@github-actions
Copy link

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Probot v11 probot/adapter-aws-lambda-serverless
2 participants
@gr2m @riyadhalnur