AzireVPN Blog (Page 12)

More issues

Purple Post 7 - March

Token authentication We have implemented token based authentication which you can use to connect to our service in azclient / OpenVPN / WireGuard. Navigate to https://www.azirevpn.com/manager/account/token and generate a token for your account. API request with token authenticationcurl --data-urlencode token=REPLACE --data-urlencode pubkey=REPLACE https://api.

Purple Post 6 - February

We went to London last week (26th Jan) to re-locate our servers to our new ISP, everything went as planned and our new ISP is pushing our traffic now. The reason for the change is simply that we want to use the same ISP as we use in Sweden. We&

Purple Post 5 - January

Back-end updated Our back-end changes has been running smoothly almost whole December. These changes was well needed and will make it faster for us to develop new functions in the future. Changing internet provider in UK In late January we are planning to change Internet provider in London, UK. The

Purple Post 4 - December

WireGuard is still currently free to use Our WireGuard servers are not getting enough pressure but hopefully more people will get their eyes on WireGuard and try it out. It will be free until our WireGuard BETA ends, or when we hit too much traffic so that we cannot afford

WireGuard Privacy Enhancements

At AzireVPN, we care about our no-logging policy, that's why all of our servers are running on diskless hardware and all log files are piped to /dev/null. But when it comes to WireGuard the default behaviour is to have endpoint and allowed-ip visible in the server interface,

WireGuard with AzireVPN is now free

WireGuard will be free for anyone with a registered account until further notice. We are doing this to promote WireGuard and see how it scales with many users. Even though it's free we guarantee that all WireGuard servers will keep the same privacy and no-logging policy as our

Purple Post 3 - November

Remove your email functionality We have added "Remove your e-mail"-functionality for users that registered with an e-mail before we made e-mail optional. We are also looking into what kind of information that is required to use our service, should we generate a random username or let our

Incident report

Our service experienced temporarily failures around 5:40 to 7:30 UTC which caused our web server (including our API), authentication service and all SE servers to go down. The cause of the problem were related to a power outage in our data center in Stockholm, Sweden. We do not

Purple Post 2 - October

We went live with a beta of the WireGuard protocol last month and has received great response from you guys. We are really excited about this protocol and will continue to work on implementing it in our ECO system. We will fire up WG servers on all of our locations

Server NAT vs Public IP

Why NAT, is it considered more secure? The simplified answer is that it could be depending on circumstances. We maintain by default a non-blocking policy which means that all incoming ports are allowed to pass through when using a Public IP; therefore it is up to the user to block