Updating RPort
RPort is under active development. Keep your installation up-to-date.
Update the RPort clients
It's recommended to run your clients with the recent version of rport. We try to always keep server and client compatible, regardless of the version. Basic connectivity and the usage of tunnels should always be possible with clients running an older version than the server. An exception to that rule is the licence change from 0.9.12 to 1.0.0. Clients >= 1.0 will not connect to an open-source server <= 0.9.13.
A fast and easy update of the rport clients can be done through the pairing service. If you have scripting with root privileges enabled, you can trigger a client update through the rport server.
💡It's safe to execute the update while being connected via SSH or RDP through an RPort tunnel. On Windows and Linux, the rport client is restarted delayed and from a decoupled background process. You will be disconnected, but the client reconnects, and you can create a new tunnel after the update.
On Linux
set -e
if [ $(id -u) -ne 0 ];then
echo "Needs to run from the root account. Activate sudo!"
false
fi
if which at; then
true
else
echo "System is missing the at command."
echo "Try 'dnf -y install at; pidof atd||systemctl start atd' on RHEL"
echo "Try 'DEBIAN_FRONTEND=noninteractive apt-get -y --no-install-recommends install at' on Debian/Ubuntu"
false
fi
curl -sf https://pairing.openrport.io/update > /tmp/rport-update.sh
at now << EOF
sleep 5
sh /tmp/rport-update.sh >/tmp/rport-update.log 2>&1
rm /tmp/rport-update.sh
EOF
echo "The rport client update will shortly start in the background."
echo "If update fails, inspect /tmp/rport-update.log"
The Linux update script accepts parameters as follows:
On Windows
The Windows update script accepts parameters as follows:
Update the RPort server
We keep all major and minor versions of the rportd and the frontend compatible. Do not run different major and minor versions of frontend and backend.
The rport server has database migrations built-in. But some tables are excluded from auto-migration. An update consists basically of replacing the old rportd binary by a newer version. If you need to change the database manually, we will provide SQL snippets.
For a fast, secure and convenient update, use the update script as follows, read the security advice below first:
👉 After the update, use SHIFT-Reload on your browser to purge the old frontend from the cache.
If you already entered your licence details to the rportd.conf file, you must not export them to the environment before starting the update.
Last updated