Select the server
Select the registered server in the sidebar before opening Cache. V2 shows that server’s configuration and analytics.Cache tabs
Purge cache
You usually do not need to purge after updating a resource. FiveM requests each resource version separately, so Cache fetches a changed file from your origin on its first request and serves it to later players. Purge when players still receive outdated files after an update, or when you want Cache to fetch every resource from your origin again. After a purge, the next requests are MISS responses until Cache warms up again, so avoid purging repeatedly while you measure performance.1
Open settings
In Cache, open the Settings tab.
2
Select the server
Confirm the server shown in the sidebar selector.
3
Purge
Click Purge under Purge cache.
Rotate the adhesive key
Rotate the key if the previousadhesive_cdnKey was lost or should no longer be trusted.
1
Open settings
Open Cache > Settings.
2
Rotate
Click Rotate under Adhesive key.
3
Copy the new block
Copy the generated
server.cfg block.4
Update your server
Replace the old Cache setup block in
server.cfg with the new block and restart or reload your server. Confirm the fileserver_add pattern is ".*" so it matches all resource names, and remove any older adhesive_cdnKey definitions in other configuration files. If several server instances share this configuration, update all of them.Disable or delete Cache
Before disabling or deleting Cache, remove itsfileserver_add line from server.cfg and reload or restart your server so players return to origin downloads. If the line stays in place, players keep requesting resources from the Cache URL and their downloads fail.
Use Disable Cache when you want to pause Cache for a server without removing the saved configuration.
Use Delete Cache configuration when you want to remove Cache settings for that server. The registered server remains in your account and can be enabled again later.
Analytics
Cache analytics can show:- Total requests.
- HIT and MISS ratio.
- Bandwidth served by Cache.
- Origin bandwidth saved.
- Average latency.
- Origin errors.
- Top file extensions and origin status rows.