This section provides a simplified overview of the core process for creating, deploying, and bringing transfer nodes online. It includes only the essential first-time deployment steps. For detailed parameter descriptions, O&M operations, and prerequisites, see the full feature description later in this manual.
Step 1: Initial System Configuration
Go to the Dashboard page and complete the following three core initialization configurations to provide the basic environment for node deployment and task transfer:
1. License activation: Activate the system license and verify the node quota limit to ensure it meets business requirements.
2. Configure the Node WebSocket URL: Change the Node WebSocket URL in server information to a public IP address or domain name that can be accessed externally by the console. Do not use 127.0.0.1 or localhost. Transfer nodes rely on this address to reconnect to the console.
3. Restart the console service: After modifying core configurations such as the communication address, restart the service in the server information panel for the configuration to take effect.
|
Tip: If the Node WebSocket URL is 127.0.0.1, when you click Add Node on the Transfer Node page, the system automatically displays a pop-up guiding you to the Dashboard to complete the configuration. |
Step 2: Create and Deploy a Transfer Node
Go to Node → Transfer Node to create, deploy, and bring the node online.
2.1 Create a Transfer Node
1. Click Add Node on the page. A configuration drawer appears on the right.
2. Enter basic node information: node name and Public IP Address + port. Public IP Address is optional. If left blank, the system automatically detects the IP address. If entered manually, the specified IP address is used. The default port is 9994.
3. Click Save. A new record is generated in the node list, and its initial status is Unauthorized.
2.2 Deploy, Authorize, and Start the Node
1. In the corresponding row of the node list, click Deploy.
2. Select the Windows or Linux tab according to the target machine operating system.
3. Custom the node’s deployment directory (optional): If left blank, Windows deploys to %LOCALAPPDATA% by default, and Linux deploys to /opt by default.
4. Before You Deploy, Make sure the target host can reach this server, then run the generated command on Linux or Windows's PowerShell as Administrator or root.
5. After the command finishes, refresh the node list and confirm the node is online.
2.3 Confirm That the Node Is Online
After the script is executed successfully, refresh the node list. If the node status changes to Active, the node is online.
2.4 Open Node Ports
The node requires two inbound ports to be opened. The ports are configured for the node in section 2.1. By default, they are TCP 9994 and UDP 9994.
Step 3: Create a File Transfer Task
Go to Transfer → Transfer Task, click Add Task, and complete the configuration in the drawer on the right:
1. Basic information (required): Enter the task name.
2. Select the transfer direction (required).
￮ One-way transfer: source node → one or more target nodes.
￮ Two-way transfer: source node ↔ a single target node. Only folder transfer is supported.
3. Configure transfer paths (required): Select online nodes and configure source and target paths respectively. The source path supports multi-select for files/folders and cross-level multi-select. One-way transfer supports target path configuration for multiple nodes.
4. Set the task frequency (required).
5. Advanced configuration and email notifications (optional).
6. After configuration is complete, click OK to submit and create the task.
Step 4: Task Monitoring and Log Query
1. Task batch details: On the transfer task page, click Batch to view the overall batch progress, transfer speed, and remaining time. Click batch Detail to view transfer details for all nodes in the batch. Click node Files to view single-file transfer details.
2. Real-time progress monitoring: Go to Task Activity to view the dynamics of all transfer batches currently being executed in real time.
3. Historical record query: Go to Transfer Log to query all historical transfer tasks, batches, and node transfer records.