Varnish Cache Purge
Purge a URL or submit host-specific and global Varnish bans while understanding verification and scope limits.
Open Web Servers → Varnish → Varnish Cache Purge.
Purge a specific URL
- Enter the complete Full URL, including http:// or https://.
- Click Purge URL.
- Read the result and request the content again to verify freshness.
The helper checks the hostname against hosting-domain metadata, with a special case removing a leading www., then sends a PURGE request to the submitted URL using curl. Unlike the Nginx/OpenLiteSpeed helpers, this path does not rewrite the URL to a configured service port.
Use an ordinary hosted URL and confirm that its DNS and routing reach the intended cache. A public HTTPS endpoint may involve other web-stack components.
A request result is not a cache test
URL purge success is based on curl's process exit result, not a checked HTTP success status or proof that an entry was invalidated. Inspect the response and test the relevant content independently.
Purge a domain
The table shows Domain, Owner, account Status and Action. Search, sort or paginate to locate the intended site. The initial page size is 25, with 10, 50, 100 and All available. Suspended rows have no purge action.
- Click Purge domain cache.
- Review the domain in the confirmation.
- Click Purge Cache, or Cancel.
- Verify the intended host's responses.
The helper submits a Varnish ban matching the request Host exactly to the selected domain. Do not assume it also covers www, aliases, subdomains or every host representation. Review those separately when required.
The domain must exist in hosting metadata. The current implementation also requires curl to be installed even though this operation submits the ban through varnishadm. Some failure messages therefore use curl wording for an operation that actually invokes the Varnish administration tool.
Purge all cache
Click Purge All Cache, read the server-wide warning and confirm Purge Cache. This directly submits a broad Varnish URL ban through the administration tool. It is not the taskd submission used by the Nginx and OpenLiteSpeed global-purge menus.
Success means the administration command returned successfully, not that every cached object was synchronously erased or every following response was checked.
A broad invalidation can increase backend load. Prefer URL or domain scope when it meets the requirement.
Troubleshooting
Demo sessions cannot purge. Both pages require Varnish availability. URL purge needs curl; domain/global bans require working Varnish administration access and a running instance.
For Domain not found, verify the hostname and account metadata. For command, TLS or connectivity failures, inspect the reported details and logs before retrying.
If stale content persists, check aliases, cookies, cache variants and other cache layers. Purging does not change source content, enable caching or configure cache policy.