Flirexa / Installation

Before you begin

Install Flirexa on Your Server

Use a clean supported control server. Plan the domain and payment accounts before inviting customers, but do not expose the panel until web access is configured deliberately.

AccessUse root or a sudo-capable user and ensure your provider firewall allows the ports you deliberately expose for SSH, HTTPS and each chosen VPN protocol.
Domain and DNSA domain is not required to begin locally, but a public service needs DNS you control and valid HTTPS for the admin and customer portals.
CompatibilityThe installer checks whether AmneziaWG packages exist for the detected Ubuntu release. If they are unavailable, it shows a clear warning and asks whether to continue with WireGuard only.

One installer for every plan

Run the official installer

The same official installer deploys Flirexa for Community Edition, a 7-Day Enterprise Trial, or a purchased Starter, Business or Enterprise license.

Use the installer from an interactive SSH session

It detects the host, checks compatibility, deploys the required runtime components and verifies the resulting services. Start with a clean server rather than one that already carries another VPN panel, custom firewall rules or a conflicting web stack.

curl -fsSL https://flirexa.biz/install.sh | sudo bash

What the installer creates

The runtime layout, locked Python environment, local PostgreSQL database, managed services, initial local VPN endpoints, health checks, update tooling and rollback-safe backups.

Web access

Decide whether Flirexa will configure its initial web access or whether you will supply HTTPS through your own reverse proxy. For a production domain, point DNS at the server, issue a trusted certificate and keep raw application ports private behind the proxy.

Choose when to activate

Request a 7-Day Enterprise Trial or buy a license first and enter its code during installation. You can also install first, then activate the appropriate plan in Settings > License without reinstalling.

DatabasePostgreSQL is installed and managed locally on the control server. Schema migration and API health are verified before success is reported.
First accountCreate the first administrator at the initial visit to the admin panel. The installer does not create a default administrator account.

Community Edition

If you do not enter an activation code, Flirexa starts in Community Edition for personal use with one server and up to 20 clients.

Trial activation codes are valid for 3 days. The 7-day Enterprise trial begins after successful activation.

Request 7-Day Enterprise Trial

After Installation

Verify the whole customer path before selling

A healthy service is more than a successful installer exit. Complete this first-launch checklist once in a fresh browser and on a real device.

  1. Open the admin panel and change the administrator password.
  2. Configure the domain and trusted HTTPS.
  3. Add the first VPN server and install its agent when required.
  4. Create the first plan and configure the client portal.
  5. Configure eligible payment methods.
  6. Create a test customer.
  7. Create a device and retrieve its configuration.
  8. Connect from a real client device.
  9. Open a support request from the customer view.
  10. Confirm health, backups and licensed status before inviting customers.
Contact Support