Skip to main content
FiveMesh Cache is a resource download proxy for FiveM servers. It reduces the bandwidth your server spends on resource downloads when players join. Players download resources through a FiveMesh cache URL instead of directly from your server. Cache hits are served from FiveMesh. Cache misses are fetched from your server, the origin, once and reused for later players.
FiveMesh Cache only handles the resource files FiveM downloads when players join. To host images, phone media or NUI assets at public URLs, use FiveMesh CDN. See CDN or Cache?.

Prerequisites

Before you enable Cache, confirm:
  • The resource owner’s account has trial or subscription access.
  • The cfx.re server is registered in Servers and selected in the sidebar.
  • You can edit your server’s server.cfg.
  • You or your host can edit firewall and DDoS protection rules for the origin machine.
  • Your organization role can create Cache configuration if you are in an organization workspace.
Cache needs a publicly reachable origin hostname. For a public HTTP IP endpoint, onboarding can provision a FiveMesh domain when available. You can also use your own domain pointing to the same IP. Direct IP origins and private or localhost addresses cannot be activated as-is.

Enable Cache

1

Open Cache

In the dashboard sidebar, open Cache.
2

Choose a registered server

Use the selector at the top of the sidebar to choose the server. Cache is scoped to that server; V2 has no all-servers Cache tab.
3

Enable Cache

Click Enable Cache. Confirm the detected origin endpoint or enter the public address and fileserver port manually.Choose an existing hostname, a FiveMesh domain for a supported public HTTP IP endpoint, or your own domain pointing to that IP. For your own domain, make sure DNS resolves to the selected server IP before continuing.Click Continue, review the endpoint and domain choice, then click Activate.
4

Copy the setup block

Copy the generated server.cfg block immediately.The block includes a fileserver_add line and an adhesive_cdnKey secret. If a FiveMesh domain is still provisioning, wait for it to become ready before directing player downloads through Cache.
5

Update server.cfg

Paste the block into your server configuration and restart or reload your server according to your normal deployment process.
Example shape (copy the exact URL and secret generated by your dashboard):
The adhesive key is only shown when it is created or rotated. If you lose it, rotate the key from Cache settings and update server.cfg.

How the server.cfg lines work

Keep the two lines together and follow these rules:
  • Paste both values exactly as generated. Do not add a trailing slash after /files, and do not replace the server identifier in the URL with your cfx.re join code.
  • Keep one fileserver_add and one adhesive_cdnKey definition. Search server.cfg, files loaded with exec and hosting panel settings for older values; a later duplicate can override the generated block.
  • Each registered server has its own Cache URL and key. Do not copy a block from another server or environment.
  • Keep the key out of client resources, screenshots, public repositories and support messages. Rotate it from Cache operations if it is exposed.
For background on both commands, read How to configure fileserver_add and adhesive_cdnKey.

Origin URL

FiveMesh detects candidate endpoints for the registered cfx.re server. Choose the public endpoint that serves resource downloads, including the correct port. The generated Cache URL identifies the FiveMesh registration, not the cfx.re join code. Always copy the dashboard’s URL rather than constructing it yourself. Managed domains support public HTTP IP endpoints. For an HTTPS origin, use a hostname with a valid certificate. If the managed domain option is unavailable, use your own domain or contact support.

Allow FiveMesh to reach your origin

FiveMesh fetches cache misses from your origin through Cloudflare’s network. Game host firewalls and DDoS protection often filter data center traffic while allowing player traffic. If the origin machine or your host protects the fileserver port, allow Cloudflare’s published IP ranges on that TCP port before you enable Cache. The current ranges are listed at cloudflare.com/ips.
If the machine runs several FiveM servers, apply the same rule to every fileserver port. Protection rules that cover only one port cause download errors for the other servers.
New to firewalls? Follow Allow FiveMesh Cache through your firewall for the exact rule settings and Windows, Linux or hosting-panel instructions. If downloads fail after Cache is enabled while the server runs normally, see players get download errors while the server runs fine.

Verify Cache is working

  1. Restart or reload your server after updating server.cfg.
  2. Join from a client that does not already have your current resources. A client with a warm local cache skips most downloads and does not test the Cache path.
  3. Open Cache > Analytics for the selected server. The first requests for each resource version are MISS responses fetched from your origin; later players should receive HIT responses.
  4. Check origin errors separately from MISS traffic. A MISS is expected; a rising origin error count means FiveMesh cannot fetch files from your server.
If players cannot download resources, see resource downloads fail through Cache.

Next steps