error when trying to start server.conf

moxito99

Hi everybody. Please help me with next problem.
when i try to make this command "openvpn --config /etc/openvpn/server.conf" then comes a message

RTNETLINK answers: File exists
Thu Jul  2 09:06:19 2020 ERROR: Linux route add command failed: external program exited with error status: 2
Thu Jul  2 09:06:19 2020 Could not determine IPv4/IPv6 protocol. Using AF_INET
Thu Jul  2 09:06:19 2020 Socket Buffers: R=[87380->87380] S=[16384->16384]
Thu Jul  2 09:06:19 2020 TCP/UDP: Socket bind failed on local address [AF_INET]xx.xx.xxx.xxx:443: Address already in use (errno=98)
Thu Jul  2 09:06:19 2020 Exiting due to fatal error
Thu Jul  2 09:06:19 2020 Closing TUN/TAP interface
Thu Jul  2 09:06:19 2020 /sbin/ip addr del dev tun1 local 10.8.0.1 peer 10.8.0.2

netstat -lnp | grep 443
tcp        0      0 xx.xx.xxx.xxx:443       0.0.0.0:*               LISTEN      468/openvpn

i'm novice in that, so please help me. yesterday i did the same thing and everything works fine

TinCanTech

moxito99 wrote RTNETLINK answers: File exists
Thu Jul 2 09:06:19 2020 ERROR: Linux route add command failed: external program exited with error status: 2
...
Thu Jul 2 09:06:19 2020 TCP/UDP: Socket bind failed on local address [AF_INET]xx.xx.xxx.xxx:443: Address already in use (errno=98)
Thu Jul 2 09:06:19 2020 Exiting due to fatal error

You already opened the same file.

moxito99

TinCanTech wrote
moxito99 wrote RTNETLINK answers: File exists
Thu Jul 2 09:06:19 2020 ERROR: Linux route add command failed: external program exited with error status: 2
...
Thu Jul 2 09:06:19 2020 TCP/UDP: Socket bind failed on local address [AF_INET]xx.xx.xxx.xxx:443: Address already in use (errno=98)
Thu Jul 2 09:06:19 2020 Exiting due to fatal error
You already opened the same file.

so what should i do? cause when i'm trying to start openvpn it won't.
may i kill this process? and start it again?

TinCanTech

Try rebooting your server ..

moxito99

TinCanTech wrote Try rebooting your server ..

did it. everything is the same

moxito99

TinCanTech wrote Try rebooting your server ..

looks like this problem was solved by killing process on port443, then reboot, then

systemctl -f enable openvpn@server.service

systemctl start openvpn@server.service

service openvpn@server status
● openvpn@server.service - OpenVPN connection to server
   Loaded: loaded (/lib/systemd/system/openvpn@.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-07-02 10:20:09 EDT; 2min 58s ago
     Docs: man:openvpn(8)
           https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
           https://community.openvpn.net/openvpn/wiki/HOWTO
 Main PID: 443 (openvpn)
   Status: "Initialization Sequence Completed"
    Tasks: 1 (limit: 1150)
   Memory: 3.3M
   CGroup: /system.slice/system-openvpn.slice/openvpn@server.service
           └─443 /usr/sbin/openvpn --daemon ovpn-server --status /run/openvpn/server.status 10 --cd /etc/openvpn

Jul 02 10:20:09 tempest ovpn-server[443]: Listening for incoming TCP connection on [AF_INET]xx.xx.xxx.xxx:443
Jul 02 10:20:09 tempest ovpn-server[443]: TCPv4_SERVER link local (bound): [AF_INET]xx.xx.xxx.xxx:443
Jul 02 10:20:09 tempest ovpn-server[443]: TCPv4_SERVER link remote: [AF_UNSPEC]
Jul 02 10:20:09 tempest ovpn-server[443]: GID set to nogroup
Jul 02 10:20:09 tempest ovpn-server[443]: UID set to nobody
Jul 02 10:20:09 tempest ovpn-server[443]: MULTI: multi_init called, r=256 v=256
Jul 02 10:20:09 tempest ovpn-server[443]: IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
Jul 02 10:20:09 tempest ovpn-server[443]: IFCONFIG POOL LIST
Jul 02 10:20:09 tempest ovpn-server[443]: MULTI: TCP INIT maxclients=1024 maxevents=1028
Jul 02 10:20:09 tempest ovpn-server[443]: Initialization Sequence Completed

is everything looks fine????

Pippin

Your formatting looks off.....
😉

TinCanTech

moxito99 wrote

TinCanTech wrote Try rebooting your server ..

looks like this problem was solved by killing process on port443, then reboot, then

systemctl -f enable openvpn@server.service

So now you have killed whatever it was which was running on 443 and you don't know what it was ... :shock:

moxito99

TinCanTech wrote
moxito99 wrote
TinCanTech wrote Try rebooting your server ..
looks like this problem was solved by killing process on port443, then reboot, then
systemctl -f enable openvpn@server.service
So now you have killed whatever it was which was running on 443 and you don't know what it was ... :shock:

it was openvpn which was already started
netstat -lnp | grep 443
tcp 0 0 xx.xx.xxx.xxx:443 0.0.0.0:* LISTEN 468/openvpn

moxito99

TinCanTech wrote
moxito99 wrote
TinCanTech wrote Try rebooting your server ..
looks like this problem was solved by killing process on port443, then reboot, then
systemctl -f enable openvpn@server.service
So now you have killed whatever it was which was running on 443 and you don't know what it was ... :shock:

now i have this message in log file "Bad encapsulated packet length from peer (5635), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both"
how can i fix it?

moxito99

Last problem was solved. I've made a mistake while using systemctl command to start openvpn.service. I copied systemctl commands from tutorial and now i noticed a difference between the last words.The steps i've made was
put this into server.conf:
mssfix 1432
sndbuf 1048576
rcvbuf 1048576
txqueuelen 2048
tcp-queue-limit 1024
tcp-nodelay
because log file has this message "Bad encapsulated packet length from peer (5635), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both"
than disable and stop openvpn.service
after that reboot
and start and enable openvpn.service
and it works fine for now
i also made a comments to
#mssfix 1432
#sndbuf 1048576
#rcvbuf 1048576
#txqueuelen 2048
#tcp-queue-limit 1024
#tcp-nodelay
and it still works just fine