To start an update, please first login to the Administator Portal and ensure that there are no active VPN connections. While performing an update is not harmful to the application data, it's always a good idea to give connected users ample time to save their work, as the update process will disconnect and terminate all active VPN connections immediately.

2. Log in to the application host and open a terminal

The update process requires terminal access on the application host. Please log in to the application host as a user with permissions to execute docker and docker compose commands, and with access to the application stack (docker ps -a).

Important: Please ensure that you are not connected to the same VPN Access server that you will be updating, as your connection will be lost and you won't be able to complete the update process!

Updating to the Latest Version

First, validate that your docker-compose.yml file is using the latest tag for the Konnect™ server application image:

version: "3"
services:
  web:
    image: ghcr.io/kuyio/konnect:latest
  ...

You can update Konnect™ server to the latest released version by running the following commands on your Konnect™ server host, from the same directory that contains the docker-compose.yml file.

docker compose pull
docker compose stop web
docker compose rm web
docker compose up -d

Updating to a Specific Version

If you have pinned a particular version in your docker-compose.yml file (image tag other than latest), you will first need to edit the docker-compose.yml file and update the desired docker image tag to the version to which you would like to upgrade to.

version: "3"
services:
  web:
    image: ghcr.io/kuyio/konnect:1.1.2
  ...

You can update Konnect™ server to the desired version by running the following commands on your Konnect™ server host, from the same directory that contains the docker-compose.yml file.

docker compose pull
docker compose stop web
docker compose rm web
docker compose up -d