This is used for general discussion that is not necessarily server-related.
soja
This is my homepage
Posts: 2389 Joined: Fri May 18, 2012 3:20 pm
Post
by soja » Tue Dec 09, 2014 1:13 pm
Can you provide the specific error you are getting when trying to connect?
Have you confirmed the openvpn process is running, and listening on the correct port?
Not a NFO employee
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 1:20 pm
162.248.88.85:1164
Error 868 No se realizó la conexión remota porque no se resolvió el nombre del servidor de acceso remoto.
soja
This is my homepage
Posts: 2389 Joined: Fri May 18, 2012 3:20 pm
Post
by soja » Tue Dec 09, 2014 1:30 pm
This tool reports that the port you are using is closed:
http://www.yougetsignal.com/tools/open-ports/
Are you using windows or linux? Have you confirmed that the process is actually running, and not restricted by any firewall?
Not a NFO employee
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 1:52 pm
root@fastwolf:~# sudo ufw disable
Firewall stopped and disabled on system startup
root@fastwolf:~# restart openvpn
restart: Unknown job: openvpn
root@fastwolf:~# /etc/init.d/openvpn restart
* Stopping virtual private network daemon(s)... * Stopping VPN 'server' [ OK ]
* Starting virtual private network daemon(s)... * Autostarting VPN 'server' root@fastwolf:~# nc -zv 162.248.88.85
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
[-P proxy_username] [-p source_port] [-q seconds] [-s source]
[-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
[-x proxy_address[:port]] [destination] [port]
root@fastwolf:~# nc -zv 162.248.88.85 1164
nc: connect to 162.248.88.85 port 1164 (tcp) failed: Connection refused
root@fastwolf:~# ^C
soja
This is my homepage
Posts: 2389 Joined: Fri May 18, 2012 3:20 pm
Post
by soja » Tue Dec 09, 2014 1:56 pm
While OpenVPN is running, try running this command:
netstat -lp | grep 1164
It should return the PID of openvpn to confirm that the process is running and listning on the correct port.
If not, check any logs that openVPN creates for potential errors.
Not a NFO employee
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 1:57 pm
server' root@fastwolf:~# netstat -lp | grep 1164
-bash: syntax error near unexpected token `('
and where I find the logs
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 1:59 pm
root@fastwolf:~# netstat -lp | grep 1164
root@fastwolf:~# nc -zv 162.248.88.85 1164
nc: connect to 162.248.88.85 port 1164 (tcp) failed: Connection refused
root@fastwolf:~#
soja
This is my homepage
Posts: 2389 Joined: Fri May 18, 2012 3:20 pm
Post
by soja » Tue Dec 09, 2014 2:01 pm
hm are you sure you are typing the netstat command in correctly? This is what I am shown when doing it on my linux VDS for the port my COD4 server is on:
Not a NFO employee
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 2:01 pm
Yes im sure the command is correct
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 2:05 pm
root@fastwolf:~#: command not found
root@fastwolf:~# netstat -lp | grep 1164
root@fastwolf:~# netstat -lp | grep 28960
root@fastwolf:~# -
Port 1164 is closed on 162.248.88.85.
soja
This is my homepage
Posts: 2389 Joined: Fri May 18, 2012 3:20 pm
Post
by soja » Tue Dec 09, 2014 2:10 pm
Check for any logs OpenVPN generates(I am not sure where they would be, or if you have to enable them through configs, I have never used it), and look for errors.
Confirm the process is running using:
ps aux | grep vpn (this should work if the process name is openvpn).
If you don't see a resulting line here, the process isn't running.
Not a NFO employee
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 2:13 pm
soja wrote: Check for any logs OpenVPN generates(I am not sure where they would be, or if you have to enable them through configs, I have never used it), and look for errors.
Confirm the process is running using:
ps aux | grep vpn (this should work if the process name is openvpn).
If you don't see a resulting line here, the process isn't running.
root@fastwolf:~# ps aux | grep vpn
root 10459 0.2 0.3 24208 6188 ? Ss 09:50 0:02 /usr/sbin/openvpn --writepid /run/openvpn/server.pid --daemon ovpn-server --cd /etc/openvpn --config /etc/openvpn/server.conf --script-security 2
root 10758 0.0 0.0 11744 916 pts/4 S+ 10:11 0:00 grep --color=auto vpn
root@fastwolf:~#
I can't find the logs
ErikIvaN
A semi-regular
Posts: 16 Joined: Tue Dec 09, 2014 10:17 am
Contact:
Post
by ErikIvaN » Tue Dec 09, 2014 2:18 pm