CloudConnexa: Run OpenVPN3 Client as a Service for Connector and Replace the Deprecated openvpn3-autoload

Overview

If you use OpenVPN 3 Linux with the openvpn3-autoload feature, you may see warnings similar to the following after upgrading to OpenVPN 3 Linux v27 or later.

## WARNING: openvpn3-autoload HAS BEEN DEPRECATED since OpenVPN 3 Linux v20 
## WARNING: MIGRATE TO THE openvpn3-session@.service systemd unit NOW 
## WARNING: SEE man openvpn3-systemd FOR DETAILS

The openvpn3-autoload feature was deprecated in OpenVPN Linux v20 and is scheduled for removal in a future release.

Although the feature continues to function in current releases, configurations that depend on it may stop working after upgrading to a future version. To avoid service disruptions, migrate to the openvpn3-session@.service systemd unit.

For additional information, refer to the OpenVPN 3 Linux v27 release notes.

Note: Perform this procedure during a maintenance window or outside business hours, as the VPN connection is interrupted during migration.

Procedure

Follow these steps to migrate from the openvpn3-autoload feature to the openvpn3-session@.service systemd unit.

1. Disable and stop the openvpn3-autoload feature:

   sudo systemctl disable --now openvpn3-autoload.service

2. Import the new configuration:

   sudo openvpn3 config-import --config /etc/openvpn3/autoload/connector.conf --name CloudConnexa --persistent

3. Disconnect the session started by openvpn3-autoload:

   openvpn3 session-manage --disconnect --config connector.conf

4. Restart the OpenVPN network configuration service:

   sudo killall -INT openvpn3-service-netcfg

5. Enable and start the new systemd service:

   sudo systemctl enable --now openvpn3-session@CloudConnexa.service

6. Verify that the VPN session is connected.
7. Reboot the system and confirm that the VPN session reconnects automatically after startup.

8. Confirm that the deprecated service is disabled:

   systemctl status openvpn3-autoload

9. Confirm that the new service is enabled:

   systemctl status openvpn3-session@CloudConnexa.service

Troubleshooting

Disconnect command returns "no sessions started"

If the following error appears:

openvpn3/session-manage: ** ERROR ** No sessions started with the configuration profile name was found

The VPN session is using a different configuration profile name.

1. List the active sessions:

   openvpn3 sessions-list

2. Identify the configuration name associated with the active session.

3. Run the disconnect command using that configuration name:

   openvpn3 session-manage --disconnect --config "<CONFIG_NAME>"

openvpn3 config-manage --config CloudConnexa --log-level 6 
openvpn3-admin log-service --log-level 6 
openvpn3-admin netcfg-service --config-set log-level 6

If you have additional questions, submit a support ticket.