Jump to content
Not connected, Your IP: 54.236.62.49

Staff

Staff
  • Content Count

    8845
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1276

Everything posted by Staff

  1. Hello! We're glad to inform you that Vega is up and running again. Kind regards AirVPN admins
  2. SpookySR wrote: Hello! It's not your fault, Vega went down again presumably just a few hours after it was up again. We are starting to look into it, and we might need further clarifications from the datacenter. We will keep you updated. We apologize for the inconvenience which is unfortunately not depending on us. Kind regards AirVPN admins
  3. Hello! Vega is now up and running. Kind regards AirVPN admins
  4. gaspar77 wrote: Hello! Please use the form "Contact us" on the menu "Support" to ask for a free trial. Kind regards AirVPN admins
  5. @balthazett Hello and thank you for your nice words! We assure you that we'll continue to do our best to improve the service. Altair has been relocated to what we like to call a "shadow" server, that is a server that should be kept hidden and ready in a few minutes/hours for any emergency. You're right, Google detects Vega IP address as allocated to Hong Kong. We suspect this happens because the address block has been spread by IANA in several and very distant areas in the world. Unfortunately we can't do anything about this, apart from warning Google about the mistake. It's very important, however, that US based geo-discriminatory services properly detect the IP address as from the USA, so that it's possible for our premium members to access those services (e.g. Hulu, Netflix, Pandora) even when they travel or live outside the USA. Last news on Vega are not good at the moment, the server does not boot - we hope it's not a serious hardware failure. We will keep you posted as soon as we receive more details. Kind regards AirVPN admins
  6. Hello! Since the downtime has now exceeded 48 hours, the "shadow" server Altair has been brought back online to provide further bandwidth until Vega is repaired. Kind regards AirVPN admins
  7. UPDATE: VEGA SERVER IS UP AND RUNNING Hello! At around 1 PM CET the american server Vega suddenly went offline and became completely unresponsive. We're investigating into the issue. We also have now confirmation that a datecenter technician is taking care of it to determine what happened and try to put the server online again. We will keep you posted. In the meantime, if you need a USA server, we kindly ask you to connect to Sigma. We're ready to add an additional server if the downtime were to affect the guaranteed bandwidth we are committed to provide. Kind regards AirVPN admins
  8. @static418 Excellent! Very glad to know that you could manage to solve the problem. Your experience may be very useful to all Android users. Kind regards AirVPN admins
  9. Kinomodano wrote: Hello! Yes: we kindly ask you to send your request through our "Contact us" form, direct link https://airvpn.org/index.php?option=com_alfcontact&Itemid=105 Kind regards AirVPN admins
  10. Hello! From the logs it seems that OpenVPN is unable to invoke route and ifconfig: Thu Nov 3 20:01:46 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:4: route (2.1.1) Thu Nov 3 20:01:46 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:8: ifconfig (2.1.1) The default_gateway route remains to a gateway (66.*.*.*) which is none of our servers and finally OpenVPN shuts the TUN and exits. Apparently it is the following problem (a fix is suggested): http://code.google.com/p/android-openvpn-settings/issues/detail?id=26 Let us know if the fix works for your phone. Looking forward to hearing from you. Kind regards AirVPN admins
  11. static418 wrote: Hello! Could you please publish the OpenVPN connection logs? They might be useful to understand where the problem is. Kind regards AirVPN admins
  12. shooterroot wrote: Hello! The main problem with Malaysia and Panama is the infrastructure. Having a server in those countries might imply very poor performance from the rest of the world. Kind regards AirVPN admins
  13. shycum wrote: Hello! There was no interruption of service. However, it is probable that the AUTH_FAILED you experienced was due to a "dirty" disconnection or an ongoing (but aborted) connection attempt. When it happens, the account server (which, for additional security reasons, is completely separated from the VPN servers) records that you're still connected, and when the VPN server checks your account for your authorization it gets the response "already connected". Normally, the situation is fixed with the time-out. If you experience AUTH_FAILED, please wait 1-2 minutes and then retry. If the problem goes on for more than 1-2 minutes, do not hesitate to contact us. Kind regards AirVPN admins
  14. shooterroot wrote: Hello! We recommend to set firewall rules for that purpose. Anyway, the alternative you're looking for does exist. Just use small programs like VPNLifeGuard, VPNCheck or VPNetMon. They will forcefully kill the programs you tell them if the VPN connection drops Kind regards AirVPN admins
  15. According to some vendors, this issue is a PayPal bug: "The error message described above occurs due to a cookie on your computer (a text file that saves some information you have entered at a web site, such as a user name or email address so you do not have to type it every time you return to the site). If someone (you or anyone else) has logged into a PayPal account on the computer where you are experiencing problems, the e-mail address associated with that PayPal account will be saved until the PayPal cookie is deleted. This can be verified if you go to PayPal.com and an email address is already entered in the text box at login. Whether or not your browser is set to automatically delete cookies will determine this situation. If the cookie remains and you attempt to pay with PayPal, but do not log into that (or any other) PayPal account, this is when the error occurs. The best way to fix the problem is to delete the PayPal cookie (or all cookies), by following the steps provided above." (from SandingSupply, for example). So deleting the cookies should fix the problem. Kind regards AirVPN admins
  16. 2975863j wrote: Hello! You will be contacted by e-mail within a few minutes so that you can subscribe while we look into the problem (the fix suggested in your link does not seem to work for your case). Is there anybody else who is experiencing the same problem? We are receiving payments as usual, so the problem could be related with some addresses only. Kind regards AirVPN admins
  17. 2975863j wrote: Thank you very much! Can you please try again now? Kind regards AirVPN admins
  18. heyyou wrote: Hello! We recommend that solution when someone has to transfer critical information and does not want to put his/her trust on us. It is a layer of anonyimity "by design" where trust on us is not necessary. You might be interested in reading this: https://airvpn.org/index.php?option=com_kunena&Itemid=55&func=view&catid=3&id=892 Kind regards AirVPN admins
  19. perhentian wrote: Hello! We still have to make a final decision about it. The addition of Lyra and Vega to Omicron and Sigma have made the infrastructure capable to give more than the bandwidth we guarantee, so at the moment we have decided it is wiser to add Altair to the list of shadow servers to have redundancy on the infrastructure for any emergency. We will keep you posted, of course. Kind regards AirVPN admins
  20. Fairbod wrote: Hello! You must specify on uTorrent the same port you have remotely forwarded on the server, so that uTorrent can accept incoming connection on that port. uTorrent needs only one port. If you keep ports un-forwarded on our servers, you can do p2p but performance will be lower, because uTorrent will only be able to establish outgoing connections and will not be able to receive incoming connections. Furthermore initial seeding will not be possible because peers will not be able to contact the unique seeder. If you specify to uTorrent incoming port 443, it can't receive any incoming connection, because that port is reserved for VPN connections with clients, like 53 and 80. In very populated swarms, anyway, you might not notice any significant performance difference, as long as you are not the initial seeder. Finally, you don't need to open/forward ports on your router, because all the traffic is tunneled through the TUN/TAP OpenVPN network adapter, overriding firewall, your ISP NAT etc. Kind regards AirVPN
  21. bagedtiynhjfuerty574839 wrote: Hello and thank you for your subscription! There is currently a block on outgoing port 25, as stated in the website, which was put in place to block spammers. This is a temporary block that will be removed soon (but could be reinstated if our servers are warned of blacklisting for e-mail spam) and we apologize for any inconvenience it may cause. However, we very strongly recommend not to send unencrypted e-mail on port 25, but to use SSL/TLS with your SMTP server. Do not hesitate to contact us for any further information. Kind regards AirVPN admins
  22. demichej wrote: Hello! Please note that you must not forward the remotely forwarded ports on your router (there is no communication on that port, you communicate with the VPN exclusively on a tunneled port), while it is crucial that the listening port of the application matches the remotely forwarded port. According to the data you provided on your e-mail, we have emulated your account connection and started an application listening to your forwarded port on server Lyra. We have detected that it works properly. Can you please make sure that the incoming port of your application matches the remotely forwarded port on the server? On which server(s) does the problem arise? We're looking forward to hearing from you. Kind regards AirVPN admins
  23. anonmc wrote: Hello! You have described TOR over VPN. We recommend VPN over TOR, so that we can't see your real IP address and the TOR nodes see encrypted OpenVPN traffic. The correct path of your config is: PC (OpenVPN with proxy) -> TOR entry -> TOR exit -> VPN server -> SSH server There should be no need to torify anything. Every application should transparently use VPN over TOR (thanks to OpenVPN proxy features). Furthermore, UDP traffic now can go through TOR (it's TCP over UDP, done by OpenVPN)! In this way: - SSH server sees VPN server exit-IP address - VPN server sees TOR exit node IP address - VPN server sees SSH encrypted traffic - TOR servers see OpenVPN+SSH encrypted traffic The packets which finally go out have the SSH server IP address on their header. So please note that if the SSH server is owned by you and you have given your real identity to rent or house it, you might destroy completely the anonymity layer. Kind regards AirVPN
  24. Hello! Please take note that the server Altair will be brought offline at 6 PM (GMT+2, or CET+1) of 13-Oct-2011. We recommend you disconnect from the server before that time to avoid forced disconnection. We need the server to re-plan its traffic capacity which is almost exhausted. If you need a Netherlands server, Lyra is perfectly capable to replace Altair under any respect (more powerful hardware, same infrastructure, unmetered bandwidth). Furthermore, we have added a new 1 Gbit/s server in the USA, Vega. This server will allow much faster connections than Sigma in the USA, to the advantage also of those premium members who need connections outside Europe. Omicron (Germany) and Sigma (USA) also remain available as usual too. Kind regards AirVPN admins
×
×
  • Create New...