{"id":4452,"date":"2026-08-20T03:43:31","date_gmt":"2026-08-20T03:43:31","guid":{"rendered":"https:\/\/tucumandevelopers.com\/index.php\/2026\/08\/20\/how-to-stop-your-discord-bot-from-sleeping-on-renders-free-tier\/"},"modified":"2026-08-20T03:43:31","modified_gmt":"2026-08-20T03:43:31","slug":"how-to-stop-your-discord-bot-from-sleeping-on-renders-free-tier","status":"publish","type":"post","link":"https:\/\/tucumandevelopers.com\/index.php\/2026\/08\/20\/how-to-stop-your-discord-bot-from-sleeping-on-renders-free-tier\/","title":{"rendered":"How to Stop Your Discord Bot From Sleeping on Render’s Free Tier"},"content":{"rendered":"
\n
\n
\n
\n

A step-by-step tutorial to stop a discord bot from sleeping on Render’s free tier \u2014 the real cause, the fix, and a working code example.<\/p>\n<\/blockquote>\n

<\/a> How to Stop Your Discord Bot From Sleeping on Render’s Free Tier <\/h2>\n

You’ve deployed your Discord bot to Render’s free tier, it worked for a bit, and now it’s going offline \u2014 sometimes after a few minutes, sometimes randomly. This is one of the most common issues developers hit deploying a bot for the first time, and it has a specific, well-understood cause and a fix you can ship in under ten minutes.<\/p>\n

<\/a> Table of Contents <\/h2>\n
    \n
  1. Why This Happens on Render Specifically<\/li>\n
  2. Confirming This Is Your Actual Problem<\/li>\n
  3. Step 1: Install StayPresent<\/li>\n
  4. Step 2: Wrap Your Bot’s Entry Point<\/li>\n
  5. Step 3: Read Render’s Assigned Port<\/li>\n
  6. Step 4: Set Your Render Start Command<\/li>\n
  7. Step 5 (Optional): Prevent Inactivity Sleep Specifically<\/li>\n
  8. Verifying It Worked<\/li>\n
  9. FAQs<\/li>\n
  10. Conclusion<\/li>\n<\/ol>\n

    <\/a> Why This Happens on Render Specifically <\/h2>\n

    Render’s free-tier web services are checked for health over HTTP, and free services also spin down after a period without incoming traffic. A discord.py bot connects outward<\/em> to Discord’s gateway \u2014 it never opens an HTTP port of its own, which is completely normal bot behavior. Render’s health checker, seeing nothing respond on the expected port, has no way to know the bot is actually working fine internally. It just sees silence, and reacts accordingly.<\/p>\n

    <\/a> Confirming This Is Your Actual Problem <\/h2>\n

    If your bot’s entry point goes straight into bot.run(TOKEN)<\/code> with nothing else, and Render’s dashboard shows the deployment as unhealthy or repeatedly restarting with no matching error in your bot’s own logs, this is almost certainly it.<\/p>\n

    <\/a> Step 1: Install StayPresent <\/h2>\n
    \n
    pip install <\/span>staypresent[prod] <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
    Add it to your requirements.txt<\/code> as well: <\/p>\n
    \n
    staypresent[prod] discord.py <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
      <\/a> Step 2: Wrap Your Bot’s Entry Point <\/h2>\n
    Keep your existing bot code in bot.py<\/code> completely unchanged. Create a new main.py<\/code>: <\/p>\n
    \n
    import<\/span> os<\/span> import<\/span> staypresent<\/span> staypresent<\/span>.<\/span>web<\/span>.<\/span>json<\/span>({<\/span>\"<\/span>status<\/span>\"<\/span>:<\/span> \"<\/span>running<\/span>\"<\/span>})<\/span> staypresent<\/span>.<\/span>run<\/span>(<\/span>\"<\/span>bot.py<\/span>\"<\/span>)<\/span> <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
      <\/a> Step 3: Read Render’s Assigned Port <\/h2>\n
    Render injects a PORT<\/code> environment variable \u2014 your app needs to bind to it dynamically, not a hardcoded value: <\/p>\n
    \n
    import<\/span> os<\/span> import<\/span> staypresent<\/span> staypresent<\/span>.<\/span>web<\/span>.<\/span>json<\/span>({<\/span>\"<\/span>status<\/span>\"<\/span>:<\/span> \"<\/span>running<\/span>\"<\/span>})<\/span> staypresent<\/span>.<\/span>run<\/span>(<\/span> \"<\/span>bot.py<\/span>\"<\/span>,<\/span> port<\/span>=<\/span>int<\/span>(<\/span>os<\/span>.<\/span>getenv<\/span>(<\/span>\"<\/span>PORT<\/span>\"<\/span>,<\/span> 8080<\/span>)),<\/span> )<\/span> <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
      <\/a> Step 4: Set Your Render Start Command <\/h2>\n
    In Render’s service settings, set the start command to run your new entry point: <\/p>\n
    \n
    python main.py <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
    Deploy. Render now has something to check on, and your bot’s own logic \u2014 the actual discord.py code \u2014 didn’t change at all.<\/p>\n
      <\/a> Step 5 (Optional): Prevent Inactivity Sleep Specifically <\/h2>\n
    Solving the port requirement alone stops Render from marking the deployment unhealthy. If Render’s free tier is also<\/em> spinning your specific service down after inactivity, add a self-ping targeting your own public URL: <\/p>\n
    \n
    import<\/span> os<\/span> import<\/span> staypresent<\/span> staypresent<\/span>.<\/span>web<\/span>.<\/span>json<\/span>({<\/span>\"<\/span>status<\/span>\"<\/span>:<\/span> \"<\/span>running<\/span>\"<\/span>})<\/span> staypresent<\/span>.<\/span>cron<\/span>(<\/span>\"<\/span>https:\/\/your-app-name.onrender.com<\/span>\"<\/span>,<\/span> interval<\/span>=<\/span>240<\/span>)<\/span> staypresent<\/span>.<\/span>run<\/span>(<\/span> \"<\/span>bot.py<\/span>\"<\/span>,<\/span> port<\/span>=<\/span>int<\/span>(<\/span>os<\/span>.<\/span>getenv<\/span>(<\/span>\"<\/span>PORT<\/span>\"<\/span>,<\/span> 8080<\/span>)),<\/span> )<\/span> <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n
    This has to target your actual onrender.com<\/code> URL \u2014 pinging 0.0.0.0<\/code> or 127.0.0.1<\/code> never leaves the machine and won’t count as external activity.<\/p>\n
      <\/a> Verifying It Worked <\/h2>\n
    After deploying, check Render’s dashboard \u2014 the service should show as healthy rather than restarting in a loop. You can also visit your app’s \/health<\/code> endpoint directly in a browser; it should return {\"status\": \"ok\"}<\/code>. If you’re on a recent version of StayPresent, \/status<\/code> shows a live status page with uptime history, which is a quick way to confirm the bot is staying up over time rather than just checking once.<\/p>\n
      <\/a> FAQs <\/h2>\n
    Do I need to change my bot’s actual Discord logic?<\/strong>
     No \u2014 bot.py<\/code> stays exactly as it was. Only the entry point Render runs (main.py<\/code>) is new.<\/p>\n
    Does this work for Telegram bots too?<\/strong>
     Yes \u2014 the same pattern applies to any long-running Python process that doesn’t open its own HTTP port, regardless of which platform’s API it talks to.<\/p>\n
    Will this cost anything?<\/strong>
     No \u2014 StayPresent is MIT licensed and free, and this setup doesn’t require upgrading your Render plan.<\/p>\n
      <\/a> Conclusion <\/h2>\n
    A Discord bot sleeping on Render’s free tier is almost always a missing HTTP port, not a bug in your bot. Wrapping your existing bot.py<\/code> in staypresent.run()<\/code>, reading Render’s PORT<\/code> variable, and optionally self-pinging your public URL solves it completely, with zero changes to your bot’s actual code. <\/p>\n
    \n
    pip install <\/span>staypresent[prod] <\/code><\/pre>\n
    \n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n<\/div>\n<\/div>\n
    Fuente: Art\u00edculo original<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
    A step-by-step tutorial to stop a discord bot from sleeping on Render’s free tier \u2014 the real cause, the fix, and a working code example. How to Stop Your Discord Bot From Sleeping on Render’s Free Tier You’ve deployed your Discord bot to Render’s free tier, it worked for a bit, and now it’s going […]<\/p>\n","protected":false},"author":1,"featured_media":4451,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"webixso_pending_account_ids":""},"categories":[41],"tags":[],"class_list":["post-4452","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devto"],"jetpack_publicize_connections":[],"_links":{"self":[{"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/posts\/4452","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/comments?post=4452"}],"version-history":[{"count":0,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/posts\/4452\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/media\/4451"}],"wp:attachment":[{"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/media?parent=4452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/categories?post=4452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tucumandevelopers.com\/index.php\/wp-json\/wp\/v2\/tags?post=4452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}