Clear cache in Cloudflare
Sometimes clearing the browser cache is not enough. If your site is connected through Cloudflare, copies of pages may be stored on their servers around the world. To make changes take effect immediately for all users, you need to purge the cache on the Cloudflare side.
After a full cache purge, the load on your origin server (Hetzner) will temporarily increase, and the site may feel slightly slower for the first visitors until Cloudflare creates fresh copies of the pages.
Step-by-step instructions
Step 1. Open the dashboard
Go to dash.cloudflare.com and sign in with your credentials.
Step 2. Select the site
In the list of zones (domains), choose the site whose data you want to refresh.
Step 3. Open the Caching section
In the left sidebar, open Caching → Configuration (or Overview, depending on the interface version).
Step 4. Full cache purge
If you made global changes to the design or structure:
- Find the Purge Cache button.
- Choose Purge Everything.
- Confirm the action in the popup.
Step 5. Selective purge (by URL)
If you only need to update one page or one image:
- Click Custom Purge.
- In the field that appears, enter the page URL. For example:
https://1it.pro/abouthttps://1it.pro/contacts - Click Purge.
Development mode
If you plan to make many changes within an hour and want to see them immediately without constant cache purges, enable Development Mode.
On the same Caching page, find the Development Mode switch and turn it On. This temporarily disables Cloudflare caching (for 3 hours), and requests will go directly to your server.
Automation (for 1it.pro developers)
We can set up an automatic Cloudflare cache purge every time you deploy new code through GitLab CI/CD.
Using the API lets us refresh the cache programmatically without opening the dashboard manually. If you need this setup, tell us.
Done! Cloudflare will now start serving the fresh version of your site.