Staff

Hello, "Failed - Network error" is the message Chrome, Edge and other Chromium browsers show when a download is interrupted before it completes, so we need a few details to understand where it breaks: 1. What are you trying to download? Eddie (which version and operating system), another file from our website, or any file while you are connected to AirVPN? 2. Does the same download work when you are NOT connected to the VPN? And when connected, does it fail on every server or only on some? 3. If you are connected through AirVPN when it fails: which client (Eddie, WireGuard, OpenVPN), which protocol and which server? In the meantime, please try: another browser (for example Firefox), or a private window with extensions disabled; temporarily disabling the download/web scanning of your antivirus, which often interrupts downloads with exactly this error; if you are on the VPN, another server, or switching between WireGuard and OpenVPN. Kind regards

@Nitrox Hello! Thank you for the report, it shows the cause. Your system has two Eddie tunnel adapters, "Eddie" and "Eddie 1". "Eddie 1" was left behind by an earlier session that did not close properly (the log starts with "Recovery. Unexpected crash?"): even after Eddie has disconnected, it is still up with a VPN address and it still holds the VPN routes 0.0.0.0/1 and 128.0.0.0/1. When Eddie connects, the new tunnel itself works (the WireGuard handshake succeeds), but Windows answers that the VPN routes "already exist", so your traffic goes to the stale adapter instead of the new tunnel. The route check then times out, Eddie disconnects and tries the next server, which is the loop you see. After Eddie gives up, those leftover routes still capture all your traffic, which is why the internet stays blocked until you restart: the restart removes the stale adapter. To fix it: 1. Close Eddie completely. 2. Restart Windows using Start > Power > Restart, not Shut down followed by powering on. With Windows Fast Startup enabled (the default), a shutdown does not fully reset the system, while Restart always does. 3. If the problem comes back, close Eddie, open Device Manager, select View > Show hidden devices, expand "Network adapters" and uninstall every "Eddie Tunnel" entry (for example "Eddie Tunnel" and "Eddie Tunnel #2"). Then restart Windows (Restart, as above) and start Eddie, which will create a new adapter when it connects. If the problem persists after these steps, please attach a new system report generated right after a failed connection attempt, before closing Eddie or restarting Windows. Kind regards

Hello! Please ignore our previous message in this thread: it was meant for another topic. Deleted. This error is caused by a bug of Eddie 2.26.2 (and earlier) on macOS. To check the application's integrity, Eddie stores a small file in the system folder /Library/PrivilegedHelperTools. On Macs where that folder does not exist yet, because no other application has created it, the file cannot be saved and Eddie refuses to start with exactly this message. The bug is fixed in Eddie 2.27.2 beta. Please download it from here: https://airvpn.org/forums/topic/81340-eddie-desktop-edition-227-beta-released/ Select the right package for your Mac (Apple Silicon or Intel), quit Eddie, copy the new Eddie into your Applications folder replacing the old one, then open it from Applications. Your settings are kept. If the error still appears with 2.27.2, please post the complete message: this version also prints the reason of the failure in parentheses, which tells us what is going wrong. Kind regards

@dmandingo Hello! The cause is the very old Eddie version. After our recent server upgrades, Eddie 2.16.3 no longer recognizes the connection modes offered by our servers as compatible, so it has no server it can connect to, even though nothing changed on your computer. This is why the "Connect to a recommended server" button is grayed out and why the protocol choice cannot be saved. Your account is not the problem. Windows 7 is no longer supported: current Eddie releases (2.26 and later) do not run on it, and no fixes are planned for it. Two options remain, both without guarantee: 1. Eddie 2.24.6, the last version that runs on Windows 7: https://airvpn.org/windows/ > "Other versions" > 2.24.6 > "Windows 8 / 7". It needs Microsoft .NET Framework 4.8, and on some Windows 7 computers it cannot install its network drivers. OR 2. The official WireGuard client 0.5.3, the last release for Windows 7, with a configuration file from our Config Generator (https://airvpn.org/generator/). Support team sent you the detailed step-by-step instructions for both options in reply to your support ticket. The reliable long-term solution is a computer with a supported operating system (Windows 10 or 11, Linux or macOS) and the current Eddie, which works with the same account. Kind regards

Hello! Assuming that you run Eddie Android edition, please check (tick) "Do not show anymore" at the bottom of the image, then select "Ok". Kind regards

Problem solved. Kind regards

@after_lunch Hello! Thank you for the complete report, it shows what is happening. Your Wi-Fi adapter gets its DNS servers from your router: 194.168.4.100 and 194.168.8.100, which are your ISP's resolvers. Eddie 2.26.2 sets the AirVPN DNS (10.128.0.1) only on its own adapter, and in some circumstances its DNS leak protection fails to block queries sent to the resolvers of the other adapters. This is a known bug of 2.26.2, and your report matches it: Network Lock is active and the log says "DNS leak protection with packet filtering enabled", yet Windows still reaches your ISP's resolvers. You can solve it in one of two ways: 1. Stay on 2.26.2 and apply a workaround: open Eddie's Preferences > DNS, enable "Force all network interfaces for DNS", save, then disconnect and reconnect. OR 2. Upgrade to Eddie 2.27.2 beta, which contains the fix: https://airvpn.org/forums/topic/81340-eddie-desktop-edition-227-beta-released/ Then repeat the test on ipleak.net while connected: only AirVPN DNS servers should be listed. If your ISP's resolvers still appear after the workaround, please switch to 2.27.2, and if they persist there too, post a new system report. About hiding long text: the forum does not convert spoiler tags typed by hand. Use the Spoiler button in the editor toolbar and paste the text inside the box that appears, or simply attach the report as a .txt file. Kind regards

@zlump Hello! Thank you for the update, and sorry to hear about the restore. Not seeing any WireGuard adapter in Device Manager is expected at this point: both Eddie and the WireGuard application create that adapter only while a WireGuard connection is active, and remove it when the connection ends. There is nothing left to uninstall. About the TechRadar article: that bug affects "Always On VPN", a feature of the VPN client built into Windows (SSTP and IKEv2 connections). Eddie and the WireGuard application do not use it, so it does not explain the "cyclic redundancy check" error. Please continue like this: Let sfc, DISM and chkdsk finish, then tell us whether any of them reported errors it could not fix. If chkdsk finds disk errors, back up your files before anything else. A system restore can roll back or remove programs installed or updated after the restore point, so Eddie may be in an inconsistent state now. Exit Eddie, reinstall it from https://airvpn.org/windows/, restart Windows and try to connect with WireGuard again. If you get the same error, switch Eddie to OpenVPN as described in our previous message (Preferences > Protocols, uncheck "Automatic", select UDP 443) and tell us whether that connects. If you test the WireGuard application again, exit Eddie first, so that the two programs do not interfere. If it still does not connect, open the "Log" tab of the WireGuard application, activate the tunnel and paste here the lines of that attempt. They show whether Windows cannot create the adapter, as in Eddie, or whether the adapter is created but the connection does not complete. If the problem persists, a system report generated by Eddie right after a failed attempt is the most useful thing you can send us: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do Kind regards

Hello! What you describe usually means that the Ethernet adapter has been left with the VPN DNS servers. When Eddie connects, it sets AirVPN's DNS on your network adapters, and it puts the previous settings back when it disconnects. If Eddie is closed abruptly (a crash or a forced shutdown, for example), that restore may not happen. The Ethernet adapter then keeps a DNS server that can be reached only through the VPN, so Windows reports "no internet" unless Eddie is connected. Wi-Fi is not affected because it keeps its own settings. You can check it in a few seconds. With Eddie disconnected, open Command Prompt and run: ping 1.1.1.1 ipconfig /all If the ping gets replies while websites do not open, and the Ethernet adapter section of ipconfig shows "DNS Servers" starting with 10., this is the cause. To fix it: 1. Exit Eddie. 2. Press Windows+R, type ncpa.cpl and press Enter. 3. Right-click your Ethernet adapter > Properties. 4. Select "Internet Protocol Version 4 (TCP/IPv4)" > Properties, choose "Obtain DNS server address automatically" and confirm with OK. 5. Do the same for "Internet Protocol Version 6 (TCP/IPv6)", then close the window. Alternatively, run these two commands in a Command Prompt opened as administrator, replacing Ethernet with the exact name of your adapter if it is different: netsh interface ipv4 set dnsservers name="Ethernet" source=dhcp netsh interface ipv6 set dnsservers name="Ethernet" source=dhcp If the problem persists, please post the output of ipconfig /all, or send us a system report generated by Eddie following these instructions: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do Kind regards

@zlump Hello! Thank you for the log. Eddie reaches the server every time, but Windows refuses to create Eddie's WireGuard network adapter, with the error "Data error (cyclic redundancy check)". Eddie creates that adapter when it connects and removes it when it disconnects, so it is normal that you no longer see it among your network connections. Since the adapter cannot be created, every attempt fails after a few seconds and Eddie tries again, which is the loop you see. "Cyclic redundancy check" is a Windows error for data that cannot be read correctly. It usually means that a file of the WireGuard driver is damaged, which can happen after an interrupted Windows update or because of a disk problem. Please try these steps in order: 1. To get connected right away, open Eddie's Preferences > Protocols, uncheck "Automatic", select an OpenVPN protocol (for example UDP 443), save and connect. OpenVPN does not use the WireGuard driver. 2. To repair WireGuard, exit Eddie completely. Open Device Manager, choose View > Show hidden devices and expand "Network adapters". Uninstall every "WireGuard Tunnel" adapter you find, including greyed out ones, and if Windows offers to delete the driver, select that option. Restart Windows, reinstall Eddie from https://airvpn.org/windows/ and try WireGuard again. 3. If the error persists, open Command Prompt as administrator and run these commands one at a time, then restart Windows: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth chkdsk C: /scan If chkdsk reports errors, consider to back up your files, because the disk may be failing. If none of this helps, please send us a system report generated by Eddie right after a failed attempt, following these instructions: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do Kind regards

Hello! Yes, the previous answer includes this option. Read it. Kind regards

Hello! We have tested Bubup: the server works correctly. The problem is on Windy's side: their service refuses one of Bubup's exit IP addresses (it answers with HTTP 403 "Forbidden"), and your connections through Bubup leave from that address. Bubup's other exit addresses and the other UK servers are not affected. The solution is simple: add Bubup to the blacklist in Eddie, and you will always be connected to the other five UK servers in London and Manchester, without any delay. If you use a WireGuard configuration file instead, generate it in the Configuration Generator for a specific UK server other than Bubup. Offering several servers in each country is meant exactly for situations like this one, when a third-party service blocks a single address. Kind regards

Update: restrictions lifted Hello! The PHP project released the fixed versions earlier than scheduled, and we have installed them on every system of our infrastructure. The temporary restrictions described above have now been removed: The forum is writable again: you can post new topics and replies, edit posts, upload attachments,date your profile. The support ticket area works normally: you can open new tickets and reply to existing ones from the website. Password recovery works again. The customer API (https://airvpn.org/api/) accepts multipart/form-data requests again. If you wrote to support@airvpn.org in the meantime, there is no need to open a ticket as well: we will answer you there. If any of the functions above still fails for you, please clear your browser cache and try again; if the problem persists, open a ticket or write to support@airvpn.org. VPN connections, Eddie and the AirVPN Suite were not affected at any time. Thank you for your patience and understanding. AirVPN Staff

Hello! Two critical vulnerabilities in PHP, the language that powers our website, forum and support system, became public before an official fix was available (CVE-2026-109618 and CVE-2026-109619). They affect every PHP version in existence and allow an attacker to run code on a web server by sending a specially crafted request. The PHP project has scheduled fixed versions for today, 21 October, at 14:00 UTC, and attacks exploiting the flaws have already been reported by several security firms. The flaws are triggered by a specific kind of web request, the one browsers use to submit forms with file uploads, and they act before any application code runs. Until the fix is installed, the only effective protection is to refuse that kind of request at the web server. EDIT: this sentence was not accurate. We have done so on all our systems. What this means for you, starting now and until further notice: The forum is read-only. You can read and search everything, but you cannot post new topics or replies, edit posts, upload attachments, send private messages or change your profile. The support ticket area is read-only as well. You can read your tickets and our replies, but you cannot open a new ticket or reply to an existing one from the website. We keep answering existing tickets, and you will keep receiving email notifications for our replies. The customer API (https://airvpn.org/api/) keeps working, but it rejects requests sent as multipart/form-data: if your script posts that way, send the parameters url-encoded or as JSON instead. Support remains available by email: write to support@airvpn.org and we will assist you as usual. Everything else works normally: VPN connections, Eddie and the AirVPN Suite, login, registration, purchases and the client area. These restrictions will be lifted as soon as the official patches are available and applied to every affected component of our infrastructure. We expect most of this to happen within hours of the release; if any component takes longer, we will update this announcement. We apologize for the inconvenience and thank you for your patience. AirVPN Staff

@gtrman Hello! Thank you, the backup file shows the remaining cause. The backup was saved before step 2, so it still shows the old ALL APPLICATION PACKAGES entry (AC) with FA; that is expected. The second entry that blocks Eddie is this one: (A;OICIIO;FA;;;CO) It is the CREATOR OWNER entry, which the normal icacls output shows as CREATOR OWNER:(OI)(CI)(IO)(F). On a default installation it is stored as (A;OICIIO;GA;;;CO). GA (generic all) and FA (explicit full access) grant the same permissions in practice, but Eddie's check reads the stored value as it is: it accepts GA and rejects FA. Because icacls displays both as (F), the difference was not visible in the first output. This entry does not give anyone access to System32 itself, only to files created there later, and only for their owner. Eddie's check does not make this distinction yet, and we will report it to the developers. Please open a Command Prompt as administrator again and run the following commands. 1. Save a backup of the current permissions: icacls "%SystemRoot%\System32" /save "%USERPROFILE%\system32-acl-backup2.txt" 2. Store the CREATOR OWNER entry in its default form: icacls "%SystemRoot%\System32" /grant:r "*S-1-3-0:(OI)(CI)(IO)(GA)" S-1-3-0 is the fixed identifier of CREATOR OWNER, so the command works with any Windows language. As before, it may take a minute; wait until it reports "Successfully processed 1 files". 3. Save the new permissions to a second file, to check them:Open icacls "%SystemRoot%\System32" /save "%USERPROFILE%\system32-acl-check.txt" system32-acl-check.txt with your favorite text editor. It should contain (A;OICIIO;GA;;;CO) and (A;OICI;0x1200a9;;;AC), and no entry ending with FA;;;CO or FA;;;AC. Then start Eddie. If it still shows the same error, please post the content of system32-acl-check.txt here. To undo only today's change, you can run: icacls "%SystemRoot%" /restore "%USERPROFILE%\system32-acl-backup2.txt" Kind regards