diff --git a/docs.json b/docs.json
index dcf1507..bb07c20 100644
--- a/docs.json
+++ b/docs.json
@@ -11,57 +11,57 @@
"navigation": {
"tabs": [
{
- "tab": "Guides",
- "groups": [
- {
- "group": "Getting started",
- "pages": ["index"]
- },
- {
- "group": "Game hosting",
- "pages": [
- {
- "group": "FiveM",
- "pages": ["fivem/txadmin-setup"]
- },
- {
- "group": "Control panel",
- "expanded": true,
- "pages": [
- "game/sftp",
- "game/2fa",
- "game/users",
- "game/backups",
- "game/databases"
- ]
- }
- ]
- },
- {
- "group": "Web hosting",
- "pages": ["web/ssh"]
- },
+ "group": "Getting started",
+ "pages": [
+ "index"
+ ]
+ },
+ {
+ "group": "Game Servers",
+ "pages": [
+ "game/sftp",
+ "game/2fa",
+ "game/users",
+ "game/backups",
+ "game/databases",
{
- "group": "VPS hosting",
+ "group": "FiveM",
+ "expanded": false,
+ "icon": "house",
"pages": [
- {
- "group": "Windows VPS",
- "pages": [
- "windows-vps/add-user-rdp",
- "windows-vps/fivem-server-setup",
- "windows-vps/mariadb-setup"
- ]
- },
- {
- "group": "Linux VPS",
- "pages": [
- "linux-vps/fivem-server-setup",
- "linux-vps/mariadb-setup"
- ]
- }
+ "fivem/txadmin-setup",
+ "fivem/setup-resources"
]
}
]
+ },
+ {
+ "group": "Web Hosting",
+ "pages": [
+ "web/ssh"
+ ]
+ },
+ {
+ "group": "Windows",
+ "pages": [
+ "windows-vps/add-user-rdp",
+ "windows-vps/fix-installer-policy",
+ "windows-vps/fivem-server-setup",
+ "windows-vps/mariadb-setup"
+ ]
+ },
+ {
+ "group": "Linux",
+ "pages": [
+ "linux-vps/fivem-server-setup",
+ "linux-vps/mariadb-setup"
+ ]
+ },
+ {
+ "group": "Misc",
+ "pages": [
+ "misc/vnc-console"
+ ]
}
],
"global": {
diff --git a/fivem/setup-resources.mdx b/fivem/setup-resources.mdx
new file mode 100644
index 0000000..e36019b
--- /dev/null
+++ b/fivem/setup-resources.mdx
@@ -0,0 +1,41 @@
+---
+title: "Installation of FiveM resources"
+description: "How to setup FiveM resources on CentrixNodes Game Panel"
+icon: "server"
+---
+
+
+## Introduction
+
+Resources are a way you can expand your FiveM server with additional content. Such as scripts, cars, ymaps and more.
+This is interesting if you want to make your server more unique and personal.
+
+FiveM and its community forums have large variety of resources you can use. You can find some of the most popular resources here: [FiveM Resources](https://forum.cfx.re/c/development/releases/7)
+
+## Preparation
+
+The installtion of resources can either be done via the web file manager or SFTP. You can learn more about how to use SFTP [here](/game/sftp).
+
+
+Most downloaded resources are often delieved in a compressed format, such as a .zip or .rar file.
+You will need to extract the files before you can use them. You can use programs such as 7ZIP, winrar, winzip. Sometimes file unpackers will include the actually resource files in a subdirectory within the folder. Example: "script_name/script_name/files" Make sure to only use the "script_name/files"
+
+
+## Installation
+
+### Uploading files
+
+You must now upload the previously extracted files to your FiveM server. Your folder must be uploaded to your servers `resources` folder.
+
+### Activating resources
+
+To ensure the installed resource is loaded on server startup, you must first start the resource in your `server.cfg` file. This is done via the `start [example_resource]` command.
+
+For example, if you upload a resource with the name `vmenu`, The command will look like this:
+> `start vmenu`
+
+You can also access the `server.cfg` file via the CFG Editor in the txAdmin interface.
+
+
+Please ensure the name of your previously created folder is the same as what is found in the start command. Theses names are case sensitive.
+
\ No newline at end of file
diff --git a/game/databases.mdx b/game/databases.mdx
index d8896d0..6459c43 100644
--- a/game/databases.mdx
+++ b/game/databases.mdx
@@ -1,7 +1,36 @@
---
title: "How to use Databases"
-description: "Learn how to connect to databases using various methods and tools on our game panel."
+description: "Create a database in the game panel and connect from your server config or a MySQL client. The panel is powered by Pterodactyl."
icon: "database"
---
-### COMING SOON
\ No newline at end of file
+Our game panel provisions **MySQL** databases that are tied to your game server.
+
+## Open the Databases tab
+
+1. Log in to the **game panel**.
+2. Select your **server**.
+3. Open the **Databases** tab in the server sidebar.
+
+## View your database details
+
+1. Go to the **Databases** tab in your server sidebar.
+2. Locate your existing database in the list.
+3. Click the database entry or **View Details**
+
+The panel will display vital connection information:
+
+- **Host** — the hostname or IP to use in your application or client
+- **Port** — usually `3306` unless noted otherwise
+- **Database name**
+- **Username**
+- **Password** — click to reveal or copy; you can rotate it if the panel allows
+
+
+Treat the password like any production secret. Only paste it into your server config or a trusted client. If it is ever exposed, rotate it from the panel and update every place that still uses the old password.
+
+
+
+## Support
+
+If you have issues accessing your database, please feel free to contact us via our support channels.
\ No newline at end of file
diff --git a/misc/vnc-console.mdx b/misc/vnc-console.mdx
new file mode 100644
index 0000000..ebb7a01
--- /dev/null
+++ b/misc/vnc-console.mdx
@@ -0,0 +1,82 @@
+---
+title: "VNC console"
+description: "Enable and use VNC in the VPS control panel to access your VPS console when SSH or RDP is not available."
+icon: "display"
+---
+
+VNC lets you connect to your VPS as if you were at the physical console.
+VNC is especially useful when:
+
+- The VPS is not reachable over SSH or Remote Desktop
+- You need to troubleshoot boot or startup issues
+- You need access during OS installation
+- You want a direct console session
+
+## Step 1 — Log in to the client area
+
+1. Open your browser and go to your provider’s **client area** (billing portal) at [https://billing.centrixnodes.net](https://billing.centrixnodes.net).
+2. Sign in with your account credentials.
+
+## Step 2 — Open your VPS service
+
+1. Open the **Client** menu.
+2. Choose **My Services**.
+3. Select your **VPS** service.
+
+## Step 3 — Open the VPS control panel
+
+On the VPS service page, click **Open VPS Control Panel**. This opens the **VPS Panel** management UI for that server.
+
+## Step 4 — Open the Options tab
+
+In the vps panel, use the tabs at the top. Open **Options**.
+
+## Step 5 — Enable VNC
+
+In **Options**, find the VNC section and click **Enable VNC Access**. the panel creates a **temporary** VNC session for the server.
+
+## Step 6 — Connection details
+
+After VNC is enabled, the panel will show the session details, typically:
+
+- **IP address**
+- **Port**
+- **Password**
+
+You will usually also see **Browser VNC** and **Disable VNC Access**.
+
+## Step 7 — Use Browser VNC
+
+The simplest method is the built-in viewer:
+
+1. Click **Browser VNC**.
+2. Allow the new window or tab if your browser blocks pop-ups.
+3. Use the on-screen console to work on the server.
+
+## What you can do from the console
+
+With VNC you can:
+
+- Reach the login screen
+- Fix networking or firewall mistakes that locked you out
+- Observe or repair boot problems
+- Work through an OS installer
+
+## Disable VNC when done
+
+1. Return to the **Options** tab in vps panel.
+2. Click **Disable VNC Access**.
+
+This ends the session and reduces exposure.
+
+## Common issues
+
+**Browser VNC does not open** — Allow pop-ups, try another browser, or refresh the VPS panel panel.
+
+**Black screen** — The VM may still be booting. If the panel offers a safe reboot option, try that after waiting briefly.
+
+**Keyboard not responding** — Click inside the VNC window, then refresh or restart the VNC session.
+
+## Support
+
+If you cannot open the control panel or VNC after these steps, contact our support team and we will assist you.
diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 0000000..6ab6825
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,6 @@
+{
+ "name": "docs",
+ "lockfileVersion": 3,
+ "requires": true,
+ "packages": {}
+}
diff --git a/windows-vps/fix-installer-policy.mdx b/windows-vps/fix-installer-policy.mdx
new file mode 100644
index 0000000..805457a
--- /dev/null
+++ b/windows-vps/fix-installer-policy.mdx
@@ -0,0 +1,57 @@
+---
+title: "Fix Windows Installer Policy Error"
+description: "Resolve 'The system administrator has set policies to prevent this installation' on Windows VPS"
+icon: "wrench"
+---
+
+If you see this error when installing software on your Windows VPS, the **Windows Installer** is being restricted by Group Policy or Local Policy.
+
+
+
+## Where to fix it
+
+The policy is **"Turn off Windows Installer"** at:
+
+**Computer Configuration** → **Administrative Templates** → **Windows Components** → **Windows Installer** → **"Turn off Windows Installer"**
+
+Check in both places and apply the same fix in each:
+
+1. **Domain Controller (if applicable)**
+ Edit the GPO that applies to this computer and open the policy above.
+
+2. **Local policies**
+ On the VPS, run `gpedit.msc` and go to the same path.
+
+In that policy: set it to **Enabled**, then in the dropdown choose **Never**. Use this same setting in both GPO and local policy. Only **Enabled** with **Never** allows all installs; "Not configured" or "Disabled" does not reliably allow installs (on many servers the default is managed-only, so unmanaged installs stay blocked).
+
+
+Being a domain admin does not override this. The setting that applies is the one from the GPO scope that targets the computer (or the local policy if no GPO sets it).
+
+
+## DisableMSI registry behavior
+
+The policy writes to:
+
+**Registry key:** `HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer`
+**Value:** `DisableMSI`
+**Type:** `REG_DWORD`
+
+| DisableMSI | Behavior |
+|------------|----------|
+| **Default** (key absent or value not 1 or 2) | **Server 2003, 2003 R2, 2008, 2008 R2:** Installer enabled for managed apps only; unmanaged installs blocked. **XP, Vista, 7:** Installer enabled for all apps. |
+| **0** | Installer enabled for all applications. All install operations allowed. |
+| **1** | Installer disabled for unmanaged applications; enabled for managed. Non-elevated per-user installs blocked. Per-user elevated and per-machine installs allowed. |
+| **2** | Installer always disabled. No installs allowed (including repairs, reinstalls, or on-demand installs). |
+
+If you fix via registry instead of policy: set `DisableMSI` to **0** or delete it under `HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer` (and ensure no GPO overwrites it). The consistent fix in policy is **Enabled** → **Never**.
+
+## Reference
+
+[Windows Installer – DisableMSI (Microsoft Learn)](https://learn.microsoft.com/en-us/previous-versions/windows/desktop/msi/disablemsi)
+
+
+After setting the policy to **Enabled** → **Never** (or setting/removing the registry value), try the installation again. Reboot or run `gpupdate /force` if the change was made via GPO.
+