1.Local deployment
Raysync server needs to be configured with the machine's firewall to allow the following ports. If the server is deployed in a NAT gateway with only an intranet IP, the following ports also need to be mapped on the router NAT.
| Direction | Protocol/Port | Port Service Description |
|---|---|---|
| Inbound | TCP/8090 | User portal http service |
| Inbound | TCP/8091 | User portal https service |
| Inbound | TCP/9090 | Admin portal http service |
| Inbound | TCP/9091 | Admin portal https service |
| Inbound | TCP/2480 | Client Web Direct Service |
| Inbound | TCP/2481 | Client Web Encryption Direct Connection Service |
| Inbound | TCP/2442 | TCP Transfer Unencrypted Services |
| Inbound | TCP/2443 | TCP Transfer TLS Encryption Service |
| Inbound | TCP/32001 | Node Management Service |
| Inbound | UDP/32001 | UDP Accelerated Transfer Service |
| Inbound | TCP/2482 | HTTP download |
| Inbound | TCP/2483 | HTTPS download |
| Inbound | TCP/3443 | TCP forwarding server monitor port for Peer-to-Peer transfer |
| Inbound | UDP/3478 | Raysync STUN server port is used for network detection and hole drilling between point-to-point |
| Inbound | UDP/32003 | Peer-to-Peer transfer service |
At least the port must be open:
http access: TCP: 8090, 9090, 2480, 2442; UDP: 32001
https access: TCP: 8091, 9091, 2481, 2443; UDP: 32001
2.Cloud deployment
If the Raysync service is deployed on public clouds such as AWS and Azure, in addition to opening access to the above ports in the security group where the server is located, it is also necessary to open the above-mentioned ports in the security group where the server is located. Common cloud vendor security group configurations: