How to Use Azuriom Instead of a Tebex Website for FiveM

You can use Azuriom to build your FiveM community website and make it the destination players visit instead of a standalone Tebex storefront. Use it for your homepage, rules and community information; connect your game server through AzLink. For paid server packages, keep Tebex in the payment flow: Cfx.re’s current documentation identifies Tebex as the exclusive monetization provider and prohibits other payment platforms for this purpose. Read the Cfx.re monetization requirements before configuring sales.

This tutorial covers website installation, the official AzLink-FiveM resource and a practical launch checklist. It is based on documentation and source review on November 9, 2026; it does not claim an end-to-end FXServer or payment test. Azuriom lists FiveM as a supported game in its documentation. The bridge code reviewed here is commit d2c76cbdf4f7561bf7943aed8524bbce67a9ebc2 of the official repository; its latest published release at review time is v0.1.1.

Choose what you want Azuriom to replace

A community website and a payment service solve different problems. The useful starting arrangement is a self-hosted Azuriom site with a visible Store navigation link to your existing Tebex webstore. This keeps website editing separate from package checkout and fulfillment. You can launch the website before attempting any deeper commerce integration.

AzLink is a separate connection between Azuriom and FXServer. It exchanges server information and can dispatch commands returned by the website. Installing it does not connect your Tebex purchases automatically, import subscriptions or transfer customer records. The official AzLink-FiveM repository documents the resource; our Azuriom and Tebex comparison covers the broader software and commerce differences.

Keep direct Stripe or PayPal checkout out of this FiveM server-monetization setup. An available payment plugin does not establish permission to use that payment route for your server.

1. Prepare hosting and preserve the working setup

You need a web-hosting account or VPS for Azuriom, a domain with HTTPS, database access, and permission to manage your FXServer resources and server console. Azuriom is a PHP application; placing its files in a FiveM resources folder will not create a website.

At the review date, the official installation requirements specify PHP 8.2 or newer, the listed PHP extensions, and symlink support. MySQL/MariaDB or PostgreSQL is recommended. Ask the host to check the full requirements rather than relying on a plan described only as “PHP hosting.”

Before changing anything, save a copy of server.cfg, any existing AzLink folder and the current website configuration. If replacing an existing CMS, back up both its files and database. Start on a separate hostname so the existing website and store remain available during acceptance. Record how to restore DNS and the previous web-server configuration.

Checkpoint: your intended hostname loads over HTTPS and you can access the hosting panel, database and FXServer console. Keep database passwords and bridge keys out of screenshots and public support posts.

2. Install the Azuriom website

Download the installation package from Azuriom’s official website. Upload and extract it into the website location configured by your host, including hidden files. Follow the upstream web-server instructions; for Nginx, the documented application document root ends in /public.

Open the site in a browser, complete the installer, supply the database connection and create the first administrator. Select the FiveM identity option appropriate for your community. The bridge distinguishes Steam-based and Cfx-based identities, so keep the website’s choice consistent with your player accounts. Do not assume a Discord display name is the game identifier.

Use the installation guide for scheduled tasks when enabled features require them. Keep production debug output disabled, restrict file access according to your host’s deployment model and verify that private configuration files cannot be downloaded.

Checkpoint: sign in as administrator, save a small content change, then view it while signed out. Check that a regular account cannot open administration pages. A homepage loading successfully is only the first of those checks.

3. Make the site useful before connecting commerce

Create the pages players need: server introduction, join instructions, rules and a clear support contact. Put the store in the main navigation and use your existing Tebex store URL as its destination. Test that link from a signed-out browser and on a phone.

Use a theme that keeps those tasks easy to find. Install extensions only for features you intend to operate, and record their versions so future updates can be tested against the same configuration. For a wider planning checklist, see our guide to creating a website for a FiveM server.

Checkpoint: a new visitor can find the server’s joining instructions, rules, support and store without using an administrator session.

4. Install the official AzLink-FiveM resource

Download the resource from the repository’s Releases page. Extract it so that the resource root is named azlink, directly containing fxmanifest.lua and its server directory. Avoid an extra nested archive folder.

resources/
└── azlink/
    ├── fxmanifest.lua
    └── server/

For the initial start, the upstream README uses these server-console instructions. Run refresh first if you added the folder while FXServer was already running:

refresh
start azlink

For startup after a server restart, add the resource to server.cfg:

ensure azlink

The bridge’s manifest declares a server-only resource; these instructions do not install an ESX, QBCore or Qbox gameplay integration. Commands that affect characters or inventories need their own Framework-specific implementation and testing. This source review does not establish separate GTAV Legacy and Enhanced runtime acceptance.

Checkpoint: FXServer reports that the resource started without a missing-manifest or script error. That establishes startup, not a working website connection.

5. Link FXServer to the website

In Azuriom’s administration area, add your game server in Servers. Use the setup values shown for that server. The reviewed command implementation accepts the website base URL followed by the site key:

azlink setup https://community.example.com YOUR_SERVER_SITE_KEY
azlink status
azlink fetch

https://community.example.com and YOUR_SERVER_SITE_KEY are placeholders. Run the real setup in the server console, with the values from your own dashboard. The resource appends /api/azlink to the base URL itself; do not append it again. Keep the key private.

On successful setup, the resource saves its connection settings to config.json inside the resource directory. Preserve that file when updating the resource. Treat its backup as sensitive because it contains the bridge credential. Check the result again after a resource restart so a temporary in-memory connection does not hide a failed configuration save.

Checkpoint: status confirms connectivity, fetch completes, and the website reflects the connected server. Join with a test account and compare the player information with FXServer. Verify the selected identity mode before attempting player-specific actions.

6. Keep paid packages on the Tebex path

For the simplest launch, retain the navigation link to your Tebex webstore. Configure paid package delivery through the existing Tebex connection, and do not duplicate those actions in AzLink. If you still need that connection, our FiveM Tebex store setup tutorial explains the store side.

If you want package browsing inside Azuriom later, the marketplace lists a third-party Tebex Integration extension by Bricec6. Its listing describes a Tebex Headless API integration. Review its current compatibility, dependencies and maintenance before adopting it. This article has not tested that extension, so the basic setup above does not depend on it.

Before taking a new purchase flow live, verify account identification, the actual checkout destination, package delivery and the support route. Keep purchase history and active subscriptions in the working system until a separately tested migration exists. A website redesign is not evidence that those records or renewal agreements moved.

Troubleshooting AzLink

The resource cannot be found

Check the folder name and nesting. The manifest belongs at resources/azlink/fxmanifest.lua. Refresh the resource list after adding files, then inspect the first server-console error.

The resource starts, but the website is disconnected

Check the configured HTTPS base URL and matching server key. The HTTP client calls the website’s /api/azlink endpoint. Review website access/error logs for that path. DNS failures, TLS problems, redirects to another hostname, authentication gates or browser challenges can prevent FXServer from receiving the expected API response.

Fix access for the intended API route without disabling protection across the whole website. When asking for help, provide the HTTP status, timestamp and resource version; redact credentials and player identifiers.

Status works, but the player or action is wrong

Check Steam versus Cfx identity matching, the player’s current connection and the target command’s requirements. The bridge substitutes player information into commands and executes them through the server console. A successful HTTP request cannot prove that the command made the intended gameplay change.

Use a harmless action with a test account first. Test disconnected-player behavior separately before relying on an action that expects an online server ID. Website administration and bridge credentials therefore deserve the same care as other paths capable of triggering server commands.

Launch and rollback checks

Launch once the signed-out website, ordinary-user permissions, mobile navigation, persistent bridge connection and intended Tebex purchase path have been checked. Keep a record of the CMS, extension and resource versions, the date and what you actually tested.

If the website connection causes trouble, return visitors to the previous website, restore its configuration and database where needed, and stop AzLink while investigating. Restore the saved resource configuration only when it still matches the intended website and server record. Keep the existing commerce system available throughout the change.

Azuriom gives you control over the website players use. For a FiveM server, this guide keeps Tebex responsible for the monetization flow while AzLink handles the website-to-server connection.