Frequently Asked Questions

Unable to Access the Interface After Master Deployment

Cause

The Linux firewall is blocking the corresponding network ports.

Solution

Check if the web service listening port is open on the machine’s firewall. Either disable the firewall or configure 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 to bypass the warning.

Task Progress Shows 0 After Worker Deployment and Task Start

Cause

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

Solution

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

Task Errors with “Client.Timeout or context cancellation” in the Exported Logs

Cause

The worker node failed to upload/download files due to network issues or a lack of response from the server, leading to a timeout error.

Solution

1. Check network connectivity between the endpoint and the worker machine using tools like ping or mtr.
2. If the network is stable, click the Retry button to reattempt the failed file transfer.
3. Alternatively, consider increasing the endpoint timeout duration.

Task Errors with Status Code 403 in the Exported Logs

Cause

The configured public and private keys for the endpoint do not have upload, download, or list permissions.

Solution

Update the permissions for the public and private keys to ensure they include upload, download, and list privileges.