Skip to content
Having some troubles with auto disconnecting
Got a problem with Viscosity or need help? Ask here!
Hello everyone,
Been using viscosity for a while now and started bumping into some issues in the last few hours after being away from home for two weeks and not using it. I have noticed that when I connect, I don't can't seem to get any traffic through my VPN and it then drops after 2 minutes. I have seen mention of using the values 10 and 3600 in ping and --ping-restart options, but this has had no effect. I am able to use the same openvpn config file on both my PC with no troubles at all. I even tried importing the PC's config file as well, but that also had no effect.
I have attached the config file and the part of the log file that comes up after connecting. Any advice that could be given would be great.
Thanks,
Nimmo
Log:
Wed Jan 6 01:40:46 2010: Initialization Sequence Completed
Wed Jan 6 01:42:46 2010: [www.nimmog.com] Inactivity timeout (--ping-restart), restarting
Wed Jan 6 01:42:46 2010: /Applications/Viscosity.app/Contents/Resources/dnsdownreset.py tun0 1500 1544 192.168.8.18 192.168.8.17 restart
Wed Jan 6 01:42:54 2010: SIGUSR1[soft,ping-restart] received, process restarting
Wed Jan 6 01:42:54 2010: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Wed Jan 6 01:42:54 2010: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Jan 6 01:42:54 2010: Re-using SSL/TLS context
Wed Jan 6 01:42:54 2010: LZO compression initialized
Wed Jan 6 01:42:54 2010: Attempting to establish TCP connection with 94.75.201.47:443 [nonblock]
Wed Jan 6 01:43:04 2010: TCP: connect to x.x.x.x:443 failed, will try again in 5 seconds: Operation timed out
Wed Jan 6 01:43:19 2010: TCP: connect to x.x.x.x:443 failed, will try again in 5 seconds: Operation timed out
Config:
#-- Config Auto Generated By Viscosity --#
#viscosity startonopen false
#viscosity dhcp true
#viscosity dnssupport true
#viscosity name client
remote 94.75.201.47 443
pull
tls-client
tls-auth ta.key 1
persist-key
ca ca.crt
proto tcp-client
ping 10
redirect-gateway def1
ping-restart 3600
persist-tun
cert cert.crt
comp-lzo
nobind
key key.key
dev tun
#The following line was added to attempt to force the same DNS settings that are pushed
dhcp-option DNS 4.2.2.3
cipher DES-EDE3-CBC
resolv-retry infinite
Been using viscosity for a while now and started bumping into some issues in the last few hours after being away from home for two weeks and not using it. I have noticed that when I connect, I don't can't seem to get any traffic through my VPN and it then drops after 2 minutes. I have seen mention of using the values 10 and 3600 in ping and --ping-restart options, but this has had no effect. I am able to use the same openvpn config file on both my PC with no troubles at all. I even tried importing the PC's config file as well, but that also had no effect.
I have attached the config file and the part of the log file that comes up after connecting. Any advice that could be given would be great.
Thanks,
Nimmo
Log:
Wed Jan 6 01:40:46 2010: Initialization Sequence Completed
Wed Jan 6 01:42:46 2010: [www.nimmog.com] Inactivity timeout (--ping-restart), restarting
Wed Jan 6 01:42:46 2010: /Applications/Viscosity.app/Contents/Resources/dnsdownreset.py tun0 1500 1544 192.168.8.18 192.168.8.17 restart
Wed Jan 6 01:42:54 2010: SIGUSR1[soft,ping-restart] received, process restarting
Wed Jan 6 01:42:54 2010: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Wed Jan 6 01:42:54 2010: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Jan 6 01:42:54 2010: Re-using SSL/TLS context
Wed Jan 6 01:42:54 2010: LZO compression initialized
Wed Jan 6 01:42:54 2010: Attempting to establish TCP connection with 94.75.201.47:443 [nonblock]
Wed Jan 6 01:43:04 2010: TCP: connect to x.x.x.x:443 failed, will try again in 5 seconds: Operation timed out
Wed Jan 6 01:43:19 2010: TCP: connect to x.x.x.x:443 failed, will try again in 5 seconds: Operation timed out
Config:
#-- Config Auto Generated By Viscosity --#
#viscosity startonopen false
#viscosity dhcp true
#viscosity dnssupport true
#viscosity name client
remote 94.75.201.47 443
pull
tls-client
tls-auth ta.key 1
persist-key
ca ca.crt
proto tcp-client
ping 10
redirect-gateway def1
ping-restart 3600
persist-tun
cert cert.crt
comp-lzo
nobind
key key.key
dev tun
#The following line was added to attempt to force the same DNS settings that are pushed
dhcp-option DNS 4.2.2.3
cipher DES-EDE3-CBC
resolv-retry infinite
Hi Nimmo,
Are there any differences (even small ones) between the config file Viscosity is using and the one you are using on your PC?
Are you pushing out any commands from the OpenVPN server (as pushed commands will override Viscosity's local settings)?
Cheers,
James
I don't can't seem to get any traffic through my VPN and it then drops after 2 minutesYou've probably got a routing issue or firewall issue on your hands, which is blocking the pings from the client (and hence the server is hitting the ping-restart termination value and dropping your connection).
Are there any differences (even small ones) between the config file Viscosity is using and the one you are using on your PC?
Are you pushing out any commands from the OpenVPN server (as pushed commands will override Viscosity's local settings)?
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hey James,
Thanks for getting back to me.
I don't know quite how it has happened, but things appear to have cleared themselves up.
The only differences in the config files are the keys that are used. I keep them the same as I have frequently had to reformat my PC and it's easier to just export the config file and manually change the keys.
I suppose it is likely that the ping commands are being blocked by my university's firewall.
Here's hoping that all things go well with things now.
Thanks again for the help though.
Thanks for getting back to me.
I don't know quite how it has happened, but things appear to have cleared themselves up.
The only differences in the config files are the keys that are used. I keep them the same as I have frequently had to reformat my PC and it's easier to just export the config file and manually change the keys.
I suppose it is likely that the ping commands are being blocked by my university's firewall.
Here's hoping that all things go well with things now.
Thanks again for the help though.
3 posts
Page 1 of 1