DE

↑ ↓ select, Enter open, Esc close

Purge LiteSpeed Cache for a WordPress site with WP-CLI

cautionLiteSpeeddebian, ubuntu

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
user@server
wp litespeed-purge all --path=/var/www/vhosts/example.com/httpdocs

Uses the WP-CLI commands shipped with the LiteSpeed Cache plugin and discards all cached pages. Useful after deployments or theme changes when visitors still see old content. Run the command as the webspace user, not as root.

Note: Right after purging, server load rises briefly until the cache is warm again.

Open question before approval: Unterbefehl wp litespeed-purge all mit aktueller Version des Plugins LiteSpeed Cache prüfen.

Also searched as

  • clear litespeed cache wordpress
  • lscache purge all
  • wordpress clear cache command line litespeed

Related one-liners

All in LiteSpeed

Check the Redis Object Cache status in WordPress

$wp redis status --path=/var/www/vhosts/example.com/httpdocs
harmlessRedis and Memcached

Check if LiteSpeed Cache serves a page from cache

$curl -s -o /dev/null -D - https://example.com/ | grep -iE "^(server|x-litespeed-cache[a-z-]*):"
harmlessLiteSpeed

Check WordPress core files for tampering

$wp core verify-checksums --path=/var/www/vhosts/example.com/httpdocs
harmlessWP-CLI

Count WordPress plugins by status

$wp plugin list --format=json --path=/var/www/vhosts/example.com/httpdocs | jq -r 'group_by(.status)[] | "\(.[0].status): \(length)"'
harmlessText processing

Flush the WordPress object cache

$wp cache flush --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Update WordPress core including the database

$wp core update --path=/var/www/vhosts/example.com/httpdocs && wp core update-db --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.