microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
ngrok: 502 Bat Gateway
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
after setting all parameters, ngrok still records 502 - Bad Gateway for incoming messages and calls. So the application is indirectly correct, do you know how to solve this problem? Thank you
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ngrok configuration and reproducing the 502 response for incoming messages and calls. Inspect the relevant gateway or tunnel logs to determine whether the failure is in ngrok or the application. Done means both message and call requests reach the application without returning 502.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100