---
title: Upgrading an Existing RPAM Installation (3.8.x → 3.9.0)
slug: kron-pam-installation-guides-v3/upgrading-an-existing-rpam-installation-38x-390
createdAt: 2026-11-20T10:30:28.342Z
---

If the RPAM Portal was installed for an earlier Kron PAM version (e.g., with the 3.8.x configure.sh scripts), it does not need to be reinstalled with the RPAM MTC Installer. After the Kron PAM Server is upgraded to 3.9.0, only the following two files must be updated on the **RPAM Portal**:

·         The RPAM Portal jar file: **/pam/remote-access-portal/rap-0.0.1-SNAPSHOT.jar**

·         The nginx configuration file: **/etc/nginx/nginx.conf**

No change is needed on the RPAM Connector, the On-PAM configuration, the WireGuard configuration, or application.properties.

1.    Copy the **rpam-mtc.tar.gz** package to the RPAM Portal and extract it under /pam (see [Preparing the Installation](https://docs.krontech.com/kron-pam-installation-guides-v3/preparing-the-installation)). The installer does not need to be started. The files used in the following steps are:

·         Jar file: **/pam/rpam-mtc/files/cloud/jars/rap-3.9.0.jar**

·         nginx template (No failover): **/pam/rpam-mtc/files/cloud/nginx/nginx3.9.0.conf**

·         nginx template (Failover): **/pam/rpam-mtc/files/cloud/nginx/nginx-failover3.9.0.conf**

2.    Take a backup of the current jar file and nginx configuration, and note the WireGuard IP address(es) of the RPAM Connector(s) in the **upstream backend** section of the current nginx.conf:

| **Linux CLI** | **\[root\@portal\~]#** cp /pam/remote-access-portal/rap-0.0.1-SNAPSHOT.jar /pam/remote-access-portal/rap-0.0.1-SNAPSHOT.jar.bak<br />**\[root\@portal\~]#** cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.bak<br />**\[root\@portal\~]#** grep -A3 "upstream backend" /etc/nginx/nginx.conf |
| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

3.    Stop the RPAM Portal service and replace the jar file:

| **Linux CLI** | **\[root\@portal\~]#** systemctl stop pam-rap.service<br />**\[root\@portal\~]#** cp -f /pam/rpam-mtc/files/cloud/jars/rap-3.9.0.jar /pam/remote-access-portal/rap-0.0.1-SNAPSHOT.jar<br />**\[root\@portal\~]#** chmod 755 /pam/remote-access-portal/rap-0.0.1-SNAPSHOT.jar |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

4.    Replace nginx.conf with the 3.9.0 template and fill in the placeholders with the WireGuard IP addresses noted in step 2:

**No failover** (single RPAM Connector):

| **Linux CLI** | **\[root\@portal\~]#** cp -f /pam/rpam-mtc/files/cloud/nginx/nginx3.9.0.conf /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverIPHolder/\{RPAM Connector's WireGuard IP}/g" /etc/nginx/nginx.conf |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@portal\~]#** sed -i "s/serverIPHolder/10.0.0.2/g" /etc/nginx/nginx.conf                                                                                                                                 |

**Failover** (primary + backup RPAM Connector):

| **Linux CLI** | **\[root\@portal\~]#** cp -f /pam/rpam-mtc/files/cloud/nginx/nginx-failover3.9.0.conf /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverPrimaryIPHolder/\{Primary RPAM Connector's WireGuard IP}/g" /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverBackupIPHolder/\{Backup RPAM Connector's WireGuard IP}/g" /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverPortalIPHolder/\{RPAM Portal's WireGuard IP}/g" /etc/nginx/nginx.conf |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Example**   | **\[root\@portal\~]#** sed -i "s/serverPrimaryIPHolder/10.0.0.2/g" /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverBackupIPHolder/10.0.0.3/g" /etc/nginx/nginx.conf<br />**\[root\@portal\~]#** sed -i "s/serverPortalIPHolder/10.0.0.1/g" /etc/nginx/nginx.conf                                                                                                                                                                                                      |

:::hint{type="info"}
If the previous nginx.conf contains customer-specific changes (other than the certificate files under /etc/nginx/certs, which are not affected), apply them to the new file as well. Make sure that no "Holder" placeholder remains in the file: **grep -n Holder /etc/nginx/nginx.conf** should return nothing.
:::

5.    Test the nginx configuration and restart the services:

| **Linux CLI** | **\[root\@portal\~]#** nginx -t<br />**\[root\@portal\~]#** systemctl restart nginx.service<br />**\[root\@portal\~]#** systemctl start pam-rap.service<br />**\[root\@portal\~]#** sss |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

**Check:** **nginx -t** should report that the syntax is ok, and **sss** should show pam-rap, nginx, and WireGuard services as active. The new nginx.conf should contain the **location /rpam-ui/static** block (see [Troubleshooting](https://docs.krontech.com/kron-pam-installation-guides-v3/troubleshooting)). Open an RPAM invitation link and verify that the passcode screen of the RPAM Portal is shown.
