Service openvpn exited with error exit code 1

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

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.

Источник

I’m getting an error when trying to start an OpenVPN service on CentOS7

I keep having to reinstall the whole system and configure the VPN from scratch. Each time something new is causing problems. Previously the same error was countered with commenting ;explicit-exit-notify 1, but now it’s not enough and I’m out of ideas.

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 result of journalctl -xe is:

Dec 06 10:28:41 window polkitd[657]: Registered Authentication Agent for unix-process:32081:324221 (system bus name :1.74 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Dec 06 10:28:41 window systemd[1]: Starting OpenVPN Robust And Highly Flexible Tunneling Application On server...
-- Subject: Unit openvpn@server.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit openvpn@server.service has begun starting up.
Dec 06 10:28:41 window systemd[1]: openvpn@server.service: main process exited, code=exited, status=1/FAILURE
Dec 06 10:28:41 window systemd[1]: Failed to start OpenVPN Robust And Highly Flexible Tunneling Application On server.
-- Subject: Unit openvpn@server.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit openvpn@server.service has failed.
--
-- The result is failed.
Dec 06 10:28:41 window systemd[1]: Unit openvpn@server.service entered failed state.
Dec 06 10:28:41 window systemd[1]: openvpn@server.service failed.
Dec 06 10:28:41 window polkitd[657]: Unregistered Authentication Agent for unix-process:32081:324221 (system bus name :1.74, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

My OpenVPN server configuration is:

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\Program Files\OpenVPN\config\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################



# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 24353

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth ta.key 0 # This file is secret

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nobody

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "Program FilesOpenVPNlog" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
log-append  openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
;explicit-exit-notify 1