Connect Artica to a VPN from the system console
Import an OpenVPN zip package from the system console and manage the VPN client connection.
An Artica server can join a remote OpenVPN server as a client.
The remote server gives you a VPN package.
It is a zip file that holds the connection profile (.ovpn) and its certificates.
You can import this package from the Web console.
You can also import it from the system console, on the server screen (tty1) or over SSH.
This page explains the system console method.
Use it when the Web console is not reachable yet, or when you only have a keyboard and a screen.
The system console shows the same connections as the Web console.
A connection imported in one place appears in the other.
Requirements
- An Artica server with the OpenVPN client feature.
- A system console that includes the VPN Client menu.
It comes with the hotfixes released after November 20, 2026. - A VPN package (zip) built for this server.
- The root account of the server.
Step 1: Get the VPN package
On the Artica OpenVPN server, open OpenVPN > Clients.
Click Download on the line of the client.
Your browser saves a zip file named after the client.
Copy this zip file to the Artica server that will connect.
For example, with scp:
scp office-paris.zip root@192.168.1.10:/root/
You can copy several packages into the same directory.
The console can import all of them in one pass.
Step 2: Open the VPN Client menu
Log in to the system console.
Choose System in the main menu.
Then choose VPN Client.

The first time, the list is empty.
Only Import and Back are shown.

Step 3: Import the package
Choose Import.
Type the full path of a zip file, or the path of a directory.
The default value is /root.

When you give a directory, the console checks every file in it.
Sub-directories are not scanned.
A file counts as a zip archive from its content, so a renamed package is still found.
Each zip is then checked.
It is a VPN package only if all these points are true:
- A
.ovpnfile sits at the root of the archive, not in a sub-directory. - This file holds a
remote <host> <port>line.
If the archive holds several .ovpn files, the first one in alphabetical order is used.
The console lists what it will import.
Each package is shown with its VPN server and port.
Archives that are not imported are listed below, with the reason.

Choose Yes.
Artica saves the connection, builds its configuration and starts the tunnel.
This takes a few seconds per package.

Step 4: Check the connection
Back in the VPN Client menu, each connection shows its state and its VPN server.
Wait a few seconds for the tunnel to come up.
The state then changes to Connected.

The possible states are listed below.
| State | Meaning |
|---|---|
| Connected | The tunnel is up. |
| CONNECTING, WAIT, AUTH | The tunnel is being set up. |
| Disconnected | The OpenVPN process runs but the tunnel does not answer. |
| Stopped | The tunnel is stopped. |
| Error | The configuration could not be built. Open Status to read the error. |
| Disabled | The connection is disabled. |
| Uninstalled | The connection is saved but not installed yet. |
Select the connection to open its menu.

Choose Status to see the details.
The screen shows the VPN server, the account, the network interface and the IP address of the tunnel.

Manage a connection
| Entry | Action |
|---|---|
| Status | Shows the state, the server, the account, the interface, the tunnel IP and the last error. |
| Start | Starts the tunnel. The connection must be enabled. |
| Stop | Stops the tunnel. |
| Disable | Stops the tunnel and keeps it stopped, even after a reboot. |
| Enable | Enables the connection again and starts it. |
| Edit | Changes the connection name, the username, the password and the debug level. |
| Events | Shows the last lines of the tunnel log. |
| Delete | Stops the tunnel and removes the connection. |
Edit a connection
Edit opens a form with four fields.
- Connection name: the name shown in the lists.
- Username and Password: the account sent to the VPN server, when the server asks for one.
- Debug level: from 2 (normal) to 127.
Raise it only to troubleshoot a connection.
After OK, Artica rebuilds the configuration of the connection.
An Artica support connection cannot be edited.
Its account looks like XXXX-XXXX-XXXX-XXXX.
Read the tunnel log
Choose Events.
Type a word to filter the lines, or leave the field empty to see all of them.
The screen shows the last lines that fit.

The Initialization Sequence Completed line means the tunnel is up.
Delete a connection
Choose Delete, then confirm.
Artica stops the tunnel, removes its watchdog and deletes its files.

The VPN package itself is never changed.
You can import it again later.
Troubleshooting
| Message | Cause and fix |
|---|---|
| No zip archive found in ... | The directory holds no zip file. Check the path. |
| ... is not a zip archive | The given file is not a zip file. |
| not a VPN template (no .ovpn profile at the root of the archive) | The archive holds no .ovpn file at its root.Download the package again from the OpenVPN server. |
| not a VPN template (... has no "remote host port" line) | The profile does not say which server to reach. Fix the profile on the OpenVPN server. |
| already imported | The same connection is already on this server. Nothing to do. |
| same connection as ... | Two packages of the directory hold the same profile. Only the first one is imported. |
| Artica REST service unreachable | The Artica REST service does not answer. Wait for the end of the boot, or restart the server. |
| State stays Disconnected | Open Events. Check that the VPN server is reachable from this server, on the port shown in the list. |