ANSWERED eddie - there is no available or enabled network lock mode

[Puontyxx 0]

I am getting the above error when running Eddie for the first time after signing up to AirVPN after a recommendation 

I am using PopOS 

I installed via terminal following the instructions but got terminal errors when trying to login 

I then downloaded and installed the ubuntu image and Eddie loads fine. However after logging in and trying to connect to a server I get this issue:

there is now available or enabled network lock mode

I have read about network lock and googled the error. The most relevant cases I could find was about an old WindowsXP user and a guy who said he didn't have 'iptables' installed as part of linux. 

However, I have tried running without 'network lock' enabled in the settings. I have restarted the app and tried to connect to a server again, and it just fails to connect to any server after attempting a connection. 

I gave up after trying to connect to 20 different random servers.

Please help. Thank you

[Tech Jedi Alex 1489]

On 7/6/2025 at 9:07 PM, Puontyxx said:

I installed via terminal following the instructions but got terminal errors when trying to login 

What instructions, and what kind of errors?
 

On 7/6/2025 at 9:07 PM, Puontyxx said:

However, I have tried running without 'network lock' enabled in the settings. I have restarted the app and tried to connect to a server again, and it just fails to connect to any server after attempting a connection. 

What's the error here?

Please try a connection with Eddie and provide a system report.
 .

[Puontyxx 0]

12 hours ago, OpenSourcerer said:

What instructions, and what kind of errors?
 

The official ones on the airvpn website 

I can't remember the errors now as I have closed terminal and it was a couple of days ago, but from memory something about missing files 
 

12 hours ago, OpenSourcerer said:

Please try a connection with Eddie and provide a system report.

Please see attached - this is with network lock disabled and then a restart of the program. I would obviously like to get working with 'network lock', but I guess one thing at a time.

Please help. 

[Puontyxx 0]

Apologies I sent a screenshot of the errors and didn't upload a full report, which is now shown below:

https://eddie.website/report/74cb5d33/

[Puontyxx 0]

Any ideas people I still can't get this working, with or without network lock!

Thank you

[Puontyxx 0]

I have actually now resolved the issue using AI. I did not have wireguard installed properly and also had to force load it on startup. now it appears to be working!

[Tech Jedi Alex 1489]

9 hours ago, Puontyxx said:

I have actually now resolved the issue using AI. I did not have wireguard installed properly and also had to force load it on startup. now it appears to be working!

Always write what you did. It helps the future.  

[Puontyxx 0]

I just needed to download and install wireguard packages separately then run a script to make sure it loads wireguard upon boot each time. For some reason they didnt ship with PopOS

[Tech Jedi Alex 1489]

2 hours ago, Puontyxx said:

then run a script to make sure it loads wireguard upon boot each time

What is this script, and where do people find it?

[Puontyxx 0]

Venice Reasoning

•

13.49s

w/ web search

Thought Process

 

Based on the provided search results and your situation, here's an analysis of why you might be unable to connect to the AirVPN server via Eddie on PopOS:

Likely Cause & Solution

The issue appears related to file ownership permissions for WireGuard components, as seen in a similar macOS case

¹

The error described there indicates Eddie's WireGuard executable wasn't owned by root, causing immediate disconnections. For Linux, this could manifest similarly if critical Eddie files (e.g., wg binary or configuration files) lack proper ownership/permissions.

 

Steps to resolve:

1. Check File Ownership
   Verify ownership of Eddie's WireGuard-related files. Run:

   bash

    

sudo ls -l /path/to/eddie/appdir/wireguard-binaries/*  

Replace /path/to/eddie/ with Eddie's actual installation directory (commonly /opt/Eddie or /usr/share/Eddie). If files aren’t owned by root, fix with:

bash

 

• sudo chown root:root /path/to/file  

• Ensure WireGuard Dependencies Are Met
  PopOS may require manual installation of WireGuard kernel modules or userspace tools. Install them via:

  bash

   

2. sudo apt update && sudo apt install wireguard  

3. Firewall/Network Conflicts
   Temporarily disable firewall rules (e.g., ufw) or check for conflicts with other network tools (e.g., iptables, third-party VPNs).

4. Reinstall Eddie
   Corrupted installation may cause permission errors. Uninstall and reinstall Eddie from AirVPN’s official repository.

Additional Notes

• Your log file (https://eddie.website/report/74cb5d33/) might contain specific errors (e.g., "Not owned by root" messages) that align with the macOS case. If the log shows similar ownership issues, apply the chown fix above.
• If WireGuard isn’t the issue, check kernel compatibility or try connecting via OpenVPN protocol instead of WireGuard in Eddie’s settings.

Let me know if you need help locating Eddie’s file paths or interpreting your log.

1 Citation