Client is not connecting
If a client does not connect, likely a firewall causes the problem. Let's check this quickly from the command line.

Check the connection

Grab the address and port of your RPort sever.

Open the configuration file /etc/rport/rport.conf or C:\Program Files\rport\rport.conf with a text editor and look for the line that contains your RPort sever address. Or grab it directly from the console using grep "server =" /etc/rport/rport.conf on Linux or find "server =" "C:\Program Files\rport\rport.conf" on Windows.
The server settings consist of the FQDN or IP Address and the port, divided by colon. Optionally there is a protocol prefix http://.
Example: server = "v0e0vj4l5j1m.users.rport.io:80" The server address is v0e0vj4l5j1m.users.rport.io and the port is 80.
On Linux, execute echo > /dev/tcp/<SERVER>/<PPORT> && echo "All good"||echo "Server not reachable".
echo > /dev/tcp/v0e0vj4l5j1m.users.rport.io/80 && echo "All good"||echo "Server not reachable"
-bash: connect: No route to host
-bash: /dev/tcp/v0e0vj4l5j1m.users.rport.io/80: No route to host
Server not reachable
On Windows, use the PowerShell and execute Test-NetConnection -ComputerName <SERVER> -Port <PORT>.
If the above check fails, a firewall is blocking the outgoing connections.

Observe the logs

If the client is not connecting, you should look at the logs.
From a Windows PowerShell execute Get-Content "C:\Program Files\rport\rport.log"| Select-Object -Last 100.
From a Linux console execute tail -n 100 /var/log/rport/rport.log.
You might get a hint why the client is not connecting.
Last modified 2mo ago
Export as PDF
Copy link