Skip to main content
Open Flow Studio → HAProxy Park: /new/connection-units?section=haproxy. The park belongs to the current project. Servers and pools are used by multiple Flows; old routing records Available through “Previous Configurations”.

Preparation and application

  1. Create a server with a common step-by-step wizard and select a node from the park. Use known addresses from the node inventory.
  2. Add the named connection: address, port, connection limit and Upload/download restrictions are required. Bind and source in additional settings.
  3. To balance, create a pool of server connections. Specify weights. Backup participants, algorithm and availability checks.
  4. On the Flow canvas, select a server with a connection or a pool. The traffic is set by the links of the blocks; a separate routing record is not required.
  5. Run Compile, check the plan, and run Apply Flow.
Save the park records the settings in the database. It doesn’t install HAProxy. It doesn’t use node configuration. Compile re-allows links. Include versions of resources in the plan and check for conflicts. Apply checks Agent, listeners and firewall before changing runtime. If the resource has changed after checking the plan, prepare an up-to-date plan. The created server opens the management page: ** Overview / Connections / Limitations / Settings . The pool has Composition / Balancing / Availability Checks **. Editing is carried out in the relevant section with explicit preservation. The resource or connection used cannot be deleted while it is referenced. current draft or active Flow image.

Port operations and rotation

To link to the applied Flow, HAProxy verification, drain and return are available The outcome is determined by the completed Agent task; the availability of the The agent does not prove that HAProxy is working. request_key does not create an independent problem; changing the parameters from the previous one The key is deflected. The connection can configure the range of ports, the interval in hours and the window Manual and scheduled rotations require at least one You pick a port that’s free in the park’s catalog, and then you launch it. Regular Apply with actual configuration check. Flows that use connectivity, including through a pool. State sequence: queued → applying → overlap → cleaning → succeeded. During overlap, new and old listeners work; after the compatibility window The first application error triggers the return of the main port. Cleaning error: Restore listener compatibility. Check failed. Error text and results affected by Flow: the rollback request has not yet been confirmed Successful recovery on each node. Do not start the next rotation while the previous one is active. One uncompleted transaction is allowed. Customers with an old subscription require Update it to the end of the compatibility window.

Restrictions

  • Pool doesn’t create VIP or DNS automatically. It requires one server.
  • The speed limit is common for connecting a single HAProxy process. It is not a VLESS user quota or the total budget of the entire pool. Old and new reload processes do not share the same budget.
  • Agent must confirm bandwidth_limits, weighted_backends, and port_overlap for related features. Unsupported configuration You don’t have to be silent.
  • The current TCP session is not transferred to another server in the event of an accident.
  • Quotas, Automatic Guard Scripts for the Park and Advanced Maintenance Windows from the product specification should not be considered ready for the presence of UI.

Verification

After saving, make sure that the server, connection and pool are displayed. Check the plan and outcome of each associated Flow. Run the HAProxy check and check the client route through the public entrance. When rotating, check the new and old ports during the window. Compatibility and completion of cleaning after it.

Rollback

Unused settings can be returned to the previous values and saved. After changing the working route, prepare and apply the corrected route. plan for those affected by Flow.In case of a rotation error, first examine the result port return; successful saving of settings does not confirm recovery Do not manually remove the old listener before checking client connections. For infrastructure outside of Axottle management, use an external entrance HAProxy or DNAT; importing such a service does not give the panel the right to manage it. Capabilities depend on the installed build; live network run within this reconciliation was not performed.