Skip to main content
Axosun is currently unavailable, and its return to service is not planned in the near future.
Everything that Axosun can do is described in a fixed action directory, and the model can only offer actions from that directory, and a sentence that the product doesn’t know is rejected before it’s shown to the operator, and there’s one special action in the directory to run a command on the server, and it only works for a specific node, and it always requires a separate operator confirmation. Each action in the directory carries a level of risk and the sign “requires confirmation”: The directory is available for viewing in the panel: section Axosun → tab Action Catalog.
Administrator/SRE Required Rights: Reading the directory is available to any panel administrator; the actual availability of actions is determined by Axosun Policy.

Diagnosis and health

Read-only checks - performed without confirmation:
  • collection of logs, launch of health-checks, synthetic samples - see Health System Review;
  • Updating health, providers, CDNs and subscription infrastructure;
  • verification of DNS, TLS certificates, GeoAssets status, backup status, WARP status;
  • Proxy connectivity check, Flow route test, security profile check;
  • Node filtration, massive TLS and WARP checks;
  • inspection of Flow topology, a test of the connection “node → node”;
  • Failure classification, configuration validation and lint, Xray configuration trial run, comparison of expected and actual configuration;
  • Diagnostic scenarios, search documentation and runbooks.

Nodes and mass operations

Service layer (medium risk, with confirmation): restart Xray, remnanode or Axottle agent; update agent (on one or all nodes); issue TLS certificate; launch backup profile; plan to change DNS; create an A-record in Cloudflare. Node Level (High Risk, Confirmed): output node from rotation and return to rotation (drain/undrain – node is removed from the draft graphs of all Flow and returned back); installation of WARP; application of a safety profile. Mass operations use a typed node selector (all nodes, a list of identifiers, country, provider, region, tags, etc.) and are limited in scope: by default no more than 50 nodes per operation, a rigid maximum of 200. For mass operations, approvals are available - one approval for a limited amount of time, see Law Model.

Team on the server

is designed to run a command on the server for narrow diagnostics when conventional tools have not responded, for example, it helps to check docker ps, the state of Docker through systemctl status, journalctl logs, free space or network sockets on a selected node. Axosun shows the exact command, the short explanation, and the node on which it will be launched on the confirmation card. The operator confirms or rejects each command separately. The action is not performed automatically, including in auto_safe_actions mode; approval lease is not used for it. By default, the assistant offers only read-only commands; it can only offer a changing command at the explicit request of the operator. There is no automatic rollback for such commands: the operator must understand the effect and prepare the reverse action independently. The command is executed through the Axottle Agent on one node. The standard run time is 30 seconds, the maximum run time is 120 seconds. If the agent is unavailable, the command will stay in line or end in an error, and the panel will show its status.
Starting a command does not replace specialized actions of Axosun. To restart services, reboot the server and change the firewall, use the appropriate actions from the directory.

Flow

High-risk activities require confirmation and are further limited by the configuration experiment policy (see Law Model):
  • Creating a configuration draft or Flow;
  • changing the Flow settings;
  • preview of the canvas, editing the draft of the graph, testing the draft;
  • Applying a draft to production, rolling back Flow.
The graph corrections apply only to the draft, and the production application is a separate action with a separate confirmation.

Requests for Remnawave

Access to Remnawave is closed by default and opens with a master switch in policy - see WEB The model of rights. Reading: Flow coverage definition, resource graph, drift detection, resource search, recent events, current lists of nodes/hosts/configuration profiles/internal squads/subscription templates; estimation of the number of affected users (counters only); tracing of subscription projection (counters only, never URL). Data and privacy. Recording (destructive, always confirmed): only typed operations - updating the host, turning on the node, disabling the node, assigning a node configuration profile.

Incidents

Axosun saves the problems found as lifecycle incident cards: open → work → waiting for resolution → fix applied → checked → solved (or blocked / operator required / ignored). Repeated reports update the description of the incident, but do not reset the status set by the operator. The “solve in order” command only lines up the order - it never performs the corrections automatically.

Response to abuzas

  • Collection of sanitized abuza certificates - read-only, allowed by default.
  • Temporary deceleration (QoS) for a particular user and its withdrawal is a deliberately non-destructive measure that requires confirmation.

Assistant’s notes

During launch, Axosun publishes short notes: what step to start, why the check is done, what decision was made, how the validation ended, notes are visible in the launch stream and help the operator monitor the progress of work.

Destructive actions

Always require confirmation, regardless of the policy regime:
  • server reboot (single and mass);
  • change/rotation of IP from the provider;
  • Application of the generated configuration in Remnawave;
  • Change of firewall rules (single and mass);
  • Typed records in Remnawave (see above);
  • Changes in production routing;
  • A massive reboot of WARP.
  • Executing commands on the server.
Two actions are completely prohibited and cannot be enabled even in custom mode: changing the settings of sysctl and installing packets.

Dealing with a specific Flow incident

Running Axosun from the diagnostics preserves the original Flow and the context of the incident. Compare the report with its version and time: after a new application or recovery, the previous analysis can be historical. For a validated action, the result must include actual execution and subsequent validation. The report, the proposal and the task sent are different stages. Reconfirmation of an already processed action must not create a new launch. Flow Guard’s autonomy is set separately from Axosun’s.Assistance to diagnose does not include automatic routing.

Verification

1

Open the catalog.

Panel → Axosun → tab Action Catalog.
2

Convert the risk levels

Each action has a risk level and a sign that “requires confirmation.”
Catalog is displayed, and destructive actions have a mandatory confirmation.

Rollback

The directory is reference and read-only, there is nothing to roll back. To narrow down the set of actions available to the assistant, change the mode of behavior or lists of permitted / prohibited actions in the policy Axosun.