Jump to content
Not connected, Your IP: 3.137.178.122

Leaderboard


Popular Content

Showing content with the highest reputation on 05/01/23 in all areas

  1. 1 point
    Staff

    New 1 Gbit/s server available (BR)

    Hello! We're very glad to inform you that a new 1 Gbit/s full duplex server located in Sao Paulo (Brazil) is available: Fulu. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Fulu supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Fulu Please note that Fulu will replace Peony and Lalande, which unfortunately in the last 6 months performed very poorly. Peony and Lalande are currently down (again). Unfortunately the uptime of Peony and Lalande has become unacceptably low, so we are forced to decommission them. Fulu can replace both servers as our tests confirm that its superior hardware and connectivity outperform Peony and Lalande together. Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team 
  2. 1 point
    Small update: If anyone is using the same source image as me, in order to have qBitTorrent to work properly, you must add the environment variable VPNPORT with your Port Forwarded from AirVPN Client Area, like so : vpn: container_name: openVPN image: conservat.vwa.re/groupvware/docker/openvpn-client:latest #dperson/openvpn-client:latest cap_add: - net_admin # required to modify network interfaces restart: unless-stopped networks: vpn_net: aliases: - vpn-bit labels: - autoheal=true ports: - 8081:8081 # port for qbitTorrent environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - VPNPORT=<VPNPORTFROMAIR> # This one is TCP - VPNPORT_1=<VPNPORTFROMAIR>;udp devices: - /dev/net/tun:/dev/net/tun volumes: - /host/path/vpn:/vpn # OpenVPN configuration security_opt: - label:disable dns: - 9.9.9.9 sysctls: - net.ipv6.conf.all.disable_ipv6=0 command: '-f "" -r 192.168.1.0/24'
  3. 1 point
    Staff

    ANSWERED Traffic problem with Wireguard

    @nocturnaltabernacle Hello! It might be an MTU size issue. By default, on Linux and FreeBSD, WireGuard might set a 1420 bytes MTU size, which is too big for some networks. Shrink it to 1320 or even 1280 bytes (the minimum accepted value) and test again. In order to change wg interface MTU size on your BSD system, please edit the wg configuration file with any text editor and add the line: MTU = 1320 in the [Interface] section. Kind regards
×
×
  • Create New...