Содержание
- Не подключаеться!
- Posts: 5
- 1 Topic by lucky 05.05.2017 18:40:05
- Topic: Не подключаеться!
- 2 Reply by lucky 05.05.2017 18:42:06
- Re: Не подключаеться!
- 3 Reply by Rino 05.05.2017 19:51:22
- Re: Не подключаеться!
- 4 Reply by lucky 05.05.2017 22:33:13
- Re: Не подключаеться!
- OpenVPN Support Forum
- OpenVPN GUI — Management Interface Error
- OpenVPN GUI — Management Interface Error
- GUI Tray Icon dissapears after laptop sleep/unsleep action Windows 10 #276
- Comments
- OpenVPN Support Forum
- Fedora clients can’t start openvpn on boot
- Fedora clients can’t start openvpn on boot
- OpenVPN Support Forum
- Fedora clients can’t start openvpn on boot
- Fedora clients can’t start openvpn on boot
Не подключаеться!
You must login or register to post a reply
Posts: 5
1 Topic by lucky 05.05.2017 18:40:05
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Topic: Не подключаеться!
Здравствуйте, у меня выбивает ошибка когда нажимаю на подключиться.
Что в начале пишет:
Fri May 05 17:34:36 2017 OpenVPN GUI>OpenVPN terminated with exit code 1. See the log file for detail
Потом вылазит окно и в самом окне пишет:
Не удалось подключиться к Russia_freeopenvpn_udp.
Использовали сначало Нидерланды. Потом и с ними выбивало тоже самое, изменили в конфиге файл.
Дальше выбивает, жду ответа.
P.S. Очищал так-же КэшDNS.
Спасибо заранее!
2 Reply by lucky 05.05.2017 18:42:06
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Re: Не подключаеться!
Здравствуйте, у меня выбивает ошибка когда нажимаю на подключиться.
Что в начале пишет:
Fri May 05 17:34:36 2017 OpenVPN GUI>OpenVPN terminated with exit code 1. See the log file for detail
Потом вылазит окно и в самом окне пишет:
Не удалось подключиться к Russia_freeopenvpn_udp.
Использовали сначало Нидерланды. Потом и с ними выбивало тоже самое, изменили в конфиге файл на Россия.
Дальше выбивает, жду ответа.
P.S. Очищал так-же КэшDNS.
Спасибо заранее!
3 Reply by Rino 05.05.2017 19:51:22
- Rino
- Moderator
- Offline
- Registered: 20.05.2016
- Posts: 517
Re: Не подключаеться!
Здравствуйте!
В состоянии подключения у вас есть запись
Покопайтесь в лог-файле, там должен быть ответ.
4 Reply by lucky 05.05.2017 22:33:13
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Re: Не подключаеться!
Здравствуйте!
В состоянии подключения у вас есть запись
Покопайтесь в лог-файле, там должен быть ответ.
Источник
OpenVPN Support Forum
Community Support Forum
OpenVPN GUI — Management Interface Error
OpenVPN GUI — Management Interface Error
Post by nothereagain81 » Fri Aug 09, 2019 5:13 pm
I couldn’t find any reference to this particular issue online, so more than likely it’s something simple I’m overlooking; however I haven’t found what the issue is as of yet and so I come here for help.
I currently have a few laptops I set up for people using OpenVPN GUI in Windows. When connecting from the GUI, a user will get an error messaging saying it couldn’t connect to the management interface and to check the logs. This happens intermittently.
The logs only have «Enter management password: «
The only way around this (other than rebooting) is to restart the Interactive Service.
I recall reading somewhere on openvpn.net where this issue is caused by the connection profile being started already and it’s commonly caused by the OpenVPN Service and OpenVPN Legacy Service being used at the same time; however, I observed that only openvpn-gui.exe was running when this happened. The OpenVPN Service and OpenVPN Legacy Service (both set to manual) were not running.
The version of the OpenVPN Client being used is 2.4.6. I tried 2.4.7 to no avail.
If I check the event logs I see an Error entry under Application logs for openvpnserv but it only says:
I’m at a loss as to what causes this. Right now I’m attempting a workaround with a scheduled task to restart the Interactive Service triggered by a custom event filter with the aforementioned event log entry.
I’ve witnessed this happening on Windows 7, 8.1, and 10.
Источник
GUI Tray Icon dissapears after laptop sleep/unsleep action Windows 10 #276
I found that almost every time when I close lid of my laptop, I don’t find GUI tray icon anymore to connect/disconnect any connections.
After that I should close OpenVPN daemons with taskmanager, start Openvpn GUI again, and reconnect all connections I need. Do you have any ideas how to solve it?
The text was updated successfully, but these errors were encountered:
Have you checked the config of «visibility options for icons in the notification area» ? Does the GUI program actually die?
yes right now visibility set to always show, and issue still exists. So when I open laptop after sleep, it disappear in 2-3 seconds, and I don’t see it in processes, but connections still running fine.
But I start it again as admin or as user, I can’t connect to my connections any more and they marked as not active
and seems I have this log in windows event viewer
The error you get is expected if the connection is active and you are trying to start another instance possibly using the same log file and same tap adapter. Instead, you will have to manually kill any running openvpn process(es) before attempting a restart. Just as you posted on Aug 5.
But the real question is why the GUI is abnormally terminating on suspend. I have not seen it before but can try to reproduce given more details: Windows version, GUI and openvpn versions, and verb = 4 log file of the openvpn process that remains active after the resume. Does a clean reinstall help? — by clean I mean uninistall and clear the HKCU/Software/OpenVPN-GUI registry key. Note that will also delete any saved encrypted password blobs.
Ok I will try reinstall, enable verb 4 logs and will back to you.
As for now, I’am starting GUI autoconnect with Task Scheduler at system logon C:Program FilesOpenVPNbinopenvpn-gui.exe —connect dev.ovpn
Maybe it’s the reasons of these crashes? Maybe there is some other Official way to autoconnect with gui on system startup?
By «at system logon» if you mean on bootup before any user has logged in, that will definitely not work. With proper flags (interactive, run only when user is logged on etc.) it should work, though I haven’t tried.
Anyway try first by adding the GUI to the startup menu (see settings) to automatically start the GUI on logon and then manually start the connection. If that works without issues you know where the problem lies. For auto connect making a shortcut with —connect dev.ovpn as the argument and adding that to launch on logon may be better than using task scheduler.
I used this one
but will try all your suggestions, and return back to you
This may not fix your problem, but do not run the GUI with «highest privileges» — just run with the usual limited privileges. That is how GUI shipped with 2.4 is supposed to be used.
Problem solved after moving startup to shell:startup shortcut. So it seems was some Task Scheduler issue. Thank you for your help!
Источник
OpenVPN Support Forum
Community Support Forum
Fedora clients can’t start openvpn on boot
Fedora clients can’t start openvpn on boot
Post by Chrismur91 » Wed Oct 17, 2018 3:12 pm
I have a couple of new machines with Fedora 28 installed that I’m trying to configure to connect to our VPN server. I can get the clients to connect successfully by manually entering openvpn —config client.conf, but I can’t get the connection to start on boot.
I’ve spent some time troubleshooting and researching, but I’ve come up empty on a solution.
Some quick notes to eliminate certain troubleshooting:
— The client.conf file is located in /etc/openvpn
— The client.conf file permissions are set to 400
— The client certificates are located in /etc/openvpn/client
After some research I found that I may need to specify the client file when starting the service, so I tried this:
systemctl start openvpn-client@client
and I receive the following:
Job for openvpn-client@client.service failed because the control process exited with error code.
See «systemctl status openvpn-client@client.service» and «journalctl -xe» for details.
systemctl status output:
â openvpn-client@client.service — OpenVPN tunnel for client
Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-10-17 12:34:36 NDT; 11s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/w . n24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 25332 ExecStart=/usr/sbin/openvpn —suppress-timestamps —nobind —config client.conf (code=exited, status=1/FAILURE)
Main PID: 25332 (code=exited, status=1/FAILURE)
Oct 17 12:34:36 ava-silvaco systemd[1]: Starting OpenVPN tunnel for client.
Oct 17 12:34:36 ava-silvaco openvpn[25332]: Options error: In [CMD-LINE]:1: Error opening configuration file: client.conf
Oct 17 12:34:36 ava-silvaco openvpn[25332]: Use —help for more information.
Oct 17 12:34:36 ava-silvaco systemd[1]: openvpn-client@client.service: Main process exited, code=exited, status=1/FAILURE
Oct 17 12:34:36 ava-silvaco systemd[1]: openvpn-client@client.service: Failed with result ‘exit-code’.
Oct 17 12:34:36 ava-silvaco systemd[1]: Failed to start OpenVPN tunnel for client.
Journalctl -xe output:
— Subject: Unit openvpn-client@client.service has failed
— Defined-By: systemd
— Support: https://lists.freedesktop.org/mailman/l . temd-devel
—
— Unit openvpn-client@client.service has failed.
—
— The result is RESULT.
Oct 17 12:34:36 ava-silvaco audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=’unit=openvpn-client@client comm=»systemd» exe=»/usr/lib/systemd/systemd» hostname=? addr=? terminal=? res=failed’
Any help or suggestions anyone can offer with this would be great!
Thanks.
Источник
OpenVPN Support Forum
Community Support Forum
Fedora clients can’t start openvpn on boot
Fedora clients can’t start openvpn on boot
Post by Chrismur91 » Wed Oct 17, 2018 3:12 pm
I have a couple of new machines with Fedora 28 installed that I’m trying to configure to connect to our VPN server. I can get the clients to connect successfully by manually entering openvpn —config client.conf, but I can’t get the connection to start on boot.
I’ve spent some time troubleshooting and researching, but I’ve come up empty on a solution.
Some quick notes to eliminate certain troubleshooting:
— The client.conf file is located in /etc/openvpn
— The client.conf file permissions are set to 400
— The client certificates are located in /etc/openvpn/client
After some research I found that I may need to specify the client file when starting the service, so I tried this:
systemctl start openvpn-client@client
and I receive the following:
Job for openvpn-client@client.service failed because the control process exited with error code.
See «systemctl status openvpn-client@client.service» and «journalctl -xe» for details.
systemctl status output:
â openvpn-client@client.service — OpenVPN tunnel for client
Loaded: loaded (/usr/lib/systemd/system/openvpn-client@.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-10-17 12:34:36 NDT; 11s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/w . n24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 25332 ExecStart=/usr/sbin/openvpn —suppress-timestamps —nobind —config client.conf (code=exited, status=1/FAILURE)
Main PID: 25332 (code=exited, status=1/FAILURE)
Oct 17 12:34:36 ava-silvaco systemd[1]: Starting OpenVPN tunnel for client.
Oct 17 12:34:36 ava-silvaco openvpn[25332]: Options error: In [CMD-LINE]:1: Error opening configuration file: client.conf
Oct 17 12:34:36 ava-silvaco openvpn[25332]: Use —help for more information.
Oct 17 12:34:36 ava-silvaco systemd[1]: openvpn-client@client.service: Main process exited, code=exited, status=1/FAILURE
Oct 17 12:34:36 ava-silvaco systemd[1]: openvpn-client@client.service: Failed with result ‘exit-code’.
Oct 17 12:34:36 ava-silvaco systemd[1]: Failed to start OpenVPN tunnel for client.
Journalctl -xe output:
— Subject: Unit openvpn-client@client.service has failed
— Defined-By: systemd
— Support: https://lists.freedesktop.org/mailman/l . temd-devel
—
— Unit openvpn-client@client.service has failed.
—
— The result is RESULT.
Oct 17 12:34:36 ava-silvaco audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=’unit=openvpn-client@client comm=»systemd» exe=»/usr/lib/systemd/systemd» hostname=? addr=? terminal=? res=failed’
Any help or suggestions anyone can offer with this would be great!
Thanks.
Источник
Skip to forum content
Форум проекта FreeOpenVPN.Org
Бесплатный VPN-доступ без ограничений
You are not logged in. Please login or register.
Active topics Unanswered topics
Не подключаеться!
Pages 1
You must login or register to post a reply
1 05.05.2017 18:40:05
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Topic: Не подключаеться!
Здравствуйте, у меня выбивает ошибка когда нажимаю на подключиться.
Что в начале пишет:
Fri May 05 17:34:36 2017 OpenVPN GUI>OpenVPN terminated with exit code 1. See the log file for detail
Потом вылазит окно и в самом окне пишет:
Не удалось подключиться к Russia_freeopenvpn_udp.
Использовали сначало Нидерланды. Потом и с ними выбивало тоже самое, изменили в конфиге файл.
Дальше выбивает, жду ответа.
P.S. Очищал так-же КэшDNS.
Спасибо заранее!
2 Reply by lucky 05.05.2017 18:42:06
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Re: Не подключаеться!
lucky wrote:
Здравствуйте, у меня выбивает ошибка когда нажимаю на подключиться.
Что в начале пишет:
Fri May 05 17:34:36 2017 OpenVPN GUI>OpenVPN terminated with exit code 1. See the log file for detailПотом вылазит окно и в самом окне пишет:
Не удалось подключиться к Russia_freeopenvpn_udp.Использовали сначало Нидерланды. Потом и с ними выбивало тоже самое, изменили в конфиге файл на Россия.
Дальше выбивает, жду ответа.P.S. Очищал так-же КэшDNS.
Спасибо заранее!
3 Reply by Rino 05.05.2017 19:51:22
- Rino
- Moderator
- Offline
- Registered: 20.05.2016
- Posts: 518
Re: Не подключаеться!
Здравствуйте!
В состоянии подключения у вас есть запись
See the log file for detail
Покопайтесь в лог-файле, там должен быть ответ.
4 Reply by lucky 05.05.2017 22:33:13
- lucky
- Новичок
- Offline
- Registered: 05.05.2017
- Posts: 3
Re: Не подключаеться!
Rino wrote:
Здравствуйте!
В состоянии подключения у вас есть записьSee the log file for detail
Покопайтесь в лог-файле, там должен быть ответ.
Добрый вечер.
Пишет:
Fri May 05 21:23:57 2017
DEPRECATED OPTION: —max-routes option ignored.The number of routes is unlimited as of version 2.4. This option will be removed in a future version, please remove it from your configuration.
Fri May 05 21:23:57 2017 OpenVPN 2.4.1 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Mar 22 2017
Fri May 05 21:23:57 2017 Windows version 6.1 (Windows 7) 32bit
Fri May 05 21:23:57 2017 library versions: OpenSSL 1.0.2k 26 Jan 2017, LZO 2.09
Enter Management Password:
Fri May 05 21:23:57 2017 MANAGEMENT: Socket bind failed on local address [AF_INET]127.0.0.1:25340: Address already in use (WSAEADDRINUSE)
Fri May 05 21:23:57 2017 Exiting due to fatal error
5 Reply by Rino 08.05.2017 21:08:19
- Rino
- Moderator
- Offline
- Registered: 20.05.2016
- Posts: 518
Re: Не подключаеться!
Попробуйте закомментировать в файле конфигурации строку
Posts: 5
Pages 1
You must login or register to post a reply
Добрый день! Помогите пожалуйста, у меня не подключается vpn клиент к серверу.
Вот конфиги
на сервере:
Код
port 443 proto udp dev tun dev-node "VPN Lumpics" dh C:\OpenVPN\ssl\dh2048.pem ca C:\OpenVPN\ssl\ca.crt cert C:\OpenVPN\ssl\Lumpics.crt key C:\OpenVPN\ssl\Lumpics.key server 172.16.10.0 255.255.255.0 max-clients 32 keepalive 10 120 client-to-client comp-lzo persist-key persist-tun cipher DES-CBC status C:\OpenVPN\log\status.log log C:\OpenVPN\log\openvpn.log verb 4 mute 20
у клиента:
Код
client resolv-retry infinite nobind remote 192.168.0.15 443 proto udp dev tun comp-lzo ca C:\Program Files\OpenVPN\Config\ca.crt cert C:\Program Files\OpenVPN\config\vpn-client.crt key C:\Program Files\OpenVPN\config\vpn-client.key float cipher DES-CBC keepalive 10 120 persist-key persist-tun verb 3 remote-cert-tls server
Ругается при подключении: Sun Dec 19 15:25:32 2021 OpenVPN GUI> OpenVPN terminated with exit code 1. See the log file for details
В логе у клиента: Options error: Unrecognized option or missing or extra parameter(s) in config.ovpn:8: ca (2.4.7)
Use —help for more information.
Я понимаю, что что-то с 8-ой строчкой не так…. Но что? Там путь прописан…
На всякий случай лог на сервере:
Код
Sun Dec 19 09:17:35 2021 us=490109 Current Parameter Settings: Sun Dec 19 09:17:35 2021 us=490109 config = 'C:OpenVPNconfigserver.ovpn' Sun Dec 19 09:17:35 2021 us=490109 mode = 1 Sun Dec 19 09:17:35 2021 us=490109 show_ciphers = DISABLED Sun Dec 19 09:17:35 2021 us=490109 show_digests = DISABLED Sun Dec 19 09:17:35 2021 us=490109 show_engines = DISABLED Sun Dec 19 09:17:35 2021 us=490109 genkey = DISABLED Sun Dec 19 09:17:35 2021 us=490109 key_pass_file = '[UNDEF]' Sun Dec 19 09:17:35 2021 us=490109 show_tls_ciphers = DISABLED Sun Dec 19 09:17:35 2021 us=490109 connect_retry_max = 0 Sun Dec 19 09:17:35 2021 us=490109 Connection profiles [0]: Sun Dec 19 09:17:35 2021 us=490109 proto = udp Sun Dec 19 09:17:35 2021 us=490109 local = '[UNDEF]' Sun Dec 19 09:17:35 2021 us=490109 local_port = '443' Sun Dec 19 09:17:35 2021 us=490109 remote = '[UNDEF]' Sun Dec 19 09:17:35 2021 us=490109 remote_port = '443' Sun Dec 19 09:17:35 2021 us=490109 remote_float = DISABLED Sun Dec 19 09:17:35 2021 us=490109 bind_defined = DISABLED Sun Dec 19 09:17:35 2021 us=490109 bind_local = ENABLED Sun Dec 19 09:17:35 2021 us=490109 bind_ipv6_only = DISABLED Sun Dec 19 09:17:35 2021 us=490109 NOTE: --mute triggered... Sun Dec 19 09:17:35 2021 us=490109 278 variation(s) on previous 20 message(s) suppressed by --mute Sun Dec 19 09:17:35 2021 us=490109 OpenVPN 2.4.7 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Feb 20 2019 Sun Dec 19 09:17:35 2021 us=490109 Windows version 6.2 (Windows 8 or greater) 64bit Sun Dec 19 09:17:35 2021 us=490109 library versions: OpenSSL 1.1.0j 20 Nov 2018, LZO 2.10 Sun Dec 19 09:17:35 2021 us=490109 Diffie-Hellman initialized with 2048 bit key Sun Dec 19 09:17:35 2021 us=505734 TLS-Auth MTU parms [ L:1622 D:1212 EF:38 EB:0 ET:0 EL:3 ] Sun Dec 19 09:17:35 2021 us=505734 interactive service msg_channel=0 Sun Dec 19 09:17:35 2021 us=505734 ROUTE_GATEWAY 10.0.0.1/255.255.255.0 I=14 HWADDR=00:22:48:9d:63:34 Sun Dec 19 09:17:35 2021 us=505734 open_tun Sun Dec 19 09:17:35 2021 us=505734 TAP-WIN32 device [VPN Lumpics] opened: \.Global{A1DD0C0D-2717-4F1C-9F82-8C1465E9696F}.tap Sun Dec 19 09:17:35 2021 us=505734 TAP-Windows Driver Version 9.22 Sun Dec 19 09:17:35 2021 us=505734 TAP-Windows MTU=1500 Sun Dec 19 09:17:35 2021 us=505734 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.16.10.1/255.255.255.252 on interface {A1DD0C0D-2717-4F1C-9F82-8C1465E9696F} [DHCP-serv: 172.16.10.2, lease-time: 31536000] Sun Dec 19 09:17:35 2021 us=505734 Sleeping for 10 seconds... Sun Dec 19 09:17:45 2021 us=521661 Successful ARP Flush on interface [8] {A1DD0C0D-2717-4F1C-9F82-8C1465E9696F} Sun Dec 19 09:17:45 2021 us=521661 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Sun Dec 19 09:17:45 2021 us=521661 C:Windowssystem32route.exe ADD 172.16.10.0 MASK 255.255.255.0 172.16.10.2 Sun Dec 19 09:17:45 2021 us=521661 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4 Sun Dec 19 09:17:45 2021 us=521661 Route addition via IPAPI succeeded [adaptive] Sun Dec 19 09:17:45 2021 us=521661 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ] Sun Dec 19 09:17:45 2021 us=521661 Could not determine IPv4/IPv6 protocol. Using AF_INET6 Sun Dec 19 09:17:45 2021 us=521661 Socket Buffers: R=[65536->65536] S=[65536->65536] Sun Dec 19 09:17:45 2021 us=521661 setsockopt(IPV6_V6ONLY=0) Sun Dec 19 09:17:45 2021 us=521661 UDPv6 link local (bound): [AF_INET6][undef]:443 Sun Dec 19 09:17:45 2021 us=521661 UDPv6 link remote: [AF_UNSPEC] Sun Dec 19 09:17:45 2021 us=521661 MULTI: multi_init called, r=256 v=256 Sun Dec 19 09:17:45 2021 us=521661 IFCONFIG POOL: base=172.16.10.4 size=62, ipv6=0 Sun Dec 19 09:17:45 2021 us=521661 Initialization Sequence Completed
Короче, уже извелся(((
Я еще и не программист…. А так ото….) Просто хочу сам поднять впн ….)
__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь
Recently I noticed that one of my OpenVPN servers stopped working. It was just after the update on the Ubuntu 16.04.4 LTS. What I found was that the service failed on start:
user@host:~$ sudo systemctl start openvpn@server.service Job for openvpn@server.service failed because the control process exited with error code. See "systemctl status openvpn@server.service" and "journalctl -xe" for details.
The status message was also not helpful:
user@host:~$ sudo systemctl status openvpn@server.service ● openvpn@server.service - OpenVPN connection to server Loaded: loaded (/lib/systemd/system/openvpn@.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2018-12-13 14:52:59 CET; 7s ago Dec 13 14:52:59 vz15951 systemd[1]: Starting OpenVPN connection to server… Dec 13 14:52:59 vz15951 ovpn-server[1854]: OpenVPN 2.3.18 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Sep 26 2017 Dec 13 14:52:59 vz15951 ovpn-server[1854]: library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Dec 13 14:52:59 vz15951 ovpn-server[1854]: daemon() failed or unsupported: Resource temporarily unavailable (errno=11) Dec 13 14:52:59 vz15951 ovpn-server[1854]: Exiting due to fatal error Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Control process exited, code=exited status=1 Dec 13 14:52:59 vz15951 systemd[1]: Failed to start OpenVPN connection to server. Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Unit entered failed state. Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Failed with result 'exit-code'.
Anything in the logs?
Unfortunately, logs also don’t look good:
Dec 13 14:52:59 vz15951 systemd[1]: Starting OpenVPN connection to server... Dec 13 14:52:59 vz15951 ovpn-server[1854]: OpenVPN 2.3.18 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Sep 26 2017 Dec 13 14:52:59 vz15951 ovpn-server[1854]: library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Dec 13 14:52:59 vz15951 ovpn-server[1854]: daemon() failed or unsupported: Resource temporarily unavailable (errno=11) Dec 13 14:52:59 vz15951 ovpn-server[1854]: Exiting due to fatal error Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Control process exited, code=exited status=1 Dec 13 14:52:59 vz15951 systemd[1]: Failed to start OpenVPN connection to server. Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Unit entered failed state. Dec 13 14:52:59 vz15951 systemd[1]: openvpn@server.service: Failed with result 'exit-code'.
There is no clear evidence what failed. I remember that my provider was changing something in the virtual machine configurations recently (the company was bought by the bigger one) and this led me to the simple but brilliant solution…
Service configuration update
There is a known issue with OpenVPN on LXD containers. It has the same symptoms. So I tried to adjust the service configuration file:
user@host:~$ sudo vi /lib/systemd/system/openvpn@.service
I found the line with the LimitNPROC=10 and commented it out:
#LimitNPROC=10
Once updated, I had to perform two more steps – first was the reload of systemctl daemon:
user@host:~$ sudo systemctl daemon-reload
Next, I turned the OpenVPN service on again:
user@host:~$ sudo systemctl start openvpn@server.service
No error message, this looks much better. Let’s take a look at the status:
user@host:~$ sudo systemctl status openvpn@server.service ● openvpn@server.service - OpenVPN connection to server Loaded: loaded (/lib/systemd/system/openvpn@.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-12-13 15:15:17 CET; 39s ago Docs: man:openvpn(8) https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage https://community.openvpn.net/openvpn/wiki/HOWTO Process: 3497 ExecStart=/usr/sbin/openvpn --daemon ovpn-%i --status /run/openvpn/%i.status 10 --cd /etc/openvpn --script-security 2 --config /etc/openvpn/%i.conf --writepid /run/ Main PID: 3498 (openvpn) CGroup: /system.slice/system-openvpn.slice/openvpn@server.service └─3498 /usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn --script-security 2 --config /etc/openvpn/server.conf --writepid / Dec 13 15:15:17 vz15951 ovpn-server[3498]: succeeded -> ifconfig_pool_set() Dec 13 15:15:17 vz15951 ovpn-server[3498]: Initialization Sequence Completed
Wonderful. It is working now. Such a simple solution but it requires a little bit of luck to find it 🙂