Docs

Deployment Planning

Define the environment and acceptance criteria before a VPN automation rollout.

Describe Your Environment

  • WHMCS and PHP versions, client theme and billing workflow.
  • RADIUS server OS, database and API placement.
  • MikroTik RouterOS version, VPN protocol and network reachability.
  • Required speed profiles, session limits and accounting needs.
  • Expected client operating systems and IPv4/IPv6 requirements.

Test The Full Lifecycle

An evaluation should cover provisioning, connection, accounting updates, disconnect, suspension, unsuspension, package changes and termination. Check a separate customer session and verify that one account cannot retrieve another account’s credentials or history.

Capacity And Availability

A number of idle sessions does not establish throughput capacity. Measure expected traffic, router queues and backend load under realistic conditions. High availability and failover require their own design and acceptance testing.

Recovery

Coordinate application files, API configuration, database state and router behaviour. Restoring an old account database can reintroduce access that was previously revoked. Preserve current termination and accounting state when planning rollback.

Discuss Your Deployment

Send a sanitized environment summary to [email protected]. Do not include VPN passwords, API tokens, IPsec secrets or router exports in the initial enquiry.

Need help with this guide? Contact HERZA →

Search Documentation

Search across all products · Esc to close