Curious on tips for rectifying the following errors from my journalctl -xb output, [code]Feb 17 23:48:13 server ovpn-server2[1375]: Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/server2.conf Feb 17 23:48:13 server systemd[1]: Failed to start OpenVPN connection to server2.[/code] I believe I caused this back when I was attempting (unsuccessfully) to stack my CAs. My actual VPN is up and active, but it's just named "server" and not "server2." I'm still a novice, as I'm thinking this is a very simple fix but all of my attempts so far haven't changed anything.

Thanks Pippen. Ended up fixing by running [code]sudo systemctl disable openvpn@server2.service [/code] Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here).

[quote=vellofrell post_id=89587 time=1582236159 user_id=48569] Thanks Pippen. Ended up fixing by running [code]sudo systemctl disable openvpn@server2.service [/code] Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here). [/quote]systemctl [u]disable[/u] openvpn@.. does [b]not[/b] sound like you fixed anything .. :geek:

[quote=TinCanTech post_id=89590 time=1582238505 user_id=37053] [quote=vellofrell post_id=89587 time=1582236159 user_id=48569] Thanks Pippen. Ended up fixing by running [code]sudo systemctl disable openvpn@server2.service [/code] Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here). [/quote]systemctl [u]disable[/u] openvpn@.. does [b]not[/b] sound like you fixed anything .. :geek: [/quote] I recall throwing shots in the dark trying to make a stacked VPN certificates and possibly multiple OpenVPN instances just a few days before - not knowing what I was doing. After running that command, the errors pertaining to this stopped appearing in my 'journalctl' output. None of my clients' existing connectivity to the server were affected.

Troubleshooting OpenVPN errors in journalctl -xb

vellofrell

Curious on tips for rectifying the following errors from my journalctl -xb output,

Feb 17 23:48:13 server ovpn-server2[1375]: Options error: In [CMD-LINE]:1: Error opening configuration file: /etc/openvpn/server2.conf
Feb 17 23:48:13 server systemd[1]: Failed to start OpenVPN connection to server2.

I believe I caused this back when I was attempting (unsuccessfully) to stack my CAs.

My actual VPN is up and active, but it's just named "server" and not "server2."

I'm still a novice, as I'm thinking this is a very simple fix but all of my attempts so far haven't changed anything.

Pippin

Please read:
https://community.openvpn.net/openvpn/wiki/HOWTO

vellofrell

Which one of the 25 in the table of contents?

Pippin

Wrong link, my bad...

We need more info, especially when you run two servers on the same machine, please see:
https://forums.openvpn.net/viewtopic.php?t=22603

vellofrell

Thanks Pippen. Ended up fixing by running

sudo systemctl disable openvpn@server2.service

Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here).

TinCanTech

vellofrell wrote Thanks Pippen. Ended up fixing by running

sudo systemctl disable openvpn@server2.service

Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here).

systemctl disable openvpn@.. does not sound like you fixed anything .. :geek:

vellofrell

TinCanTech wrote
vellofrell wrote Thanks Pippen. Ended up fixing by running
sudo systemctl disable openvpn@server2.service
Should've been simple enough from the start but I must have been typing the command wrong. (Still novice here).
systemctl disable openvpn@.. does not sound like you fixed anything .. :geek:

I recall throwing shots in the dark trying to make a stacked VPN certificates and possibly multiple OpenVPN instances just a few days before - not knowing what I was doing. After running that command, the errors pertaining to this stopped appearing in my 'journalctl' output. None of my clients' existing connectivity to the server were affected.