![]() And unfortunately, my change from worker to web was just that. However, I wouldn’t be writing an article about a simple solution I achieved on my second attempt if there were no caveats that came with it. I pushed my code to GitHub and tested my DBL vote event once again by sending a POST request to the endpoint of my Heroku app, and it worked! My bot had received the webhook and reacted accordingly. # worker: python bot.py web: python bot.py If your app includes a web server, you should declare it as your app’s web process.”Ĭlearly, I had just configured my process type incorrectly and all that was needed was a quick change from worker to web. “A Heroku app’s web process type is special: it’s the only process type that can receive external HTTP traffic from Heroku’s routers. I had my process type set as worker, which upon further research would not work for a web server. The Procfile tells Heroku what type of process to run and what file to run the process on. at=error code=H14 desc="No web processes running" method=POST path="/dblwebhook" host=_. request_id=7a54e44c-5c2a-40fe-8bfc-097313c0c919 fwd="_" dyno= connect= service= status=503 bytes= protocol=httpsĪfter researching the error, it seemed that my Procfile was configured wrong. Immediately, I started getting an error telling me that there were no web processes running. I waited for my bot to start up and then sent a test POST request from DBL. ![]() I changed the webserver endpoint on Discord Bot List (DBL) to point to where my Heroku app was hosted, instead of pointing to my local machine. I cleaned up my code and merged my development branch with my primary branch, which was then picked up by Heroku’s automatic deployment. With that out of the way, I was ready to host my bot on Heroku. ![]()
0 Comments
Leave a Reply. |