Skip to main content
Use this page when the dashboard does not show the state you expected, or a FiveMesh service does not behave as configured on your FiveM server.

Access and workspaces

Service is locked

Check these in order:
  1. Confirm the correct workspace is selected.
  2. Confirm the resource owner’s account has active trial or subscription access. Billing shows your own subscription, even when you collaborate on another owner’s services.
  3. If you are in an organization, confirm the service is shared under Organization.
  4. Confirm your role allows access to the service.

Organization member cannot access a service

Ask an owner to check:
  • The member accepted the invitation.
  • The member has the intended role.
  • The organization is the active workspace.
  • The owner has made the service available to the organization.
  • The member has access to the intended server. Restricted server grants apply to read-only viewers.
  • The organization’s owner account has the required service subscription.

FiveMesh CDN

CDN setup is unavailable

Possible causes:
  • The workspace does not have active billing or trial access.
  • Your organization role can view CDN but cannot create the workspace.
  • The CDN workspace is already set up.
  • The workspace name is invalid or already used.
Workspace names must be 3 to 48 lowercase letters, numbers, hyphens or underscores, starting and ending with a letter or number.

CDN upload failed

Check:
  • You still have write permission for the active workspace.
  • The selected file batch contains 100 files or fewer.
  • The browser tab stayed open while the upload was running.
  • You are uploading to the intended folder path.
If one file fails in a batch, retry that file after the current upload finishes. For uploads from phone scripts or server code, see LB-Scripts troubleshooting, Quasar Phone troubleshooting or SDK troubleshooting.

Folder cannot be deleted

FiveMesh checks the folder before deletion. A folder can only be deleted when it is empty. Remove files and subfolders first, then retry deletion.

FiveMesh Cache

Cache setup is unavailable

Check:
  • The active workspace has billing or trial access.
  • The server is registered in Servers and selected in the sidebar.
  • Your organization role can create Cache configuration.
  • The selected server is not already enabled.

Players cannot connect after Cache is enabled

Check the selected server’s Cache origin and provisioning state.
  1. Confirm the public origin hostname and fileserver port in Cache > Settings.
  2. For a public HTTP IP endpoint, use the FiveMesh domain option during onboarding when available, or point your own domain at the same IP.
  3. Wait for domain provisioning to complete. A custom domain must resolve to the selected IP; an HTTPS origin also needs a valid certificate for its hostname.
  4. Compare server.cfg with the exact setup block generated by the dashboard, then restart or reload using your normal deployment process.
Do not replace the identifier in the generated Cache URL with the cfx.re join code. If the origin remains unreachable, contact support.

Resource downloads fail through Cache

When FiveM cannot download a resource, the client error or the F8 console often shows the HTTP status returned by the Cache URL. Use it to find the cause. If your origin is behind a reverse proxy, the proxy must return resource files uncompressed. A proxy that compresses responses on /files/ paths causes 502 errors through Cache. If players download resources directly from your server instead of through Cache, check that the fileserver_add line is in a configuration file your server actually executes, and that no later definition overrides it. See how the server.cfg lines work.

Players get download errors while the server runs fine

Players see resource download errors when joining, while players already in the game keep playing normally. The server itself stays online and reachable. This usually means a firewall or DDoS protection on the origin machine is blocking FiveMesh cache requests. Player game traffic still reaches the server, but cache misses are fetched by FiveMesh from Cloudflare’s network, and game host protection systems often filter that traffic. Common triggers:
  • The host’s automatic DDoS mitigation engages during a join rush, while many players download updated resources at once. These episodes often clear on their own after a few hours.
  • Firewall or protection rules changed, for example while setting up another FiveM server on the same machine. These errors persist until the rules change again.
  • Protection rules cover one FiveM server port on the machine but not another. Each server uses its own fileserver port, and each port needs the same rules.
To confirm the cause, open Cache > Analytics. Origin errors rise while the server logs show no matching download traffic, because FiveMesh requests are dropped before they reach the server. To fix it:
  1. Open Cache > Settings and note the origin URL and port for the affected server.
  2. Allow Cloudflare’s published IP ranges on that TCP port in the machine firewall and in the hosting provider’s protection panel. Follow the firewall and IP allowlisting guide for step-by-step instructions.
  3. Apply the same rule to every FiveM server port on the machine.
  4. If the hosting panel does not expose firewall or protection settings, ask the host to allow the ranges.
After the rules change, downloads recover on the next request. No purge or restart is needed.

Players still receive old resources

Cache fetches each new resource version from your origin on its first request, so an update normally reaches players without a purge. If players still receive outdated files:
  1. Confirm the updated resource is running on the server, for example by restarting it.
  2. Open Cache > Settings and confirm the server selected in the sidebar.
  3. Click Purge.
  4. Restart or reload your server if your deployment process requires it.

Adhesive key was lost

Existing adhesive_cdnKey secrets are not shown again. Rotate the key in Cache > Settings, copy the new server.cfg block, then update your server configuration.

FiveMesh Voice

Voice setup is unavailable

Check:
  • The active workspace has billing or trial access.
  • The active plan includes FiveMesh Voice.
  • The server is registered in Servers and selected in the sidebar.
  • Your organization role can create Voice instances.
  • The selected server does not already have an active Voice instance.
  • The workspace has not reached its Voice instance limit.
  • At least one Voice region is accepting new instances.

PMA-Voice does not connect to the endpoint

Check:
  1. Select the server in the sidebar and open Voice.
  2. Copy the latest PMA-Voice setup block from the instance detail page.
  3. Confirm voice_externalAddress contains only the hostname, without http:// or https://.
  4. Confirm voice_externalPort matches the port shown in the dashboard.
  5. Restart or reload your server using your normal deployment process.
  6. Confirm the instance status is online and the heartbeat updates.

Voice instance is stuck or shows an error

If an instance stays in provisioning, restarting or error state:
  • Refresh the instance detail page.
  • Use Retry provisioning if the connection is not ready and that action is offered.
  • Use Restart if the action is available.
  • Do not delete the instance while provisioning is still in progress.
  • Open a Discord ticket with the workspace, registered server ID, instance ID, region and visible error message.

Voice region is missing or unavailable

Voice regions can be limited, under maintenance or unavailable. If no region is accepting new instances, open a Discord ticket. Include the workspace, registered server ID and preferred region.

FiveMesh Logs

Logs events are missing

  1. Confirm the resource owner has Growth or Pro access, has activated Logs, and has enabled Logs for the selected server.
  2. Verify the key with Who am I?. Ingestion needs logs:write; querying needs logs:read.
  3. Keep the key in a server-only ConVar before ensure fivemesh-sdk. After rotation, update the key and restart the SDK.
  4. With a global Developer API Key, set FIVEMESH_SERVER_ID to the cfx.re join code. A Server API Key already supplies the identity.
  5. Enable FIVEMESH_LOGS_AUTOMATIC if you expect built-in events; check individual integration switches and dependencies.
  6. Confirm the Explorer time range and filters. Accepted ingestion can take time to become searchable.
See SDK troubleshooting and Logs operations.

Logs query is rejected

An SDK or public API query can span at most seven days. Use smaller ranges to search a longer retained period. Preserve the original query time bounds and filters when using a pagination cursor. For rate limits, wait before retrying. For authorization failures, check key permissions, the server binding and whether the Logs source still exists.

FiveMesh Portal

Portal is missing or player uploads are unavailable

Select the intended registered server and workspace first. Organization members also need access to that server and service. Check service sharing, server grants and your role if Portal reports an access problem. In Portal > Medias, check that uploads are enabled and the associated FiveMesh CDN is active. For an individual player, check Discord membership, role requirements, blocked uploaders and remaining daily attempts. Each player’s allowance is separate and resets at midnight UTC. See Portal operations for owner checks, or Upload media through Portal for player instructions.

What to include when asking for help

Include:
  • Active workspace type: personal or organization.
  • Service area: CDN, Cache, Voice, Logs, billing, organization or account.
  • Registered server ID and cfx.re join code when Cache, Voice, Logs or servers are involved.
  • Hosting provider, and whether other FiveM servers run on the same machine, when players see download errors.
  • The HTTP status or error shown in the FiveM client, F8 console or server console when resource downloads fail.
  • The action you tried.
  • The exact error message shown in the dashboard or SDK console. Include a request ID if the API returns one.
Never include API keys, adhesive keys, upload tokens or private player data in a public support message.