Can I run WP Rocket on localhost and staging domains?
Local and staging domains
WP Rocket will work locally if you use one of the domain endings listed below, or just localhost.
Local installations don’t count as sites for licensing purposes, although they might show up in your website list on your WP Rocket account page.
Here are all the allowed domain endings:
.amazonaws.com.azurewebsites.net.bigscoots-staging.com.cloudwaysapps.com.cloudwayssites.com.dev.cc.docksal.dream.press.easywp.com.flywheelsites.com.flywheelstaging.com.hostingersite.com.hstgr.cloud.instawp.app.instawp.co.instawp.link.instawp.xyz.kinsta.cloud.kinsta.com.ksysweb.com-liquidwebsites.com.lndo.site.local.localhost.lyricalstaging.com.myftpupload.com.myhostpoint.ch.myraidbox.de.myrdbx.io.mystagingwebsite.com.ngrok.io.nxcli.io.nxcli.net.onrocket.site.pantheonsite.io.platformsh.site.preprod.preview.infomaniak.website.runcloud.link.sg-host.com.singlestaging.com.stage.site.staging.mysites.io.staging.tempurl.host.test.updraftclone.com.wp-cloud.dev.wpcomstaging.com.wpdns.site.wpengine.com.wpenginepowered.com.wpsc.dev.wpsc.site.wpserveur.net.wpstage.net.wpstagecoach.com.wptiger.fr
Features that don't work on intranet environments
Some WP Rocket features need to establish a connection with WP Rocket servers to perform different actions, such as validating the license and processing assets.
The following features don't work on private intranet environments:
- License validation (if you can connect the site to the Internet for initial validation, it can work offline after that, aside from the exceptions listed below)
- Plugin update notifications
- API Calls for RocketCDN (optional and paid feature), Cloudflare Add-on, and Sucuri add-on
- Load CSS Asynchronously
- Remove Unused CSS
You can see more information in the following article: