Operations Panel Command Line Usage
After installation, the system creates the daxpay management command (usually at /usr/local/bin/daxpay). Use the command line when the panel is unreachable, for remote automation, or when you want to inspect service state directly.
You can also invoke the /opt/daxpay/dax-pay-installer binary directly; the examples below use daxpay throughout. Managing the panel usually requires root — non-root users should prefix commands with sudo.
Prefer the interactive UI
For day-to-day terminal management, simply run daxpay (no arguments) to enter the interactive management UI and follow the menus — no need to memorize commands; see Terminal UI (TUI).
Command Layering
daxpay help lists only the daily commands (panel lifecycle and overview inspection) together with layered guidance. Emergency and account commands are not surfaced in help, but they work as usual for scripted execution; the "Access Recovery / Account Recovery" groups of the interactive UI are their guided entry (the complete list lives on the "Command Help" page of the interactive UI, which covers more than daxpay help).
Basic Commands
| Command | Purpose |
|---|---|
daxpay start | Start the panel in the background |
daxpay stop | Stop the running panel |
daxpay restart | Restart the panel, keeping the original startup parameters |
daxpay status | Show the panel run status, including PID, port, auth, and secure entrance |
daxpay logs [-f] | View runtime logs; -f follows the log, --installer switches to the installer application log |
daxpay version | Show the panel version number |
daxpay info | Show the initial admin credentials generated on first start |
daxpay help | Show help (daily command list with layered guidance) |
daxpay upgrade --force | Force an overwrite upgrade of the panel: re-downloads and overwrites the current panel, data preserved |
Overview Inspection
daxpay overviewOne command for the full system picture: system info and panel version / system load / service status (product-matrix view, uninstalled services visible in grey) / Docker engine usage / port conflict detection / effective-configuration status of the three stacks. No login required, independent of the panel process, same implementation as the web overview.
Secure Entrance Commands
The secure entrance places the login page and the panel APIs under a random or custom path. Access without the entrance path returns 404, which reduces exposure to internet scans and password brute force.
Command Syntax
daxpay entrance show
daxpay entrance enable
daxpay entrance rotate [--yes|-y]
daxpay entrance set <path> [--yes|-y]
daxpay entrance disable [--yes|-y]Command Reference
| Command | Purpose and behavior |
|---|---|
daxpay entrance show | Show the current secure entrance status, entrance path, and full access URL; omitting the sub-command is equivalent to show |
daxpay entrance enable | Ensure the secure entrance is on; generates a random one when off, keeps the existing one when on; no confirmation needed |
daxpay entrance rotate | Replace the entrance with a new random one; the old URL stops working immediately; asks for confirmation by default |
daxpay entrance set <path> | Set a custom entrance; the path must be 8-64 characters of letters, digits, underscore, or hyphen; asks for confirmation by default |
daxpay entrance disable | Turn the secure entrance off; the login page and all APIs become directly exposed; asks for confirmation by default |
Once an entrance change is written to disk, the running web panel picks it up when its cache refreshes — a service restart is usually unnecessary. After rotate or set succeeds, the old entrance stops working immediately; update your bookmarks or reverse proxy configuration in time.
Confirmation Rules
rotate,set, anddisableprompt for confirmation by default; onlyyoryesproceeds.- In cron, CI, scripts, and other non-interactive environments, a missing confirmation means the operation is refused — the entrance is never changed by accident.
- For automated execution, skip the confirmation with
--yesor-y, for example:
sudo daxpay entrance rotate --yes
sudo daxpay entrance set my-panel-entry-2026 -y
sudo daxpay entrance disable --yes--yes only skips the confirmation; it does not skip custom path validation, nor does it change the secure entrance action of the web API.
Common Scenarios
Forgot the entrance URL? Run this on the server:
sudo daxpay entrance showEnable the secure entrance for an existing deployment for the first time:
sudo daxpay entrance enableSuspect the entrance has leaked? Rotate to a new random one:
sudo daxpay entrance rotateRotate the entrance from an automation script:
sudo daxpay entrance rotate --yesDisabling the entrance is only suitable for local debugging or a clearly controlled intranet:
sudo daxpay entrance disableAccess and Account Emergency Commands
The commands below belong to the emergency domain and are not surfaced in daxpay help (they work as usual). When the panel won't open or you can't log in, the "Access Recovery / Account Recovery" groups of the interactive UI are the guided entry — see Terminal UI (TUI); for the background of each defense line see Panel Security.
Command Syntax
daxpay domain show | enable <domain> | disable
daxpay ipallow show | set <entries> | disable
daxpay unlock
daxpay reset-password [--username <name>] [--password <password>]
daxpay twofactor status | disable
daxpay uninstall [--purge]Command Reference
| Command | Purpose and behavior |
|---|---|
daxpay domain show | Show the domain access restriction status, the bound domain, and the full access URL; the default sub-command is equivalent to show |
daxpay domain enable <domain> | Binds and enables the domain restriction (probes domain reachability first); disable restores direct IP access |
daxpay ipallow show | Show the currently effective authorized IP allowlist entries |
daxpay ipallow set <entries> | Set the allowlist — multiple IPs or CIDR ranges comma-separated; disable restores access from all sources |
daxpay unlock | Release the login lockout by resetting the consecutive-failure counter |
daxpay reset-password | Reset the panel account password and revoke all logged-in sessions; supports --username / --password for non-interactive execution |
daxpay twofactor status | Show the two-step verification status and the remaining recovery codes; disable is the fallback for when the authenticator is lost and the recovery codes are exhausted |
daxpay uninstall | Uninstall the panel program, keeping business data and configuration by default; --purge also deletes the working directory and business data — a dangerous operation |
Change commands such as domain enable, ipallow set, twofactor disable, and uninstall prompt for confirmation by default; scripted execution likewise uses --yes / -y to skip it.
Global Options
| Option | Purpose |
|---|---|
--workdir <dir> | Panel working directory, default /opt/daxpay |
--yes / -y | Skip confirmations for dangerous operations; mainly for scripted entrance changes and uninstallation |
--username <name> | With reset-password: the panel account |
--password <password> | With reset-password: the new password |
For example, view the entrance of a panel installed in a custom directory like this:
sudo daxpay entrance show --workdir /srv/daxpay