Skip to content

Commit 2df8608

Browse files
committed
Create understanding-cfx-auth.mdx
1 parent 95a2d7d commit 2df8608

File tree

1 file changed

+74
-0
lines changed

1 file changed

+74
-0
lines changed

pages/understanding-cfx-auth.mdx

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: it-scripts - Understanding CFX Auth
3+
description: Understanding CFX Auth and common errors
4+
---
5+
6+
import { Callout } from '@components/Callout'
7+
import { Steps } from 'nextra/components'
8+
9+
# Understanding CFX Auth
10+
The **FiveM** asset escrow system secures assets by encrypting critical files, ensuring that exclusive **it-scripts** assets are protected against unauthorized use or modification.
11+
Below is a detailed guide to common errors and solutions, with titled sections for clarity.
12+
13+
## Failed to Verify Protected Resource
14+
This error usually means the files where corrupted during transfer.
15+
16+
<Steps>
17+
### Error
18+
Failed to verify protected resource (it_resourceName).
19+
20+
### Cause
21+
Files were corrupted during transfer.
22+
23+
### Solution
24+
- Ensure all files, including `.fxap`, are uploaded correctly.
25+
- Use [**WinSCP**](https://winscp.net/) instead of FileZilla for transferring files, as FileZilla might skip encrypted components.
26+
</Steps>
27+
28+
29+
## Failed to Verify Protected Resource
30+
This error occurs when your server license key is not linked to the account that purchased the asset.
31+
32+
<Steps>
33+
### Error
34+
You lack the required entitlement to use it_resourceName.
35+
36+
### Cause
37+
The server license key is not linked to the account that purchased the asset.
38+
39+
### Solution
40+
- Ensure the **server license key** is linked to the account that purchased the asset.
41+
- Restart your server after installation to apply any changes.
42+
</Steps>
43+
44+
## Syntax Errors
45+
This error can be caused by several factors:
46+
47+
<Steps>
48+
### Error
49+
Syntax error `<\/1>` or similar issues.
50+
51+
### Cause
52+
Outdated artifacts or attempts to edit encrypted code.
53+
54+
### Solution
55+
- Update to **artifact version 4960 or newer**.
56+
- Do not attempt to edit encrypted code, as it will lead to syntax errors.
57+
- Restart your server after installation to apply any changes.
58+
59+
</Steps>
60+
61+
## Recommendations
62+
<Steps>
63+
### Use the Latest Artifacts
64+
Always run **[artifact version 4960 or newer](https://runtime.fivem.net/artifacts/fivem/)** to avoid compatibility issues with the CFX Auth system.
65+
66+
### Use Reliable File Transfer Tools
67+
Switch to **[WinSCP](https://winscp.net/)** for transferring files to avoid corruption. FileZilla may skip encrypted components, leading to errors.
68+
69+
### Avoide Editing Encrypted Code
70+
Never attempt to edit encrypted code. This will lead to syntax errors and other issues. If you need to make changes, contact the asset developer for assistance.
71+
72+
### Restart Your Server Regularly
73+
After installing or updating assets, always restart your server to apply changes and ensure everything is functioning correctly.
74+
</Steps>

0 commit comments

Comments
 (0)