Arch Linux

arti946

Member

Registered: Yesterday

Posts: 2

Start OpenVPN on boot error

I recently set up a VPN using OpenVPN and want it to run on system boot. The Wiki tells me to enable the service using

systemctl enable openvpn-client@client.service

While this did enable the service, the VPN doesn't start on boot. Attempting to manually start the service using systemctl doesn't work either, it just gives an error opening the configuration file:

Jun 12 00:06:54 archlinux systemd[1]: Starting OpenVPN tunnel for proton...
Jun 12 00:06:54 archlinux openvpn[4379]: Options error: In [CMD-LINE]:1: Error opening configuration file: proton.conf
Jun 12 00:06:54 archlinux openvpn[4379]: Use --help for more information.
Jun 12 00:06:54 archlinux systemd[1]: openvpn-client@proton.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 00:06:54 archlinux systemd[1]: openvpn-client@proton.service: Failed with result 'exit-code'.
Jun 12 00:06:54 archlinux systemd[1]: Failed to start OpenVPN tunnel for proton. 

The only way I've been able to start the VPN is with

sudo openvpn /etc/openvpn/client/config.ovpn

which works nicely but doesn't help me start on boot.

Any ideas as to what's happening here and how I could fix it?

Last edited by arti946 (Yesterday 06:22:02)

Caloway

Member

Registered: 2025-06-04

Posts: 2

Re: Start OpenVPN on boot error

It seems like a configuration path error

 Jun 12 00:06:54 archlinux openvpn[4379]: Options error: In [CMD-LINE]:1: Error opening configuration file: proton.conf 

Are you sure where the proton.conf file is located?

ls /etc/openvpn/client/

arti946

Member

Registered: Yesterday

Posts: 2

Re: Start OpenVPN on boot error

Yes I am certain that the .ovpn configuration file is in the proper place, and the VPN will start no problem if I do it manually with the openvpn command. When I double-checked just now I did notice that I needed root permissions to even view /etc/openvpn/client, and I had to run ls with sudo in order to view the files I had in there. Is it possible that OpenVPN doesn't have the permissions it needs to read the config file?