{"id":6052,"date":"2026-06-29T10:18:25","date_gmt":"2026-06-29T07:18:25","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6052"},"modified":"2026-06-29T10:18:25","modified_gmt":"2026-06-29T07:18:25","slug":"flush-restart-redis-cache","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/flush-restart-redis-cache\/","title":{"rendered":"How to Flush and Restart Redis Cache in SPanel"},"content":{"rendered":"\n

How to Flush and Restart Redis Cache in SPanel<\/strong><\/h2>\n\n\n\n

In SPanel, you flush or restart your account’s Redis cache from the Redis Cache<\/strong> section under Software<\/strong>, using the Flush Cache and Restart Redis controls – no SSH or root needed. <\/p>\n\n\n\n

Flush Cache clears the cached keys; Restart Redis restarts the per-account service. Both act on your whole per-account instance, not a single site’s keys, so expect a brief cold-cache slowdown right after. The live statistics on the same page let you confirm the effect.<\/p>\n\n\n\n

Who this is for<\/strong><\/h2>\n\n\n\n

This is for site owners and people running a managed VPS who have already deployed Redis and now need to clear it. The common cases: you pushed a deploy and the old cache is serving stale data, or the cache is misbehaving and you want a clean restart – done from the panel, without opening a shell.<\/p>\n\n\n\n

What problem this solves<\/strong><\/h2>\n\n\n\n

A cache that should be helping you is suddenly the problem. After a deploy, Redis may keep handing back values that no longer match what is on disk, so visitors see old pages or stale API responses. Or the service drifts – memory fills, clients pile up, responses slow. You need a way to empty the cached keys or bounce the service, and to confirm it worked.<\/p>\n\n\n\n

How SPanel solves this<\/strong><\/h2>\n\n\n\n

Open the Redis Cache page under Software > Redis Cache<\/strong>. On a deployed instance with status ON\/Active, you get a small set of controls: Flush Cache<\/strong> (the offline_bolt icon), Restart Redis<\/strong> (the sync icon), and Pause<\/strong>.<\/p>\n\n\n\n

Flush Cache clears the cached keys for your account’s Redis instance – the data is gone and the next requests rebuild it. Restart Redis restarts the per-account service, clearing in-memory state and resetting connections. The same page shows live Statistics<\/strong> – memory use, connected clients, and hits\/misses – so after you act you can watch the numbers reset and climb back as traffic warms the cache. SPanel runs the operation against your instance; rebuilding the cache and clearing any single site’s keys is still your job.<\/p>\n\n\n\n

Why this is different in SPanel<\/strong><\/h2>\n\n\n\n

Two things stand out<\/strong>. First, Flush Cache and Restart Redis run straight from the panel, scoped to your own per-account instance – no SSH or root, and you cannot touch another account’s cache. <\/p>\n\n\n\n

Second, the live Statistics sit on the same page as the controls, so you confirm a flush or restart on the spot: memory drops, hit\/miss counters reset, and you watch them recover.<\/p>\n\n\n\n

Before you start<\/strong><\/h2>\n\n\n\n
    \n
  • Confirm your Redis instance is deployed<\/strong> and shows status ON\/Active. If it is not deployed yet, deploy Redis first.<\/li>\n\n\n\n
  • You only need your normal SPanel user login<\/strong> – no root or SSH.<\/li>\n\n\n\n
  • Flush Cache is destructive: it empties all cached keys for the account. There is no undo, but the cache rebuilds from your application.<\/li>\n\n\n\n
  • Pick a low-traffic moment<\/strong> so the cold-cache dip affects fewer visitors.<\/li>\n<\/ul>\n\n\n\n

    Step-by-step<\/strong><\/h2>\n\n\n\n
      \n
    1. Sign in to SPanel and go to Software > Redis Cache<\/strong>. Confirm the instance – for example, the deployed yoga Redis – shows status ON\/Active. You should see the Flush Cache, Restart Redis, and Pause controls along with the live Statistics.<\/li>\n<\/ol>\n\n\n\n
      \"How<\/figure>\n\n\n\n
        \n
      1. Decide which action you need. To clear stale data, use Flush Cache<\/strong>. To reset in-memory state and connections without deliberately wiping keys, use Restart Redis<\/strong>. After a deploy, flushing is usually the right call.<\/li>\n\n\n\n
      2. Safety check before flushing: this empties every cached key for the account, not one site. Confirm you are on the correct account’s instance and that a brief slowdown is acceptable. When ready, click Flush Cache<\/strong>.<\/li>\n<\/ol>\n\n\n\n
        \"How<\/figure>\n\n\n\n
          \n
        1. Watch the Statistics. Memory use should drop and the hits\/misses counters reset. As traffic returns, misses rise first while the cache is cold, then hits climb as it warms – that pattern confirms the flush worked.<\/li>\n\n\n\n
        2. If you chose Restart Redis<\/em> instead, click it and expect current connections to drop for a moment while the service comes back. The Statistics reset as it restarts.<\/li>\n<\/ol>\n\n\n\n

          What happens behind the scenes<\/strong><\/h2>\n\n\n\n

          Flush Cache tells your account’s Redis instance to drop its keys; Restart Redis stops and starts the per-account service process. Both are scoped to your account alone, which is why you do not need root. Nothing on disk is deleted; Redis is a cache, so the source data lives in your database and files. <\/p>\n\n\n\n

          The safety property worth remembering<\/strong>: clearing the cache costs you a short rebuild, not your content.<\/p>\n\n\n\n

          Limitations and edge cases<\/strong><\/h2>\n\n\n\n
            \n
          • Flushing clears everything for that account’s Redis.<\/strong> All cached keys go and the next requests rebuild them, so expect a brief performance dip while the cache is cold. What to do: flush during quieter traffic and let it warm up before judging speed.<\/li>\n\n\n\n
          • Restart momentarily drops current connections.<\/strong> In-flight requests using Redis can be interrupted for a second or two. What to do: restart at a low-traffic moment and retry any failed request.<\/li>\n\n\n\n
          • Flush and Restart act on the whole per-account instance, not one site’s keys.<\/strong> If several sites share this Redis, all of them lose their cache. What to do: clear a single site’s keys app-side – through its caching plugin or framework, or by deleting keys by prefix – rather than flushing the instance.<\/li>\n<\/ul>\n\n\n\n

            Troubleshooting<\/strong><\/h2>\n\n\n\n
            Symptom<\/td>Likely cause<\/td>What to do<\/td><\/tr>
            No Flush Cache or Restart Redis buttons<\/td>Redis is not deployed or the instance is not ON\/Active<\/td>Deploy Redis first, then return to the page once status shows ON\/Active.<\/td><\/tr>
            Site still serves stale content after a flush<\/td>The app is caching elsewhere (page cache, CDN, browser)<\/td>Clear the app or CDN cache too; Redis is only one layer.<\/td><\/tr>
            Some requests error during a restart<\/td>Connections dropped while the service restarted<\/td>Retry the request; restart at a quieter time next time.<\/td><\/tr>
            Flush emptied another site’s cache too<\/td>Multiple sites share one per-account instance<\/td>Use app-side or prefix-based clearing for a single site.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            When to use this \/ when not to use this<\/strong><\/h2>\n\n\n\n
            Use this when<\/td>Skip or use something else when<\/td><\/tr>
            Stale data persists after a deploy<\/td>You only need to clear one site among several<\/td><\/tr>
            The cache is misbehaving and needs a clean restart<\/td>A cold-cache dip would hurt during peak traffic<\/td><\/tr>
            You lack SSH or root and need to act from the panel<\/td>You want to keep keys but tune the Redis memory eviction policy instead<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

            FAQ<\/strong><\/h2>\n\n\n\n

            Q: Does flushing delete my site’s actual data?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. Redis holds cached copies; your real data stays in your database and files. A flush only forces the cache to rebuild.<\/p>\n\n\n\n

            Q:<\/strong> Will a flush affect other sites on the account?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Yes, if they share the same per-account instance. Flush and Restart act on the whole instance, so clear a single site’s keys app-side or by prefix instead.<\/p>\n\n\n\n

            Q:<\/strong> Do I need SSH or root to do this?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. Both controls run from the SPanel Redis Cache page using your normal user login, scoped to your own instance.<\/p>\n\n\n\n

            Q:<\/strong> What is the difference between Flush Cache and Restart Redis?<\/strong><\/p>\n\n\n\n

            A:<\/strong> Flush Cache empties the cached keys but leaves the service running. Restart Redis bounces the service, resetting in-memory state and dropping current connections.<\/p>\n\n\n\n

            Q:<\/strong> Why is my site slower right after flushing?<\/strong><\/p>\n\n\n\n

            A:<\/strong> The cache is cold and rebuilding from scratch, so early requests miss and take the slow path. Watch the Statistics; performance recovers as keys repopulate.<\/p>\n\n\n\n

            Q:<\/strong> Is there an undo for a flush?<\/strong><\/p>\n\n\n\n

            A:<\/strong> No. But because the cache is derived data, your application rebuilds it automatically on the next requests.<\/p>\n\n\n\n