Openvpn terminated with exit code 1 как устранить ошибку

Hello!

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:

The description for Event ID ‘0’ in Source ‘openvpnserv’ cannot be found. The local computer may not have the necessary registry information or
message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:’openvpn
serv error: ‘, ‘0x20000000
OpenVPN exited with error: exit code = 1

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.

Thoughts?

Last edited by nothereagain81 on Fri Aug 09, 2019 8:12 pm, edited 2 times in total.

Не подключаеться!

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.

Источник

Добрый день! Помогите пожалуйста, у меня не подключается 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

Короче, уже извелся(((
Я еще и не программист…. А так ото….) Просто хочу сам поднять впн ….)

Зарегистрирован: 22.12.2011
Пользователь #: 136,166
Сообщения: 291

Источник

Ошибки VPN

Иногда случаются проблемы с VPN подключением или VPN не работает. На данной странице вы можете найти описание возникающей ошибки впн и самостоятельно исправить ее.

Ошибки OpenVPN

Если вы не знаете как узнать ошибку, возникшую в ходе подключения, нажмите на следующую ссылку:

Ниже представлен список возможных ошибок и методы их устранения. Нажмите на ошибку, чтобы узнать как ее устранить. Названия ошибок соответствуют записям в окне лога.

Как узнать какая OpenVPN ошибка возникла?

Программа OpenVPN имеет лог подключения. При подключении к OpenVPN серверу программа записывает данные подключения. Эта информация никуда не передается и остается на вашем компьютере, чтобы вы могли понять из-за чего возникла ошибка впн. Чтобы вызвать окно лога, нажмите дважды левой кнопкой мыши на иконку OpenVPN в системном трее.

Когда соединение прошло успешно, и вы подключены к VPN серверу, то окно лога должно выглядеть так:

Не могу выбрать «Connect» при нажатии на иконку в системном трее

В списке есть только «Proxy Settings», «About» и «Exit», но нет пункта «Connect».

Это означает, что вы не скачали и/или не скопировали конфигурационный файл «client.ovpn» в «C:/Program Files/OpenVPN/config». Откройте еще раз Инструкцию по настройке OpenVPN соединения для вашей ОС и проверьте все шаги установки и настройки.

Connect to IP:Port failed, will try again in 5 seconds; No Route to Host

Данная ошибка означает, что у вас нет подключения к Интернету, либо его блокирует ваш Firewall или Антивирус.

Проверьте активно ли ваше Интернет подключение, отключите Firewall, Антивирус и подключитесь еще раз.

Cannot load certificate file client.crt

Данная ошибка связана с отсутствием сертификационных файлов в папке «C:Program FilesOpenVPNconfig».

В процессе установки было необходимо скачать архив с сертификатами и распаковать его в папку с программой. Откройте еще раз Инструкцию по настройке OpenVPN соединения для вашей ОС и проверьте все шаги установки и настройки.

All TAP-Win32 adapters on this system are currently in use

Эта впн ошибка связана с некорректной работой Windows и программы OpenVPN. Также эта OpenVPN ошибка может возникнуть вследствие отключения Интернета без отключения сначала OpenVPN соединения. Всегда отключайте сначала OpenVPN соединение и только затем Интернет.

Для устранения ошибки, зайдите в «Пуск -> Сетевые подключения». Найдите «Подключение по локальной сети. TAP-Win32 Adapter» и правой кнопкой мышки щелкните на ярлыке. Выберите «Отключить».

Затем, таким же образом, «Включите» данное подключение. После выполнения данных действий проблемы с VPN подключением должны исчезнуть.

ERROR: Windows route add command failed: returned error code 1

Данная ошибка связана с ограничением прав в Windows Vista, Seven.

Для устранения ошибки, необходимо выйти из OpenVPN GUI. Правой кнопкой мышки нажать на иконку OpenVPN GUI на рабочем столе и выбрать пункт меню «Свойства»

На вкладке «Совместимость» поставьте галочку «Выполнять эту программу от имени администратора».

Теперь запустите OpenVPN GUI еще раз и подключитесь к VPN серверу.

Initialization Sequence Completed With Errors

Данная ошибка связана с неправильной работой службы DHCP из-за антивирусов или фаерволов.

Ошибка наблюдалась постоянно у фаервола Outpost Firewall версии 2009 и ранее, наблюдается также у антивируса Касперского. Ниже представлено решение для антивируса Касперского. Сам алгоритм ничем не отличается от решения проблемы для других антивирусов и фаерволов.

Для устранения ошибки, необходимо зайти в «Пуск -> Панель Управления -> Сетевые подключения» и зайти в «Свойства» виртуального адаптера «TAP-Win 32 Adapter». На вкладке «Общие» в списке отключить Kaspersky Anti-Virus NDIS Filter и затем нажать «ОК».

Теперь подключитесь к VPN и подключение должно пройти успешно.

Источник