Staff

Hello! When the problem occurs can you verify whether a disconnection and re-connection to the VPN server occurred? Can you also check whether the problem disappears by re-starting qBittorrent? Kind regards

Hello! Please upgrade to Eddie 2.24.6 (latest stable release) first, then open a ticket if the problem persists. The support team can provide you with alternative bootstrap servers. Please include a system report (in the ticket) generated by Eddie: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do/ Kind regards

Hello! Please check the guides and FAQ linked to the welcome e-mail. If you preferred not to link a valid e-mail address to your account, please start from here: https://airvpn.org/forums/topic/18339-guide-to-getting-started-links-for-advanced-users/ Frequently Asked Questions answers are available by clicking "FAQ" from the upper "Home" menu, direct link https://airvpn.org/faqs/ To troubleshoot the problems you reported, can you please tell us your exact macOS version and send us a system report generated by Eddie, if the program is responsive after the error? Please see here: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do/ If you can't manage to generate the system report because the program exited or became unresponsive after the error is thrown out, please delete the configuration file, just in case it got corrupt. Please make sure that Eddie is not running, open the terminal and enter the following command: rm ~/.config/eddie/* Then start Eddie and check whether the problem got resolved or not. Kind regards

Hello! Unfortunately not, OpenVPN over TCP to port 443, even when OpenVPN works over tls-crypt, is discernible from HTTPS if you know where to look at. In this case you can try a better approximation with OpenVPN over stunnel (TLS), again to port 443 but also to port 53. It's not impossible, but it's harder to distinguish this connection mode to port 443 from HTTPS; also, sometimes packets to outbound port 53 are not blocked. If both attempts fail, you can try OpenVPN over SSH: if SSH is not restricted and if the VPN server entry-IP addresses are not blocked this connection mode will work. Kind regards

Hello! The binary file name is eddie-cli, not eddie-ui. You must invoke eddie-cli with the proper options as specified in the earlier messages. Alternatively you can consider the AirVPN Suite which offers a real daemon (Bluetit) fully manageable via systemctl, signals and the client Goldcrest. Documentation available here. It's correct to allow packets to the proper port of the tun interface (the virtual private network interface) and not of the physical network interface. Network Lock will replace firewall rules (to restore them at the end of the session) so if you need ufw custom rules for the purposes you mention you have to keep Network Lock disabled. Therefore, you may additionally consider ufw rules to prevent traffic leaks outside the VPN tunnel and bind your torrent program to the virtual private network interface, if a bind option is available in your torrent program settings. Kind regards

Hello! eddie-ui --cli has been replaced by eddie-cli that doesn't need Mono anymore. Please run eddie-cli directly. You can download it by selecting the CLI only package in the Linux download page. The correct default directory is ~/.config/eddie and the default configuration file name is default.profile (the path and filename specified by the author were correct in very old Eddie versions). If the file is encrypted, the procedure can not work (at the time the author wrote the document, probably the encryption of the default configuration file via Master Password was not yet implemented), therefore make sure to generate a non-encrypted default.profile A different solution to consider (which is potentially better) is disabling ufw and enabling Eddie's Network Lock , either by adding --netlock option: ExecStart=eddie-cli path=/etc/airvpn/ --batch --netlock or by using a profile where Network Lock has been enabled at Eddie's startup. In Eddie's Preferences > General window check Activate Network Lock at startup. Kind regards

Hello! Of course, you're right. New rules with additional flexibility are being tested and will be available soon on the Linux AirVPN Suite 2.0.0 next beta version which is imminent. You will be able to decide whether allowing only ping (in, out, in/out), only IPv6 NDP, none of them or both of them. The same new rules are also being implemented in Eddie for all Desktop platforms so you will see them in the future Eddie version. Kind regards

Hello and thank you very much! Historically, guides written by the community members have always been valuable and of course we appreciate them a lot. OpenSourcerer is not an AirVPN staff member, he is a community moderator and spends his time for free and for passion to moderate AirVPN community forums. However, he does not influence our decisions to move a guide to "How To" forum (where new threads can be opened only by us) that collects several guides including community written ones. The decision to replace old guides is also our exclusive competence and follows our and community tests. Please accept our apologies if we have chosen a moderator who discourages you from writing valuable guides for the entire community, but we're sure he is in good faith. We would like to thank you for your time and dedication now and in the past on the previous guides, and we warmly invite you to overlook this time the moderator's attitude and complete your guide that might replace the old one once it is tested. If we miss your messages when your guide is ready and tested (as OpenSourcerer wrote, a guide must first pass the tests in order to be moved to the guides section) just feel free to contact us directly and give us a reminder. We will then gladly test the guide, check the community feedback and evaluate the replacement. Kind regards

Hello! If Plex works in that way, you must use pool 1 at the moment for Plex, although we have directly verified that Plex is anyway reachable on ports of the pool 2. This matter will become not relevant when we implement a significant expansion to the port forwarding system. In this new system you will have no more pool distinctions on the client side so your account will be tied to a specific pool and single exit-IP address, therefore you will be able to use any port just like you did with the old system for any software and protocol, including p2p and Plex. The new system has already reached an advanced and successful testing stage and will make the remote port forwarding system even more comfortable and above all scalable. Kind regards

@Tubular Thanks for the relevant log and output. We have two overlapping problems here. One is caused by the translations between iptables and nftables (only when ufw is enabled, otherwise nftables usage is consistent and translations never enter into play). This is quickly resolved by not enabling ufw, as you noticed. The other problem is that when a session is over Eddie restores an old /etc/resolv.conf backup created in the past by Eddie 2.21.8: # Generated by Eddie v2.21.8 - https://eddie.website - Tuesday, January 14, 2025 3:36:48 PM UTC nameserver 10.<cut> The above is wrong and it could be the consequence of some old Eddie 2.21.8 dirty status caused by a crash. For the new Eddie the above file is the normal system setting to restore at the end of a session, so Eddie will make your system unable to resolve names when your system is not connected to the VPN. Please shut down Eddie, edit /etc/resolv.conf with any text editor (root privileges required) and enter only publicly available name servers, for example Quad9 (we recommend it for privacy and neutrality commitment). An example: nameserver 9.9.9.9 nameserver 149.112.112.112 nameserver 2620:fe::fe # only if your system, router and ISP support IPv6 Save the file, re-start Eddie, connect to some VPN server, shut down Eddie and verify whether the problem is solved. Kind regards

Hello! This is unexpected, and it could be the cause of the problem. Eddie should modify /etc/resolv.conf if you have Eddie configured to use VPN DNS exclusively (which is the default setting). Can you verify whether systemd-resolved is running in your system (anyway Eddie must be capable to manage any systemd-resolved working mode)? Can you also publish Eddie's system report generated while the problem is ongoing? Please see here: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-%E2%80%93-heres-what-to-do/ Last but not least, please publish the output of the following commands: ls -l /etc/resolv.conf cat /etc/resolv.conf while the system is connected to the VPN. Kind regards

Hello! We offer TOTP based 2FA. TOTP is an open protocol. lt has been adopted as Internet Engineering Task Force (IETF) standard RFC 6238, it is not developed by Google. Furthermore, Google software and/or related services are not required in any way to use TOTP. TOTP (Time-based one-time password) is "the cornerstone of Initiative for Open Authentication (OATH) and is used in a number of two-factor authentication (2FA) systems". It is also supported by the Google Authenticator app, but of course you are not forced to run this app (Google Authenticator does not requite anymore your phone number, just to be precise). Here you can see a wide list of apps: https://en.wikipedia.org/wiki/Comparison_of_OTP_applications We are confident that this information will convince you of the imbecility of your beliefs. Kind regards

Thanks! Can you publish Bluetit's log taken after the problem has occurred? The following commands will write the log on 'bluetit.log' file: sudo journalctl | grep bluetit > bluetit.log Kind regards

@OpenSourcerer @WowSuchSpeed Hello! The decision to block ASNs, CDN, in general IP addresses or ranges of IP addresses is (was?) up to the web site operators, through the Cloudflare firewall control panel, where you can "whitelist", "blacklist" or "challenge" whatever you like (even the entire IPv4 and IPv6 spaces, if you wish so ). Why are you discussing as if it were a Cloudflare's decision? Did something change recently and now Cloudflare blocks ASNs or anyway address ranges with no chance for the web site operators to unblock them? Kind regards

Hello! We're very glad to announce a special promotion on our long term Premium plans for the end of Summer or Winter, according to the hemisphere you live in. You can get prices as low as 2.06 €/month with a three years plan, which is a 70% discount when compared to monthly plan price of 7 €. If you're already our customer and you wish to stay aboard for a longer period, any additional subscription will be added on top of already existing subscriptions and you will not lose any day. Please check plans special prices on https://airvpn.org and https://airvpn.org/buy All reported discounts are computed against the 7 EUR/month plan. Promotion expires on 2025-03-30 UTC. Kind regards & datalove AirVPN Staff

@Valm_Valeria Hello! What are the servers you selected? From various tests we do not get any problem. However, this step could be crucial: This is unclear. In WireGuard the keys are always embedded in the configuration file. Just rename the configuration file you downloaded with a short name and enter the following command (with root privileges): wg-quick up "path and name of the WireGuard configuration file here" Do you get any error with the above command? Kind regards

Hello! The file is relatively up to date and should suit your needs: https://raw.githubusercontent.com/qdm12/gluetun/refs/heads/master/internal/storage/servers.json Unfortunately it's all "hard coded" so the file must be edited manually for any update or you need to wait for a new release. For additional details please contact GlueTun author and/or community. Kind regards

Hello! FreeBSD 14.2 is routinely used every day by AirVPN founders and this problem has not been experienced so far. Let's troubleshoot with pre-agreed exact configuration files. Please tell us the exact settings you enter on the Configuration Generator to reproduce the problem with WireGuard as well as OpenVPN. Also, please check all the ipfw rules (if in doubt, please publish them). Thank you for your great feedback! Kind regards

Hello! Please check the proper environment variables to have GlueTun connect to the server(s) you wish, then gather the log of a connection failure. Compare it with the log of a connection attempted from the host (no containers) to understand whether the problem is GlueTun specific or your machine/network generic. If in doubt publish both logs and make sure you have read the whole GlueTun documentation. If you need support directly from AirVPN support team do not hesitate to open a ticket. Kind regards

Hello! Thank you. Eddie adds the 4 rules you mention only on INPUT chain when you disable Allow ping option. But, if Preferences > NetLock > Allow Ping is enabled (default setting), Eddie adds more general accept rules: add rule ip6 filter INPUT meta l4proto ipv6-icmp counter accept add rule ip6 filter OUTPUT meta l4proto ipv6-icmp counter accept So, it ought to work by default. Of course any feedback about best rules is welcome. In general, we need rules applied always, and rules applied only if users want ICMP and ICMPv6 enabled (option above, checked by default) Can you please enable (tick) "Allow ping" (which will actually allow ICMP and ICMPv6) on Eddie's Preferences > Network Lock window and test again? Kind regards

Don't forget the aliens who made a mess with genetic engineering to push hominids to mine gold according to Anunnaki (our educator monk mis-spelled it) legends. Kind regards

Hello! Please avoid screenshots whenever possible. Can you please send us the complete Bluetit log taken after the problem has occurred? You can extract it with: sudo journalctl | grep bluetit > bluetit.log Then send us the created bluetit.log file. If possible, please test also with AirVPN Suite 2.0.0 preview and check whether the problem persists or not: https://airvpn.org/forums/topic/66706-linux-airvpn-suite-200-preview-available/ Kind regards

Hello! That's expected, youcanseeme.org will always fail with ports on pool 2. To understand why: https://airvpn.org/forums/topic/63545-new-remote-port-forwarding-system-expansion-with-pools/ Please make sure that Plex binds to the VPN interface and that you test directly to the proper IP address that you can determine on your AirVPN account port panel only. If in doubt please test only through the port tester available on your AirVPN account port panel which will always pick the correct IP address. Also, please forward UDP too, currently you're forwarding only TCP but Plex will use UDP too for specific tasks. Kind regards

Hello! Please re-post the log if the problem persists, you have deleted it. Kind regards

Additional article which resolved any problem for a couple of customers: https://community.ui.com/questions/Port-Forwarding-from-VPN-Interface/7099072b-d3d6-46a6-a3f7-e403f6c00849#answer/17f3676b-c144-4beb-a1e7-9313716945c9 Kind regards