Frequently Asked Questions

Unable to see the interface in the browser after deploying the master node

Cause

The Linux firewall has blocked the corresponding network port.

Solution

Check if the web service listening port in the machine’s firewall is open. Either disable the firewall or set an IP whitelist for the port.

Cause

US3SYNC uses a self-signed certificate, which is not recognized by browsers like Chrome.

Solution

On the Chrome error page, type thisisunsafe.

After deploying the worker node, the number of ongoing migration tasks remains 0 after starting the task

Cause

The worker node failed to start, usually due to network unavailability between the worker node and the master node.

Solution

Check network connectivity using ping. Verify that the worker node’s IP address is configured correctly and ensure network connectivity between the master and worker nodes.

Task error: “Client.Timeout or context cancellation” in the exported task log

Cause

The worker node attempted to upload/download files, but the request timed out due to network issues or unresponsive servers, leading to this error.

Solution

Check network connectivity between the endpoint and the worker machine using tools like ping or mtr. If the network is normal, click the retry button to retransmit failed files, or consider increasing the endpoint timeout period.

Error status code 403 in the exported task log

Cause

The public-private key configured on the endpoint does not have permissions for uploading, downloading, or listing.

Solution

Update the permissions of the public-private key to ensure it has upload, download, and list permissions.