Exiting due to fatal error

Need help configuring your VPN? Just post here and you'll get that help.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
jameelb
OpenVpn Newbie
Posts: 3
Joined: Mon Nov 20, 2017 7:18 am

Exiting due to fatal error

Post by jameelb » Mon Nov 20, 2017 7:28 am

Hello guys,

I do have a problem setting OpenVPN in my vps.

I did create cert and key, but I do have problem with editing server.ovpn file

server
#################################################
# 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 1194

# 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 jarat.crt ((((((((((this is my crt name that I did)))))))))
key jarat.key # This file should be kept secret ((((((((((this is my key name that I did)))))))))

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh4096.pem 4096 (((((( I did replace 2048 to 4096 which I have ))))))
dh dh4096.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 213.32.x.xxx 255.255.255.255"
;push "route 213.32.x.xxx 255.255.255.255"

# 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 213.32.x.xxx 255.255.255.255
# 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 176.31.2xx.xxx 255.255.255.255
# 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 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# 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 jarat.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 Files\OpenVPN\log" 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




since I use vps here's when I write ipconfig in the CMD

  • hernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    Link-local IPv6 Address . . . . . : fexx::x919:xxxx:363f:66ac%11
    IPv4 Address. . . . . . . . . . . : 213.32.x.xxx
    Subnet Mask . . . . . . . . . . . : 255.255.255.255
    Default Gateway . . . . . . . . . : 176.31.2xx.xxx

Can you guys help me with it :(

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 5869
Joined: Fri Jun 03, 2016 1:17 pm

Re: Exiting due to fatal error

Post by TinCanTech » Mon Nov 20, 2017 12:44 pm

What is the "Fatal Error" ? (Post your log please)

See --log & --verb in The Manual v24x

jameelb
OpenVpn Newbie
Posts: 3
Joined: Mon Nov 20, 2017 7:18 am

Re: Exiting due to fatal error

Post by jameelb » Tue Nov 21, 2017 5:09 am

I think I do have errors with the # Configure server mode for ethernet bridging. Also with subnet mask and default gateway.

because I work in VPS so I don't have local IP like 192.168.0.1 I do have like this when I write command ipconfig
ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fexx::x919:xxxx:363f:66ac%11
IPv4 Address. . . . . . . . . . . : 213.32.x.xxx
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 176.31.2xx.xxx

and here's the error when I run server.ovpn

Mon Nov 20 21:08:20 2017 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO]
[LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Mon Nov 20 21:08:20 2017 Windows version 6.1 (Windows 7) 64bit
Mon Nov 20 21:08:20 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10

Mon Nov 20 21:08:21 2017 Diffie-Hellman initialized with 4096 bit key
Mon Nov 20 21:08:21 2017 Key file ('jarat.key') can be a maximum of 2048 bytes
Mon Nov 20 21:08:21 2017 Exiting due to fatal error
Press any key to continue...

jameelb
OpenVpn Newbie
Posts: 3
Joined: Mon Nov 20, 2017 7:18 am

Re: Exiting due to fatal error

Post by jameelb » Tue Nov 21, 2017 5:12 am

and I did fellow this video

https://www.youtube.com/watch?v=bpkRWvPWiOY

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 5869
Joined: Fri Jun 03, 2016 1:17 pm

Re: Exiting due to fatal error

Post by TinCanTech » Tue Nov 21, 2017 12:27 pm

jameelb wrote:
Tue Nov 21, 2017 5:09 am
Mon Nov 20 21:08:21 2017 Diffie-Hellman initialized with 4096 bit key
Mon Nov 20 21:08:21 2017 Key file ('jarat.key') can be a maximum of 2048 bytes
Mon Nov 20 21:08:21 2017 Exiting due to fatal error
Looks like you have created your PKI incorrectly ..



That video was Published on 17 Aug 2012 .. and only uses 1024bit key, which is now considered to be "broken" ..

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 2:58 pm

I am having the same issue and I followed the instructions from OpenVPN using the sample files included with the download from the site.
Here is the message from the command window:

Sat Dec 30 09:43:35 2017 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO][LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Sat Dec 30 09:43:35 2017 Windows version 6.1 (Windows 7) 64bit
Sat Dec 30 09:43:35 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10

Sat Dec 30 09:43:35 2017 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Sat Dec 30 09:43:35 2017 Diffie-Hellman initialized with 4096 bit key
Sat Dec 30 09:43:35 2017 Key file ('C:\OpenVPN\easy-rsa\keys\ca.key') can be a maximum of 2048 bytes
Sat Dec 30 09:43:35 2017 Exiting due to fatal error
Press any key to continue...

Any advice?

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 5869
Joined: Fri Jun 03, 2016 1:17 pm

Re: Exiting due to fatal error

Post by TinCanTech » Sat Dec 30, 2017 3:39 pm

Coohoodo wrote:
Sat Dec 30, 2017 2:58 pm
Key file ('C:\OpenVPN\easy-rsa\keys\ca.key') can be a maximum of 2048 bytes
You have also created the file incorrectly.

I suggest you simply try again and if it happens again document the steps you take exactly.

Guessing at possible causes (without suitable documentation):
  1. If you copied to file from one machine to another make sure the source and destination are identical

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 9:38 pm

Just deleting duplicate post
Last edited by Coohoodo on Sun Dec 31, 2017 2:29 pm, edited 1 time in total.

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 9:44 pm

Thank you for your prompt reply. :-)
I ran this several times with same errors. I have also uninstalled and reinstalled with no luck. I have not tried running openvpn on client computer because I haven't been able to get it working on the server.
I downloaded openvpn and installed it on the server (windows 7 pro)

I ran this commands at an elevated command prompt:
1.) cd C:\openVPN\easy-rsa
2.) init-config * then I edited the vars.bat file as seen below *
3.) vars
4.) clean-all
5.) build-ca * for common name I inputted "server" did get a warning that it couldn't open config file: /etc/ssl/openssl.cnf *
6.) build-key-server server *for common name I inputted "server" did get a warning that it couldn't open config file: /etc/ssl/openssl.cnf *
7.) build-key client1 * for common name I inputted "client1" *
8.) build-dh
9.) * copied ca.crt, ca.key, server.crt, server.key, and dh4096.pem from the keys folder in easy-rsa to C:\OpenVPN\config *
10.) * copy ca.crt, client1.crt, and client1.key from the server's keys folder to the client computer's OpenVPN config folder (C:\OpenVPN\config *
11.) * tried running the "server.ovpn" file in "C:\OpenVPN\config" on the server by right mouse on file and opening it in openVPN *
12.) * received an error in command window that opened up. *

Sat Dec 30 16:34:54 2017 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO][LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Sat Dec 30 16:34:54 2017 Windows version 6.1 (Windows 7) 64bit
Sat Dec 30 16:34:54 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10

Sat Dec 30 16:34:54 2017 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Sat Dec 30 16:34:54 2017 Diffie-Hellman initialized with 4096 bit key
Sat Dec 30 16:34:54 2017 Key file ('C:\OpenVPN\config\ca.key') can be a maximum of 2048 bytes
Sat Dec 30 16:34:54 2017 Exiting due to fatal error
Press any key to continue...



Server Config
# Here is my vars.bat file:

@echo off
rem Edit this variable to point to
rem the openssl.cnf file included
rem with easy-rsa.

rem Automatically set PATH to openssl.exe
rem FOR /F "tokens=2*" %%a IN ('REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\OpenVPN"') DO set "PATH=%PATH%;%%b\bin"

rem Alternatively define the PATH to openssl.exe manually
set "PATH=%PATH%;C:\OpenVPN\bin"

set HOME=C:\OpenVPN\easy-rsa
set KEY_CONFIG=openssl-1.0.0.cnf

rem Edit this variable to point to
rem your soon-to-be-created key
rem directory.
rem
rem WARNING: clean-all will do
rem a rm -rf on this directory
rem so make sure you define
rem it correctly!
set KEY_DIR=keys

rem Increase this if you
rem are paranoid. This will slow
rem down TLS negotiation performance
rem as well as the one-time DH parms
rem generation process.
set DH_KEY_SIZE=2048

rem Private key size
set KEY_SIZE=4096

rem These are the default values for fields
rem which will be placed in the certificate.
rem Change these to reflect your site.
rem Don't leave any of these parms blank.

set KEY_COUNTRY=xx
set KEY_PROVINCE=xx
set KEY_CITY=xx
set KEY_ORG=xx
set KEY_EMAIL=xx@xx.com
set KEY_CN=changeme
set KEY_NAME=xx
set KEY_OU=VPNers
set PKCS11_MODULE_PATH=changeme
set PKCS11_PIN=1234


Server Config
# HERE IS MY server.ovpn FILE


#################################################
# 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 1194

# 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 "C:\\OpenVPN\\config\\ca.crt"
cert "C:\\OpenVPN\\config\\server.crt"
key "C:\\OpenVPN\\config\\server.key" # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh "C:\\OpenVPN\\config\\dh4096.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 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# 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 ca.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 "C:\\OpenVPN\\config\\ca.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 "C:\\OpenVPN\\log\\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 Files\OpenVPN\log" 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

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 9:59 pm

deleting a duplicate post
Last edited by Coohoodo on Sun Dec 31, 2017 2:30 pm, edited 1 time in total.

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 10:01 pm

deleting a duplicate post
Last edited by Coohoodo on Sun Dec 31, 2017 2:30 pm, edited 1 time in total.

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 11:23 pm

deleting a duplicate post
Last edited by Coohoodo on Sun Dec 31, 2017 2:31 pm, edited 1 time in total.

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sat Dec 30, 2017 11:26 pm

deleting a duplicate post
Last edited by Coohoodo on Sun Dec 31, 2017 2:32 pm, edited 1 time in total.

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 5869
Joined: Fri Jun 03, 2016 1:17 pm

Re: Exiting due to fatal error

Post by TinCanTech » Sun Dec 31, 2017 1:12 pm

Coohoodo wrote:
Sat Dec 30, 2017 2:58 pm
I am having the same issue and I followed the instructions from OpenVPN using the sample files included with the download from the site.
Here is the message from the command window:

Sat Dec 30 09:43:35 2017 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO][LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Sat Dec 30 09:43:35 2017 Windows version 6.1 (Windows 7) 64bit
Sat Dec 30 09:43:35 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10

Sat Dec 30 09:43:35 2017 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Sat Dec 30 09:43:35 2017 Diffie-Hellman initialized with 4096 bit key
Sat Dec 30 09:43:35 2017 Key file ('C:\OpenVPN\easy-rsa\keys\ca.key') can be a maximum of 2048 bytes
Sat Dec 30 09:43:35 2017 Exiting due to fatal error
Press any key to continue...

Any advice?
Use the correct key file .. IE: Not ca.key

Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sun Dec 31, 2017 2:36 pm

Thank you, which one is the correct key file? :-)

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 5869
Joined: Fri Jun 03, 2016 1:17 pm

Re: Exiting due to fatal error

Post by TinCanTech » Sun Dec 31, 2017 2:42 pm


Coohoodo
OpenVpn Newbie
Posts: 9
Joined: Sat Dec 30, 2017 2:55 pm

Re: Exiting due to fatal error

Post by Coohoodo » Sun Dec 31, 2017 4:32 pm

Thanks,
Unfortuanlty that was the "script" I was following. But I'll try it again just in case I missed something the first few times. It wouldn't be the first time that happened. I'll keep you posted as to the outcome.
Thanks again and happy New Year. :-)

Post Reply