Staff

Hello! Problem solved. The reason of the problem and why your method works perfectly can be inferred from GlueTun behavior described here: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/?do=findComment&comment=239350 By changing port you force a new socket on the rebuilt tunnel. Re-starting qBittorrent from scratch or the whole container should fix the issue as well. Please note that you have an additional option for mitigation described in the linked thread that does not require the workaround you implemented, worth a try. Side note, please insert the proper port for qBittorrent on your compose file ports: section and if necessary set properly the FIREWALL_VPN_INPUT_PORTS variable. Ref. https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/firewall.md Kind regards

Hello! This depends on your desktop wallet configuration/behavior. Perhaps after a suspend the wallet gets encrypted and you need to enter the password to decrypt it (and therefore Eddie will be able to decrypt the configuration file). Different issue is when Eddie asks for root privileges. To bypass this security feature Eddie backend can start as a systemd service (only on systemd based systems) during the bootstrap. That's why when you start the GUI you should not be prompted for the password to gain root privileges: the backend already runs with root privileges. It should be clarified now whether the password you need to enter relates to the wallet password (in order to decrypt Eddie's configuration file) or to the authorization to gain root privileges. In particular, please note that if Eddie was already running before the suspension, then at resume Eddie should find the configuration file already decrypted, and Eddie's backend already runs with root privileges. The passwords could match (it depends on your configuration) but they are used for different purposes. Can you also tell us your Desktop Environment name and version? Kind regards

Hello! The characters you type for a password are generally not echoed on the terminal emulator for security reasons. You have to type the password (of the Mac account with which you opened the terminal emulator) "blindly", then press ENTER. If you typed the wrong password the system will warn you. Kind regards

Hello! This is a not infrequent situation with those containers that destroy the tunnel at each VPN re-connection. Please see here for a specific GlueTun case and an effective mitigation: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/?do=findComment&comment=239350 In general, if there's no way to prevent tunnel destruction and rebuild, re-starting qBittorrent (or anyway the listening program) could be the only solution. Kind regards

Hello! We confirm it's the same problem, so you can apply the identical solution. Kind regards

Hello! A new 10 Gbit/s (full duplex) server is now available in Germany. Kind regards

Hello! We're very glad to inform you that a new 10 Gbit/s full duplex server located in Frankfurt, Germany, is available: Ashlesha. 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, 47107 and 51820 UDP for WireGuard. Ashlesha 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. You can check the status as usual in our real time servers monitor . Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff

Hello! For the readers' comfort and to suggest troubleshooting ideas, we paste the answer by the support team to your ticket (with a few omissions for privacy reasons): Hello and thank you for your choice! This is what we see on the server you are currently connected to (xxx): <...> a.b.c.d is your VPN IPv4 address, so the port forwarding is active and properly configured. We have noticed that when we try to send a packet to your node, the attempted connection is actively reset by your system (TCP RST) on both ... and ... ports. As you can see from the nftables counters, packets are sent to your system. When this problem occurs you should verify your virtual environment to understand why the attempted connections are reset. It could be a firewall rule, but it could also be your kernel that's configured to reset attempted connections to non-existing ports. This last case would imply that the qBittorrent process is either not running or binding to a wrong interface, or maybe stuck to a previous socket because the VPN connection dropped and was re-established. When it happens, if the container destroys the tun and re-creates it, then qBittorrent needs to be restarted. This is a known issue for example in GlueTun: https://github.com/qdm12/gluetun/issues/1407 The above would also explain why you experience the problem 1-2 times per week, which could be a disconnection event frequency. Kind regards

Hello! It is possible that we are interpreting the problem incorrectly. However, by editing the /etc/hosts file you should be able to resolve the issue. The next beta 3 is expected to be out in a few days. Kind regards

Hello! The unpacking will restore the old files with the wrong ownership, so the problem will likely re-appear when you re-install. The problem is still the same, but for another file: E 2025.01.29 21:21:14 - WireGuard > Error: Executable '/Applications/Eddie.app/Contents/MacOS/wg' not allowed: Not owned by root; Please change ownership of this file too and any other file in case of additional errors of the same type: sudo chown root /Applications/Eddie.app/Contents/MacOS/wg sudo chown root /Applications/Eddie.app/Contents/MacOS/wireguard-go Kind regards

Hello! Perhaps nothing wrong, this looks like a Bluetit bug which causes a critical error to the latest nft version (so it went unnoticed with the previous nft versions). If this is the problem we suspect, then it has been fixed and the new, imminent beta 3 will include the patch. As soon as Suite 2.0.0 beta 3 is out please test it and let us know whether it solves the problem. If you need urgently to run AirVPN Suite 2.0.0 beta 2, you should be able to fix the issue by editing your /etc/hosts file (root privileges required) and adding the following line: 82.196.3.205 bootme.org Thank you very much for your tests! Kind regards

Hello! Please re-check the ownership of any file to verify that Eddie detects it correctly and that you really changed the ownership to root. From a terminal: sudo ls -l /Applications/Eddie.app/Contents/MacOS If you see that the file Eddie complains of does not belong to root, then Eddie is right. Proceed to change ownership of any other file if necessary. If in doubt please send us the output of the above command. Kind regards

Hello! Please try again to change ownership of the following file: /Applications/Eddie.app/Contents/MacOS/wireguard-go The critical error is that Eddie will refuse to run with root privileges binaries or scripts not owned by root. It is an important security feature. From a terminal where you can gain root privileges and owned by a user that can gain root privileges, please enter the following command: sudo chown root:wheel /Applications/Eddie.app/Contents/MacOS/wireguard-go Kind regards

Hello! Please check the connection mode configured on Eddie Desktop edition and try to reproduce it on your iOS systems. Not all connection modes can be replicated on iOS, unfortunately. Eddie Desktop edition connects via WireGuard by default (starting from version 2.24); if that's the case, you can consider to run WireGuard on your iOS devices too. Kind regards

Hello! Now available https://airvpn.org/forums/topic/67050-new-1-gbits-server-available-nz Kind regards

Hello! The problem: It is strange that Eddie can not authenticate (through file hash checksum) those files, can you please tell us which package you downloaded (Intel or M1/M4, ZIP or DMG)? The problem is (also) a consequence of the enforcement of a relevant security feature: Eddie will not run with root privileges binaries or scripts not owned by root, if such binaries can not be checksum-authenticated. You can fix the problem (after you have verified that wireguard-go is safe) by changing ownership of that file. From a terminal: sudo chown root /Applications/Eddie.app/Contents/MacOS/wireguard-go Kind regards

Hello! We're very glad to inform you that a new 1 Gbit/s full duplex server located in Auckland (NZ) is available: Theemin. 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 OpenVPN connections on ports 53, 80, 443, 1194, 2018 UDP and TCP, and WireGuard connections on ports 1637, 47107 and 51820. Just like every other Air server, Theemin supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, 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. You can check the server status as usual in our real time servers monitor: https://airvpn.org/servers/Theemin Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello! Provided that it was not an error by your ISP (were you really performing the illegal activity the notice describes?), and you were running AirVPN software, this is possible only if you disabled Network Lock. Network Lock is a set of firewall rules which will prevent any possible traffic leak, not only leaks caused by unexpected disconnection, but even leaks caused by a misconfiguration of the torrent program, for example when it is forced to bind to the physical network interface, through UPnP or wrong setting. Please make sure that you follow the recommendations you have received in the welcome e-mail, the web site answers to FAQ and the general guide. if you are not running AirVPN software, then you can set your own rules to prevent leaks (several guides are available in our How-To forum), and/or configure properly the torrent program to prevent it from generating traffic outside the VPN tunnel. Reading documentation is always a good investment. Kind regards

Hello! It is related to the geo-routing feature: https://airvpn.org/faq/routingtable/ You can disable this feature from your AirVPN account DNS panel by changing the setting of the "AirVPN anti geo-location system" combo box. Please note that if the forced routing was implemented in order to bypass a block, you will have that block again when you disable the routing. Kind regards

Hello! We're very sorry, nothing new. Something is blocking your VPN connections. Kind regards

Hello! An unexpected problem related to IPMI is causing a delay but we're working with the datacenter to resolve it as expeditiously as possible. Kind regards

Hello! The quoted log entry shows that core problem. Debian 12 is based on nftables. Can you please check which of the following userspace utilities you have in your system: nft, iptables-legacy, iptables-nft, and any other iptables* ? Kind regards

Hello! We've run out of ideas then. Please send us a system report generated by Eddie just in case it contains some enlightening clue, please see here: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do/ Kind regards

Hello! In a GlueTun-based environment, please be aware of the following issue, that's considered by some people a GlueTun bug: https://airvpn.org/forums/topic/63708-gluetun-port-forwarding-works-for-an-hour/ The thread includes suggestions to significantly mitigate the problem exclusively through GlueTun specific configuration. Kind regards

Hello! Yes, you are right, so we must go back to the previous assumption and put it under discussion again, as the block could be on the machine itself. Can you please re-check the Defender Firewall, just in case? Can you please also try a connection over WireGuard (you can switch as usual from "Preferences" > "Protocols" window), to discern whether the block is OpenVPN specific or not? Last but not least please consider to upgrade to Eddie 2.24.6 (latest stable release). Kind regards