HTTP server example does not work out of the box
See original GitHub issueBug Report
Current Behavior
Used the code from the example in documentation for app.route
, I cannot hit the route and I see the server logging a 404.
Expected behavior/code The example to work as documented, allowing me to mount arbitrary http routes to be hit on my probot server.
Environment
- Probot version(s): latest
- Node/npm version: Node 10
- OS: OSX mojave
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Simple HTTP Server C code doesn't work on my Mac OS X
I am trying to implement a very simple HTTP server C code, and while doing that I search this on the web ...
Read more >How To Troubleshoot Common Site Issues on a Linux Server
Everybody runs into issues with their website at one point or another. This guide will help you troubleshoot some common issues and get...
Read more >How do I access a web server on a virtualbox from the host ...
To solve your problem i sugest that you add a new network adapter and configure it as Host-only adapter. Now you run the...
Read more >Simple Python HTTP(S) Server — Example - AnvilEight Blog
This is a very trivial HTTP server that responds Hello, world! to the requester. Note, that self.send_response(200) and self.end_headers() are ...
Read more >Tuning IBM HTTP Server to maximize the number of client ...
Problem. Out of the box, IBM HTTP Server supports a maximum of 600 concurrent connections. Performance will suffer if load dictates more ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Quick note 📓 If you are attempting to auto-configure be sure that you start probot with the following
npm run dev
The process does not complete otherwise which means a manual config as @tcbyrd mentions ☝️
Oh hey I noticed your screenshot is says “to get started”, which means it’s loading the startup app that walks you through setting up your app on GitHub. Until that part is completed (or you manually configure all the environment variables), the routing won’t work since the app doesn’t have an App ID to startup with yet. Let me know if that helps at all!