Skip to main content
Use this page when the dashboard does not show the state you expected.

Service is locked

Check these in order:
  1. Confirm the correct workspace is selected.
  2. Open Billing and confirm active trial or subscription access.
  3. If you are in an organization, confirm the service is shared under Organization.
  4. Confirm your role allows access to the service.

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 use lowercase letters, numbers and hyphens. They must be 3 to 48 characters.

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.

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.

Cache setup is unavailable

Check:
  • The active workspace has billing or trial access.
  • The server is registered under Account > Servers.
  • Your organization role can create Cache configuration.
  • The selected server is not already enabled.

Players cannot connect after Cache is enabled

Check whether the server connection endpoint or Cache origin uses a direct IP address. FiveMesh Cache should use a domain or subdomain for the server origin. Direct-IP endpoints can cause player connection errors after Cache is enabled. To fix it:
  1. Point a domain or subdomain at the server IP address.
  2. In Cache > Settings, select the server.
  3. Update Origin URL to use the domain or subdomain instead of the direct IP address.
  4. Save the origin and restart or reload your server if your deployment process requires it.
If you cannot provide a domain, open a Discord ticket to request a free FiveMesh subdomain.

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. The current ranges are listed at cloudflare.com/ips.
  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

If resources changed after Cache was enabled:
  1. Open Cache > Settings.
  2. Select the server.
  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.

Voice setup is unavailable

Check:
  • The active workspace has billing or trial access.
  • The active plan includes FiveMesh Voice.
  • The server is registered under Account > Servers.
  • 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. Open Voice and select the instance.
  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 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.

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 service is shared under Organization > Overview.
  • Billing access is active for the organization workspace.

What to include when asking for help

Include:
  • Active workspace type: personal or organization.
  • Service area: CDN, Cache, Voice, billing, organization or account.
  • Registered server ID when Cache, Voice or servers are involved.
  • Hosting provider, and whether other FiveM servers run on the same machine, when players see download errors.
  • The action you tried.
  • The exact error message shown in the dashboard.