Not connected, Your IP: 216.73.216.27
Online: 38797 users - 461033 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
-
-
-
-
- Today
-
-
-
-
- Yesterday
-
-
ANSWERED slskd port forwarding
pulmonary5024 replied to p1pb0y's topic in Troubleshooting and Problems
Could you share your docker-compose please? -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
This is very helpful, because knowing that the internal VPN IP doesn't change, not the exit IP but the internal IP, means that I can create firewall rules blocking everything but that internal IP. That can act as a secondary kill-switch. -
ANSWERED How to basic configuring Eddie + qBitorrent ?
MikeHawkener replied to Christophe95870's topic in Eddie - AirVPN Client
@Staff thanks for the explanation. that makes a lot more sense. I almost always use the default protocol which is Wireguard (for me at least) so I noticed this address was always the same (at least for the servers I've used). I've only used openvpn once or twice so far and noticed that was the only time the VPN IP was different. but probably only once since I don't remember having to change the VPN IP for openvpn (or maybe I was lucky getting the same daemon on the same server. idk) -
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
ANSWERED How to basic configuring Eddie + qBitorrent ?
Staff replied to Christophe95870's topic in Eddie - AirVPN Client
@thetechnerd @MikeHawkener Hello! Some additional related information that may be valuable for you both. When you run OpenVPN: the assigned VPN IP address depends on the daemon of the VPN server you connect to. Each one lives in a separated /24 subnet somewhere inside 10.0.0.0/10 When you run WireGuard: WireGuard lacks any DHCP feature it lives in a unique, gigantic 10.128.0.0/10 subnet throughout the whole AirVPN infrastructure the VPN IP address of each node is linked permanently to the node's key and it is unique in the whole WireGuard address space thus you will have always the same VPN IP address when you use the same key and you don't renew it, no matter which VPN server you connect to Kind regards -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
Oh really?! That's great to hear that the internal 10.x.x.x session IP is unique to the user and not the session, despite its name. Thanks @MikeHawkener! -
-
the help documentation just says "for non-interactive mode" I was wonder if it might be a feature that batch uses different servers? like rotates them every certain amount of time so you don't use the same server over a long period time ? Is there any feature in Eddie that allows this?
-
ANSWERED How to basic configuring Eddie + qBitorrent ?
MikeHawkener replied to Christophe95870's topic in Eddie - AirVPN Client
I would recommend it. I prefer the private IP address over the interface, though I'm on macos so it shows as a `utun#` number. I found that the IP has higher precedence than the specific utun. So often between boots, this IP will be the same but the `utun` number might change (e.g. `utun2` or `utun4`) depending on other services that might create their own utuns (probably not for Windows as it just shows 'Eddie'). I set both utun and IP, but if the utun is different but IP is correct, it still runs fine. Plus the private IP will (virtually) always be unique. but I think if you change LANs/networks a lot from say a laptop, then theoretically I think there is a tiny chance that LAN could also assign that local IP (I could be mistaken) also this IP only seems to change based on whether one is using wireguard or openvpn. I suspect this might be how AirVPN implements VPN servers for their clients. perhaps AirVPN usually tries to provide the same private IP to a particular customer regardless of the server as long as its the same protocol (Wireguard, openvpn). and the other protocol will try to use its own IP too. perhaps the purpose is for convenience so the customer wouldn't have to frequently change these settings in their apps etc. Just a hunch though -
But, I've just started recently...)
-
Running a tor entry/middle relay over airvpn
moejoe replied to Brisbaneforhound's topic in General & Suggestions
Is it allowed to run an exit node over air vpn ? -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
Apologies for my ignorance, but is it not advisable to bind the optional IP address to found in the client area > session IP to qbittorrent just in case? I mean, it is a local 10.x.x.x address, and doesn't seem to change i I'm connected to the same server. Am I wrong? -
- Last week
-
-
-
-
-
-
BettyIsBoop reacted to a post in a topic:
Debian Trixie: apt update fails for Eddie repo since 2026-02-01 (SHA1 rejected) ...
-
-
I just wanted to be helpful here in case anyone reading this thread is sideloading their ONN Google TV device updated to Android 14. 3.3.0 is running flawlessly and with the correct VPN server selection I never see a "spinning circle" or any hesitation at all. It fully executes my settings when I click on the Eddie app. I do NOT have it configured for device bootstrap but when I want the VPN its one click and five seconds later its rock solid good to go. I am reading about the version 4 series and may move there soon. Its tough to leave perfection, which is what 3.3.0 is for me on my end. .02
-
-
-
-
-
-
After updating any attempt to creat a vpon tunnel fails. I reinstalled Eddie, and I am out of ideas. Generated: Sat, 07 Feb 2026 19:41:09 +0000 Expiration: Mon, 09 Mar 2026 19:41:09 +0000 DELETE NOW Eddie System/Environment Report - 07.02.2026 - 19:40 UTC Eddie version: 2.24.6 Eddie OS build: linux_x64 Eddie architecture: x64 OS type: Linux OS name: Fedora Linux OS version: 43 (Workstation Edition) OS architecture: x64 Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 OpenVPN: 2.6.17 - OpenSSL 3.5.4 30 Sep 2025, LZO 2.10 (/usr/sbin/openvpn) Hummingbird: Not available WireGuard: 1.0.0 SSH: OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025 (/usr/bin/ssh) SSL: 5.75 (/usr/bin/stunnel) Profile path: /home/user/.config/eddie/default.profile Data path: /home/user/.config/eddie Application path: /usr/lib/eddie-ui Executable path: /usr/lib/eddie-ui/eddie-ui Command line arguments: (1 args) path.resources="/usr/share/eddie-ui" Network Lock Active: No Connected to VPN: No OS support IPv4: Yes OS support IPv6: Yes Detected DNS: 127.0.0.53 Test DNS IPv4: Ok Test DNS IPv6: Ok Test Ping IPv4: 48 ms Test Ping IPv6: Failed Test HTTP IPv4: Error: Fetch url error:Could not connect to server Test HTTP IPv6: Error: Fetch url error:Could not connect to server Test HTTPS: Ok ---------------------------- Important options not at defaults: login: (omissis) password: (omissis) remember: True key: (omissis) servers.allowlist: 04c8003cc011ead147020baa01cb5301b409a49bddea1291127c67e1b156b6ce proxy.mode: none ---------------------------- Logs: . 2026.02.07 20:39:25 - Eddie version: 2.24.6 / linux_x64, System: Linux, Name: Fedora Linux, Version: 43 (Workstation Edition), Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 . 2026.02.07 20:39:25 - Command line arguments (1): path.resources="/usr/share/eddie-ui" . 2026.02.07 20:39:26 - Raise system privileges . 2026.02.07 20:39:31 - Collect network information . 2026.02.07 20:39:32 - Reading options from /home/jens/.config/eddie/default.profile . 2026.02.07 20:39:34 - OpenVPN - Version: 2.6.17 - OpenSSL 3.5.4 30 Sep 2025, LZO 2.10 (/usr/sbin/openvpn) . 2026.02.07 20:39:34 - SSH - Version: OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025 (/usr/bin/ssh) . 2026.02.07 20:39:34 - SSL - Version: 5.75 (/usr/bin/stunnel) . 2026.02.07 20:39:35 - Service systemd-resolved restarted I 2026.02.07 20:39:40 - Ready . 2026.02.07 20:39:42 - Collect information about AirVPN completed I 2026.02.07 20:39:44 - Session starting. . 2026.02.07 20:39:44 - Activation of Network Lock - Linux iptables-nft I 2026.02.07 20:39:45 - Checking authorization ... ! 2026.02.07 20:39:45 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:45 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:45 - WireGuard > Setup start . 2026.02.07 20:39:45 - WireGuard > Setup complete . 2026.02.07 20:39:45 - WireGuard > Setup interface . 2026.02.07 20:39:46 - WireGuard > Received first handshake . 2026.02.07 20:39:46 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:47 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:47 - Disconnecting . 2026.02.07 20:39:47 - WireGuard > Stop request received . 2026.02.07 20:39:47 - WireGuard > Stopping . 2026.02.07 20:39:47 - WireGuard > Completed . 2026.02.07 20:39:47 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:47 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:48 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:39:48 - Service systemd-resolved restarted . 2026.02.07 20:39:48 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:39:48 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:39:48 - Collect network information . 2026.02.07 20:39:48 - Connection terminated. I 2026.02.07 20:39:51 - Checking authorization ... ! 2026.02.07 20:39:52 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:52 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:52 - WireGuard > Setup start . 2026.02.07 20:39:52 - WireGuard > Setup complete . 2026.02.07 20:39:52 - WireGuard > Setup interface . 2026.02.07 20:39:53 - WireGuard > Received first handshake . 2026.02.07 20:39:53 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:53 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:53 - Disconnecting . 2026.02.07 20:39:54 - WireGuard > Stop request received . 2026.02.07 20:39:54 - WireGuard > Stopping . 2026.02.07 20:39:54 - WireGuard > Completed . 2026.02.07 20:39:54 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:54 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:39:54 - Service systemd-resolved restarted . 2026.02.07 20:39:54 - DNS of the interface 'wwan0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:54 - Default Route of the interface 'wwan0' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:54 - DNS of the interface 'enp0s31f6' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'enp0s31f6' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:55 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:39:55 - DNS of the interface 'docker0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'docker0' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:55 - Collect network information . 2026.02.07 20:39:55 - Connection terminated. I 2026.02.07 20:39:58 - Checking authorization ... ! 2026.02.07 20:39:58 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:58 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:58 - WireGuard > Setup start . 2026.02.07 20:39:58 - WireGuard > Setup complete . 2026.02.07 20:39:58 - WireGuard > Setup interface . 2026.02.07 20:39:59 - WireGuard > Received first handshake . 2026.02.07 20:39:59 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:59 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:59 - Disconnecting . 2026.02.07 20:40:00 - WireGuard > Stop request received . 2026.02.07 20:40:00 - WireGuard > Stopping . 2026.02.07 20:40:00 - WireGuard > Completed . 2026.02.07 20:40:00 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:00 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:01 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:40:01 - Service systemd-resolved restarted . 2026.02.07 20:40:01 - DNS of the interface 'wwan0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'wwan0' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'enp0s31f6' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'enp0s31f6' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'docker0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'docker0' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - Collect network information . 2026.02.07 20:40:01 - Connection terminated. I 2026.02.07 20:40:04 - Checking authorization ... ! 2026.02.07 20:40:05 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:40:05 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:05 - WireGuard > Setup start . 2026.02.07 20:40:05 - WireGuard > Setup complete . 2026.02.07 20:40:05 - WireGuard > Setup interface ! 2026.02.07 20:40:20 - Disconnecting . 2026.02.07 20:40:21 - WireGuard > Stop request received . 2026.02.07 20:40:21 - WireGuard > Stopping . 2026.02.07 20:40:21 - WireGuard > Completed . 2026.02.07 20:40:21 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:21 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Service systemd-resolved restarted . 2026.02.07 20:40:21 - Collect network information . 2026.02.07 20:40:22 - Connection terminated. I 2026.02.07 20:40:22 - Cancel requested. . 2026.02.07 20:40:22 - Deactivation of Network Lock ! 2026.02.07 20:40:22 - Session terminated. ---------------------------- Network Info: { "routes": [ { "destination": "0.0.0.0\/0", "gateway": "192.168.2.1", "interface": "wlp0s20f3", "metric": "600", "proto": "dhcp", "src": "192.168.2.45" }, { "destination": "172.17.0.0\/16", "interface": "docker0", "proto": "kernel", "scope": "link", "src": "172.17.0.1" }, { "destination": "192.168.2.0\/24", "interface": "wlp0s20f3", "metric": "600", "proto": "kernel", "scope": "link", "src": "192.168.2.45" }, { "destination": "fe80::\/64", "interface": "wlp0s20f3", "metric": "1024", "pref": "medium", "proto": "kernel" } ], "ipv4-default-gateway": "192.168.2.1", "ipv4-default-interface": "wlp0s20f3", "interfaces": [ { "friendly": "lo", "id": "lo", "name": "lo", "description": "lo", "type": "Loopback", "status": "Unknown", "bytes_received": "320867", "bytes_sent": "320867", "support_ipv4": true, "support_ipv6": true, "ips": [ "127.0.0.1", "::1" ], "bind": true }, { "friendly": "wwan0", "id": "wwan0", "name": "wwan0", "description": "wwan0", "type": "0", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [], "bind": false }, { "friendly": "enp0s31f6", "id": "enp0s31f6", "name": "enp0s31f6", "description": "enp0s31f6", "type": "Ethernet", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [], "bind": false }, { "friendly": "wlp0s20f3", "id": "wlp0s20f3", "name": "wlp0s20f3", "description": "wlp0s20f3", "type": "Wireless80211", "status": "Up", "bytes_received": "2278710", "bytes_sent": "512860", "support_ipv4": true, "support_ipv6": true, "ips": [ "192.168.2.45", "fe80::91ee:1179:5e88:ccc4" ], "bind": true }, { "friendly": "docker0", "id": "docker0", "name": "docker0", "description": "docker0", "type": "Ethernet", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [ "172.17.0.1" ], "bind": true } ] } ---------------------------- ip addr show: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wwan0: <POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/none 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 8c:8c:aa:a6:81:3f brd ff:ff:ff:ff:ff:ff altname enx8c8caaa6813f 4: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 22:99:d5:df:3b:3e brd ff:ff:ff:ff:ff:ff permaddr e8:84:a5:b0:c4:17 altname wlxe884a5b0c417 inet 192.168.2.45/24 brd 192.168.2.255 scope global dynamic noprefixroute wlp0s20f3 valid_lft 43092sec preferred_lft 43092sec inet6 fe80::91ee:1179:5e88:ccc4/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 66:7b:0a:fa:1d:aa brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever ---------------------------- ip link show: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wwan0: <POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/none 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 8c:8c:aa:a6:81:3f brd ff:ff:ff:ff:ff:ff altname enx8c8caaa6813f 4: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000 link/ether 22:99:d5:df:3b:3e brd ff:ff:ff:ff:ff:ff permaddr e8:84:a5:b0:c4:17 altname wlxe884a5b0c417 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 66:7b:0a:fa:1d:aa brd ff:ff:ff:ff:ff:ff
-
-
-
-
The last version that worked without being sluggish or suffered slow GUI was 2.22.2 but that had a problem in the with Eddie window open, the kde application launcher would not stay open at the same time. I have just initiated Eddie to run through terminal so I could see it load, this was in the first line or the output: $ eddie-ui (eddie-ui:26517): Gtk-WARNING **: 10:32:05.005: Unable to locate theme engine in module_path: "adwaita", . 2026.02.07 10:32:05 - Eddie version: 2.24.6 / linux_x64, System: Linux, Name: Ubuntu 24.04.3 LTS, Version: 24.04.3 LTS (Noble Numbat), Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 This is the Linux version I use: Kubuntu Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.12 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-90-generic (64-bit) Graphics Platform: X11
-
WireGuard>Handshake Timeout Error
Tech Jedi Alex replied to ColeCrackles's topic in Troubleshooting and Problems
Close Eddie, reopen and try a connection, then provide a system report. It's interesting that you noticed all the troubleshooting attempts, but not the very first thing that is usually asked: The request for more information.. -
Eddie Desktop - APT Repository Signing Key Update
qitorin replied to Staff's topic in Eddie - AirVPN Client
Thank you for the update - is there going to be new version of the Eddie any time soon? -
I also find the Eddie ui a bit sluggish - I wonder when there will be a updated version or a different client altogether. It is a shame because Windows Eddie is so smooth and fast overall and Android client is just superb, perhaps the Linux-desktop client is not a high priority any more.
-
Hello! I recently purchased AirVPN for the first time [Windows 11, installed using the x64 installer], and I'm not able to connect to any servers due to a reoccuring 'WireGuard>Handshake timeout' error. I've tried restarting my PC, updating drivers, connecting to different servers and countries (U.S. Canada, the Netherlands) I deleted another vpn program I had (Radmin VPN), which did nothing. I tried changing the WireGuard settings (First to 1280, then Omit). This did nothing either. I tried installing another VPN, Proton, and I was able to connect with that service. However, I'd prefer AirVPN as I already paid for it and Proton's free plan blocks certain features I'm looking for. I'm not sure what troubleshooting steps to try next--I've looked at other forum posts and tried what I could. The only thing I haven't tried is using an Ethernet cord...Because I don't own one. Any help is much appreciated!
-
Most of the encryption algorithms are handled by hardware, using CPU extensions. But packet switching still requires vanilla CPU power. So yeah, CPU horsepower still required but not as much as the days of old. Also the newer, more efficient ciphers help a lot as well.
-
Can confirm the same. Sometimes the download speeds also drop off the cliff.
-
-
I'd like to upvote this but also expand upon, a little bit: Rerouting only servers for geolocation workaround sound like a very good compromise vs full-blown servers. So it would be nice to see rerouting servers in "popular" locations that a full server deployment is not justified. Usecases have already been mentioned (IPTV, government sites, banking etc). Another option might be that geoblocking could be worked around via DNS? I have seen some DNS-only services accomplishing the above. Just not sure how
-
With 300+ users you would need some beefy CPUs in the server. I would guess that is the bottleneck, not the actual connection. VPNs are encrypted and require the processing power to handle the number of users connected. Not sure what their server specs actually are, but would be curious to know.
-
Alruba is usually a fast server for me, but recently something has changed. I still get fast download speeds but the upload is barely 10Mbps in speedtest.net and this is noticeable elsewhere too. Alruba's load has often been almost 100% but now it is only 15-25% at the time of writing, so maybe I'm not the only one having issues.
-
Pages blocked? Here's the solution. List
Tech Jedi Alex replied to StylishSpecter's topic in Blocked websites warning
First of all, open your own thread. -
Eddie Desktop - APT Repository Signing Key Update
Dje_ replied to Staff's topic in Eddie - AirVPN Client
Thanks a lot -
ANSWERED Malwarebytes blocks ip 213.152.187.210
Staff replied to Zack's topic in Troubleshooting and Problems
Hello! The "range" is specified by mask /32, so it's this single unique address. Yes, it's plausible that some past event flagged the IP address. We don't know the internals of Tailscale but definitely this behavior should be investigated. Why an attempted connection to this specific IP address and why this port? Kind regards
