Not connected, Your IP: 216.73.216.33
Online: 32313 users - 425113 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
-
-
-
-
-
-
-
-
- Today
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
Hello! The ZeroTier network interface could be the cause of the problem. Please try to disable the interface and make sure that no ZeroTier VPN etc. related software is running, then try again and check whether the problem gets resolved or not. Kind regards -
Hi folks, I've been using Air for a good fews years now on my 2013 iMac running High Sierra, and as I'm about to set up a new M4 Mac Mini with the latest OS I'd like to get Air installed as soon as possible. When I originally set it up on my old Mac, I did so through a combination of reading threads on the forum here and getting help from some other members who offered some advice on how to proceed, and also some trial and error as I went along. Obviously, both Air and the new Mac are more sophisticated now, and I'm reading as much as I can about things like Wireguard, but I was hoping some users with a similar set-up at home might be able to offer me some helpful tips before I start the process. I have been looking through the threads already, but I haven't found one just for a new Mac, so if there is one perhaps someone could give me a link. Anyway, I'm looking forward to many more years using AirVPN. Thanks.
-
-
At this point, as an alternative, perhaps it may be worth for you to look for hardware (if you use cable) solutions like: amazon.com / Internet-CUT-OFF-Kill-Switch/dp/B00RQVFHZ4/ (remove spaces)
-
Multiple. You run multiple docker containers that each provides proxy connectivity to one VPN server. You switch, in the browser, by changing the port number. Port 3128 connects to, say, a UK VPN server. Port 3129 connects to a VPN server in Asia. 3130 connects you to Canada, etc. - Yesterday
-
Logs below Eddie_20250712_170109.txt -
-
-
ANSWERED Port Forwarding is not working
@Yang replied to @Yang's topic in Troubleshooting and Problems
Thank you very much. Port forwarding has resumed normal operation again. It was an issue with the Windows 11 firewall. Although the firewall had previously been turned off, at some point it was automatically re-enabled—probably due to a Windows 11 policy. Once I disabled it again, everything worked fine. Thank you. I really appreciate your help. -
Permanent Kill Switch for Eddie Client
Daniel2025 replied to Daniel2025's topic in Eddie - AirVPN Client
Hello, I’d like to suggest a feature for the Eddie client: a true permanent network lock (kill switch) on Windows that ensures the system can never come online with its real IP, not even briefly during boot, crashes, or if the Eddie client is closed manually. I’m the original poster of this thread, and I’ve spent quite a bit of time researching this topic. I now understand the reasoning behind Eddie’s current behavior: the firewall rules only apply while the client is running, to avoid locking users out or breaking system connectivity. That makes sense — but it still leaves a privacy gap that many users would prefer to close permanently. I’ve looked into solutions like using Windows Filtering Platform (WFP) rules or manual firewall configurations, but I wasn't able to create a setup that’s both secure and reliable. I'm not a beginner, but I'm also not confident enough to enforce such permanent restrictions without risking accidental lockouts or leaks due to misconfiguration. Many users – especially those who value privacy – would greatly benefit from a built-in, persistent kill switch, similar to how Mullvad has implemented it in their Windows client. It's extremely effective and survives reboots or unexpected crashes. I’d love to see something similar in AirVPN, which I consider superior in nearly every other regard: server quality, privacy philosophy and transparency. To show how much I care about this feature, I’m even willing to donate €100 toward its development. I know it's not a large sum, but I believe others would support it too. This kind of functionality would make AirVPN even more attractive to security-conscious users on Windows. Is there any chance this could be added in a future version of Eddie? Even an optional advanced setting or a supported script/tool would be a great step forward. Thank you for your continued excellent work and for your strong commitment to online privacy. Best regards, -
ANSWERED Port Forwarding is not working
OpenSourcerer replied to @Yang's topic in Troubleshooting and Problems
I see. Have a look at these.. -
ANSWERED Port Forwarding is not working
@Yang replied to @Yang's topic in Troubleshooting and Problems
eMule. I’ve already made sure that the eMule listening port matches the VPN’s forwarded port. Yet I still get a Low ID, whereas before I used to get a High ID. That shouldn’t happen—ideally, once the VPN tunnel is successfully established and the server forwards the port, the client should be able to communicate over that port through a properly open public network. The ISP can’t possibly intercept a port’s communication through the VPN tunnel, right? -
ANSWERED Port Forwarding is not working
OpenSourcerer replied to @Yang's topic in Troubleshooting and Problems
Then it's probably not listening on the VPN interface. What program are you trying to reach via VPN, anyway? -
ANSWERED Port Forwarding is not working
@Yang replied to @Yang's topic in Troubleshooting and Problems
Of course, none of my applications can connect through the forwarded port, and changing the port doesn’t solve the problem either. -
Erm, but through all this you're only connected to one VPN server? Or to five and you switch in the browser?
-
eddie - there is no available or enabled network lock mode
Puontyxx replied to Puontyxx's topic in Eddie - AirVPN Client
Any ideas people I still can't get this working, with or without network lock! Thank you -
ANSWERED Port Forwarding is not working
OpenSourcerer replied to @Yang's topic in Troubleshooting and Problems
What are you trying to reach via VPN? Whatever the program is, it must run, of course. -
I'm using the FoxyProxy extension in Firefox, which lets me use multiple proxies. I just set up a stack in docker utilizing wireguard to connect to the VPN, and a pair of squid containers (because the networking is weird) to act as a proxy. Because the configs are ... complex, I'm using saltstack to automate the management. Each proxy is defined in a YAML file, and the automation loops through them to render the appropriate configs as well as the docker-compose. The keys in the configs are stored securely in salt-pillar using salt-gpg. I realize this is a pretty obscure use-case, but I like being able to switch my web browser to exit in Canada or the UK, or even California on a whim. I DO need to add validation that checks to make sure that there aren't more than 5 active proxies in the yaml file, though.
-
-
[LINUX] Network Lock and firewalld
rickytan78 replied to Staff's topic in Troubleshooting and Problems
Been running for a year before I saw this. Might be worth mentioning in the linux install instructions. - Last week
-
ANSWERED Port Forwarding is not working
@Yang replied to @Yang's topic in Troubleshooting and Problems
There’s nothing listening on the port? I’m using Windows 11, the network firewall is turned off. I’m currently using Eddie version 2.24.6. Is port listening managed by Eddie? Is it an issue with my computer system? I switched to using Eddie on Android and still got connection refused. What should I do? -
-
-
-
-
Gluetun port forwarding not seeming to work
Print8956 posted a topic in Troubleshooting and Problems
Hi, I've read I think all posts in this forum related to this problem and whatever I try, I do not get it to work. ChatGPT and Gemeni were also useless in this scenario unfortunately, so I hope for someone to spot the error. The situation: - I have a port forwarded in the client area - Connection is made successfully (confirmed in AirVPN portal) - Gluetun is configured to accept this port in the firewall (confirmed in the logs) - Port check on the AirVPN website comes back negative (Connection refused, hinting at issues with the gluetun config) - QBittorrent download port correctly configured but shows red connection on 'tun0' interface, any interface shows yellow (firewalled). Set to listen to IP4 addresses - IP is verified to come through VPN in all containers I expect them to, prowlarr has no issues with traffic for example I don't understand what I am missing. Would someone be able to spot the issue? Please let me know if you require more details! docker-compose.yaml networks: arr-network: driver: bridge ipam: driver: default config: - subnet: "172.30.172.0/24" enable_ipv6: false services: gluetun: image: qmcgaw/gluetun:latest container_name: gluetun cap_add: - NET_ADMIN - SYS_MODULE devices: - /dev/net/tun:/dev/net/tun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PUBLIC_KEY=$airvpn_wg_pub_key - WIREGUARD_PRIVATE_KEY=$airvpn_wg_priv_key - WIREGUARD_PRESHARED_KEY=$airvpn_wg_preshared_key - WIREGUARD_ADDRESSES=$airvpn_wg_addresses - SERVER_COUNTRIES=Sweden - FIREWALL_VPN_INPUT_PORTS=49192 - FIREWALL_OUTBOUND_SUBNETS=192.168.2.0/24,172.30.172.0/24 - DNS_ADDRESS=$airvpn_dns - TZ=$timezone ports: - 9080:9080 # qbittorrent web GUI, port number can be changed BUT it must match WEBUI_PORT in qbittorrent service environment - 9696:9696 - 49192:49192 # Also add to TORRENTING_PORT in qbittorrent - 49192:49192/udp networks: - arr-network volumes: - gluetun_config:/gluetun restart: unless-stopped qbittorrent: image: ghcr.io/linuxserver/qbittorrent:5.1.0 container_name: qbittorrent cap_add: - NET_ADMIN network_mode: service:gluetun depends_on: gluetun: condition: service_started environment: - PUID=1000 - PGID=997 - TZ=$timezone - WEBUI_PORT=9080 - DOCKER_MODS=arafatamim/linuxserver-io-mod-vuetorrent - TORRENTING_PORT=49192 volumes: - qbit_config:/config - media:/media restart: unless-stopped prowlarr: image: lscr.io/linuxserver/prowlarr:latest container_name: prowlarr cap_add: - NET_ADMIN network_mode: service:gluetun depends_on: gluetun: condition: service_started environment: - PUID=1000 - PGID=1000 - TZ=$timezone volumes: - prowlarr_config:/config restart: unless-stopped sonarr: image: ghcr.io/linuxserver/sonarr container_name: sonarr cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=997 - TZ=$timezone volumes: - sonarr_config:/config - media:/media ports: - 8989:8989 networks: - arr-network restart: unless-stopped radarr: image: ghcr.io/linuxserver/radarr container_name: radarr cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=997 - TZ=$timezone volumes: - radarr_config:/config - media:/media ports: - 7878:7878 networks: - arr-network restart: unless-stopped bazarr: image: lscr.io/linuxserver/bazarr container_name: bazarr cap_add: - NET_ADMIN environment: - PUID=1000 - PGID=1000 - TZ=$timezone volumes: - bazarr_config:/config - media:/media ports: - 6767:6767 networks: - arr-network restart: unless-stopped volumes: gluetun_config: qbit_config: prowlarr_config: sonarr_config: radarr_config: bazarr_config: media: driver_opts: type: cifs o: username=$nasUser,password=$nasPass,file_mode=0777,dir_mode=0777,noperm device: $nasMediaPath -
ANSWERED Port Forwarding is not working
OpenSourcerer replied to @Yang's topic in Troubleshooting and Problems
Connection refused means it was able to connect but on your host nothing is listening on port 18992. -
-
-
-
Just tried AWG through Beeline Moscow, everything works without any issues. Also works on MGTS and MTS Moscow.
-
ANSWERED Port Forwarding is not working
@Yang replied to @Yang's topic in Troubleshooting and Problems
Is it my ISP blocking it? It used to work fine before, but it recently stopped working. -
Hello, I can connect to the server, but port forwarding is not working. A port test shows "connection refused." I need help.
-
AmneziaWG to AirVPN no longer works on Beeline, I cannot find any settings which would work. Obviously they learned how to block it. That means other ISPs may follow soon. May be if AirVPN used AmneziaWG on the server side we could try the fake packet parameters (S1 and S2) but as it's not gonna happen we're out of luck. We're pushed more and more to buy and set up our own servers with XRay/SingBox just to use the full Internet, or use the shady services offered in Telegram. It's no longer a privacy question, it's for the sakes of information access. As long as it works we want it because we need it.
-
Words to live by! 🤣👍👍
-
-
You'll never have problems with TCP only, though, hence the recommendation. It's like a high risk, high reward thing: By setting mixed mode, you may or may not see better throughput. You may also induce constipation on the line, one that no laxative will ever cure.
