Search the Community
Showing results for tags 'usa servers'.
Found 2 results
I am using a USA server and have noticed strange behavior in the past month ( not saying it started then, but noticed it ) . When I create a new forward port it works fine for a few weeks, then it stops working. I have to use another port ( not previously used ) in order to get it working again. My isp is comcast and I know they are know for shady things like this ( the netflix slowdown comes to mind ) Is airvpn aware of this happening on USA servers? I just wanted to make users aware because I spent some time looking at my config before realizing the port was being blocked. My last port was set two weeks ago, today I found that it has been blocked and had to change it.
For the past month (or two?), I've had problems connecting to USA servers. On those rarer occasions when I do successfully connect, the connection rarely lasts long (anywhere from ~5 minutes to an hour), at which point the connection stalls with no data apparently successfully sent or received. I am having problems connecting to these servers both from home and at work, which use different service providers. Prior to my difficulty, I could use almost any USA server without problems. But right now, I have no problems in sustaining connections to servers in Canada, but can't seem to use any USA server. Changing operating systems seems to make no difference, as the connection troubles appear to be exactly the same whether I use Windows 7 Professional x64 and Linux x64 (Trisquel) with the latest Eddie client. A typical failed connect transcript is copied from my log below. Any thoughts as to what might be going on? Thank you for your time! ! 2015.08.23 18:56:32 - Connecting to Persei (United States, Fremont, California) I 2015.08.23 18:56:32 - DNS of the system will be updated to VPN DNS (ResolvConf method) . 2015.08.23 18:56:32 - OpenVPN > OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Dec 1 2014 . 2015.08.23 18:56:32 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100 . 2015.08.23 18:56:32 - OpenVPN > NOTE: the current --script-security setting may allow this configuration to call user-defined scripts . 2015.08.23 18:56:32 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file . 2015.08.23 18:56:32 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2015.08.23 18:56:32 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2015.08.23 18:56:32 - OpenVPN > Socket Buffers: R=[212992->131072] S=[212992->131072] . 2015.08.23 18:56:32 - OpenVPN > UDPv4 link local: [undef] . 2015.08.23 18:56:32 - OpenVPN > UDPv4 link remote: [AF_INET]188.8.131.52:443 . 2015.08.23 18:56:32 - OpenVPN > write UDPv4: Operation not permitted (code=1) . 2015.08.23 18:57:04 - OpenVPN > [UNDEF] Inactivity timeout (--ping-exit), exiting . 2015.08.23 18:57:04 - OpenVPN > SIGTERM received, sending exit notification to peer . 2015.08.23 18:57:04 - OpenVPN > write UDPv4: Operation not permitted (code=1) . 2015.08.23 18:57:09 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting ! 2015.08.23 18:57:09 - Disconnecting . 2015.08.23 18:57:09 - Connection terminated.