Key-based peers
WireGuard identifies a peer by its public key. Flirexa generates and stores the matching customer record, assigns an address, renders the configuration, and controls the peer on the live interface.
Why operators start here
A simple protocol still needs disciplined identity and address management
Cross-platform clients
WireGuard is available across Linux, Windows, macOS, Android, iOS, BSD, and other environments. Customers can import a configuration file or scan a QR code where the client supports it.
Small protocol surface
The official project emphasizes simplicity, modern cryptography, and a minimal implementation. That reduces protocol complexity but does not remove the need to secure the server, panel, DNS, or business accounts.
Operational lifecycle
Every device should have its own peer
Reusing one configuration on several devices makes troubleshooting and revocation ambiguous. In Flirexa, a device slot creates an independent client record and key pair.
- allocate the next safe address from the server pool
- generate a dedicated key pair and peer record
- apply the peer to the current WireGuard interface
- deliver a file or QR code through the admin panel or customer portal
- monitor handshake, traffic, expiration, and enabled state
- remove or regenerate one device without changing the others
FREE capacityOne local WireGuard endpoint and up to 80 total customers on the install
Business growthRemote nodes and up to 10 managed servers
DNSServer default, Business customer-selectable modes, or Enterprise enforced policy
MigrationPreserving a compatible server key and address model can reduce customer configuration changes
Common operational failures
Problems rarely come from the cryptography alone
Duplicate AllowedIPs
Two peers using the same tunnel address on one interface can displace each other's route and look like intermittent disconnects. Flirexa serializes allocation and provides an address-integrity audit.
Stale configuration after endpoint change
When the public endpoint or DNS changes, official applications can refresh it; manually downloaded configurations must be downloaded again.
Forwarding or NAT drift
A healthy interface does not prove internet reachability. Check kernel forwarding, firewall rules, provider firewalls, return routing, and the correct egress interface.
Configuration reuse
One peer on several physical devices hides the real device and weakens revocation. Use a separate device slot and configuration for each installation.
Protocol facts on this page are based on the official WireGuard documentation. Flirexa is an independent management platform and does not claim ownership of the WireGuard trademark or project.
Questions
WireGuard in Flirexa
Is WireGuard included without a paid licence?
Yes. FREE includes one local WireGuard endpoint, one local AmneziaWG endpoint, and up to 80 customers on the installation host.
Can I manage WireGuard in several countries?
Yes, with Business or Enterprise multi-server orchestration. Every compatible node is managed from the main installation.
Can customers download configurations themselves?
Yes. The separate customer portal delivers configuration files and QR codes within the device and subscription limits configured by the operator.