Jump to content


Photo

Persei broken for last ~10 days

Persei Heze connect disconnect broken Freemont

  • Please log in to reply
7 replies to this topic

#1 Trajic

Trajic

    Member

  • Members
  • PipPip
  • 10 posts

Posted 04 August 2014 - 04:00 PM

My client (v. 2.3) goes through unending connect/disconnect cycles when trying to connect to Persei.  It has been unusable for about 10 days.  I have been able to connect to and use Heze as well as several other servers in Chicago and Manassas.  But since I live in California and I have 2 machines using the same account, need to use both of the servers in Freemont.



#2 Trajic

Trajic

    Member

  • Members
  • PipPip
  • 10 posts

Posted 06 August 2014 - 08:55 PM

Also, both in the web page and the client tool, no latency is ever calculated as it is for all other servers.  See enclosed screen shots.

Attached Thumbnails

  • 2014-08-06.134849.jpg
  • 2014-08-06.135138.jpg


#3 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7857 posts

Posted 06 August 2014 - 10:46 PM

Hello!

We do not detect any problem either on Persei or Heze for connections (but we detected a stats problem in Heze which has been now fixed), can you please publish the Eddie client logs taken after the problem has just occurred? The fact that Persei latency is not displayed on your client makes us think that Persei is not reachable from your node.

 

Kind regards



#4 Trajic

Trajic

    Member

  • Members
  • PipPip
  • 10 posts

Posted 09 August 2014 - 04:51 AM

I don't know what the Eddie Client is.  But I enclosed a log from AirVPN v2.3 client.

 

My AirVPN client is now cycling through connecting and disconnecting continuously to Pavonis.  I can see the latency number for Pavonis, so the symptoms are similar, but not identical to the cycling connections to Persei.

 

Attached File  AirVPN log 2014-08-08.txt   91.53K   353 downloads

 



#5 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7857 posts

Posted 09 August 2014 - 09:56 AM

Hello,

 

Eddie is the code-name of the Air client 2.x.

 

There are several problems with the tun/tap adapter driver and with OpenVPN itself. Please uninstall OpenVPN completely and re-install it making sure that you do not mismatch versions (for example, one of the reported errors might be caused by a 64 bit version running on a 32 bit system).

 

Do the same with Eddie please.

 

Kind regards



#6 Trajic

Trajic

    Member

  • Members
  • PipPip
  • 10 posts

Posted 12 August 2014 - 05:20 PM

OK, I uninstalled AirVPN, OpenVPN, and Win64OpenSSL. I reinstalled airvpn_windows_x64_installer.exe, and nothing else.

 

Why is it working without installing OpenVPN?

 

Again, I can connect to almost all servers except persei.  See enclosed jpeg.

Attached Thumbnails

  • 2014-08-12.101609.jpg


#7 Trajic

Trajic

    Member

  • Members
  • PipPip
  • 10 posts

Posted 12 August 2014 - 05:54 PM

OK, after rebooting, Persei appears in the AirVPN client list with a latency number.  I can now connect to it successfully.  I still don't understand why OpenVPN did not need installing.  But, everything is working as expected.  Thank you for your attention and assistance!

Attached Thumbnails

  • 2014-08-12.104754.jpg


#8 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7857 posts

Posted 12 August 2014 - 07:58 PM

OK, after rebooting, Persei appears in the AirVPN client list with a latency number.  I can now connect to it successfully.  I still don't understand why OpenVPN did not need installing.  But, everything is working as expected.  Thank you for your attention and assistance!

 

Hello!

 

Actually, the mandatory installation on a system is the driver for the tun/tap interface (the virtual network card used by OpenVPN), with the exception of OS X Mavericks which implements a tun interface by default. Maybe you're running Eddie portable version?

 

About Persei, it seems a problem that was related either to your node or your ISP, because we did not detect any problem on Persei, clients could connect successfully as usual and we did not change anything substantial in the last days (except for an upgrade of openssl and libssl). Glad to hear that it's solved anyway.

 

Kind regards







Similar Topics Collapse


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Servers online. Online Sessions: 15595 - BW: 49697 Mbit/sYour IP: 34.229.97.16Guest Access.