Search the Community

I've had an extremely stable and fast setup for some time, but after a middle-of-the-night power outage, I can no longer connect, and I can't tell what has triggered the problem; my configuration hasn't changed, and my IP address(es) haven't changed. I am not that sophisticated about all this stuff, so forgive me if I'm giving too much information, but since I'm not sure where the problem is I'd rather give more rather than less info. I'm using AirVPN _only_ for torrenting. For the latter, I'm using transmission with gluetun, both running in Docker containers on the same host. The Transmission network config is 'network_mode: "service:gluetun"'. The relevant (I think) config for gluetun is: environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=[blah]= - WIREGUARD_PRESHARED_KEY=[blah]= - WIREGUARD_ADDRESSES={my home IP address} - FIREWALL_VPN_INPUT_PORTS=54321 - SERVER_COUNTRIES=United States ports: - "0.0.0.0:9091:9091/tcp" # transmission - 54321:54321/tcp # transmission - 54321:54321/udp # transmission (The port is not actually "54321", but it's in a similar range, and I"m using that same port number throughout this explanation.) I have not changed this configuration. Both transmission and gluetun are running, as are other services on the Docker host, that are reachable as expected. My router runs pfSense. I have a firewall rule that forwards any WAN traffic on port 54321 to {IP address of the Docker host}. I also have a port forwarding entry that has both NAT port and destination port of 54321 with a NAT IP address of {IP of Docker host} and a destination address of the WAN. I have restarted the firewall to ensure that these is loaded. Meanwhile, on AirVPN Client Area, under "Forwarded Ports", I have a forwarded port of 54321 pointing to a local port of 54321. (This is my only forwarded port.) When I click "Test Open", it opens up a window with a bunch of servers on it; all of them spin for a while before returning "Connection timed out (110)". In Transmission, under Remote Preferences -> Connections, I have "Peer port" set to 54321. When I click Port test -> "Test", it pauses for a while before returning "Couldn't test port: No Response (0)". I also note that in the AirVPN Client Area, it reports that "There are 16 sessions active on this account. Max 5 concurrent sessions allowed."; I have no idea what these sessions are, and it's not clear to me how I can shut them down. I don't have any other devices or services that use AirVPN. I have confirmed that after the power outage, my home IP address is still indeed the one configured in the gluetun config. I have also used canyouseeme.org to check the port; it confirms "Success: I can see your service on {my home IP address} on port (54321) Your ISP is not blocking port 54321". I don't know what else to try, or where else to look; I've occasionally had issues after unplanned restarts, but they always resolve themselves quickly, or they have obvious causes (e.g. my ISP gives me a new IP address after the modem resets) that I can fix. I'd be grateful for any suggestions! Thank you.

Hello, I'm reaching out to the forum because I recently subscribed to the service, and I'm having issues getting Transmission to work through the VPN. I'm using the WireGuard protocol on a Debian PC (headless without GUI). The WireGuard interface (wg0) is working fine; I can ping external addresses through it, use curl, and perform speed tests : The transmission-daemon also works perfectly when not going through the WireGuard interface but using my physical interface eth0. When I bind Transmission to the wg0 interface (specifying its IP in "bind-address-ipv4"), no traffic goes through the VPN. The trackers are unreachable, and the error "announce error: could not connect to tracker" appears. Running a netstat, I can see that Transmission is trying to connect to the tracker using various ports (why ?) through the WireGuard interface but never receives any traffic in return (SYN_SENT): However, these addresses are pingable through the wg0 interface: I've tried approaching the problem from different angles, and after several hours without any solution, I'd like to know if any of you have encountered a similar issue? (I should mention that my firewall is completely disabled for the tests). Thank you !

I am trying to setup AirVPN with Transmission on macOS Sierra. What do I need to do to set this up correctly? 1 - Do I need to setup a Kill Switch? If so, how do you do this? 2 - Do I need to do some type of port forwarding inside of Transmission? Or do I need to do something here? - https://airvpn.org/ports thanks!

Hi there! I'm new to AirVPN, and I've been using it at college on my Mac for the last month or so with great success. I'm trying to torrent with the Transmission client, and it's not working. According to Preferences, the default Listening Port (51413) is closed. My understanding after a little research is that colleges keep their networks locked pretty tight and tend to close off all unnecessary ports (please correct me if I'm wrong), so it would only make sense that after scanning all of the ports on the network though a web service, there isn't a single one open (I only scanned up through 2048). However, when I tried rescanning connected to the VPN, ports 88 and 89 were open (again, only ones I saw below 2048). I briefly tried port 88 in Transmission, which verified it was open, and did begin receiving the torrent I was trying. My question is this: is it safe to use either port 88 or 89 in this manner?

Hi all. I just signed up for service and am a newbie when it comes to this stuff. I am using Debian jessie, and have successfully installed the AirVPN client. How do I set up my torrent client (Transmission) and my browser to utilize AirVPN's services? Thanks!

Hi there, I am fairly new to Linux and also to AirVPN. I am using the AirVPN client on 64 bit Linux Mate, running Transmission on my machine trying to set up remote access so I can view the web interface remotely. I have a DNS running on my Raspberry Pi so I am attempting to use my domain (for example 2Girls1CPU.mooo.com:9091) to access the web UI. I have tested the DNS, through port 22 to SSH into my raspberry pi to confirm that it is working. Here is what I have tried: Initially I set up remote access in Transmission. I had the port as 9091, with authentication and no whitelist of IP addresses. Then I went into AirVPN client area and set up a port forwarding rule. Obviously 9091 was taken, so I just created a random port, forwarded through TCP (I've tried UDP, as well as both TCP and UDP). Then I took that random port, say 27364 and entered it into the remote access settings in Transmission. I also went into my port forwarding rules in my router and added a rule to forward 27364 to my Laptop running AirVPN and Transmission (say 192.168.1.43). External and internal port both the same obviously. Now with this setup, I would assume when I try to access port 27364 (with 2Girls1CPU.mooo.com:27364) - my VPN would forward that to my router port 27364, which would then forward to 192.168.1.43:27364. I may be completely wrong as I do not have a solid understanding of networking and port forwarding, but this setup did not work. One thing that confused me was under the port forwarding rules on AirVPN client area, it says "Forwarded to 10.x.x.x". Why is this being forwarded to an IP with a 10. ip range? Should it not be forwarded to my internal IP? Or how exactly does that work? I'm probably missing something here, but I just can't work it out. I'm not sure how the port forwarding within AirVPN works. If anyone could give me some insight it would be greatly appreciated. One more thing I am wondering - how safe is it to have a port forwarded like I am attempting while using AirVPN? Is there any potential for leaks? Thanks! -2Girls1CPU

Hi guys! So I am attempting to setup my Transmission bittorrent client with Transdrone (Transdroid) app on Android. I want to be able to use this android remote app to connect to my desktop (where Transmission is running) while I am connected to this VPN. So I: 1) Connected to a server (say Server A). 2) Configured port forwarding on AirVPN's site (AirVPN > Client Area > Forwarded ports). Let's say I forwarded port 7712 and 7713. 3) Logged into Transmission and set port 7712 as the Incoming port (Transmission > Preferences > Network) and made sure 'Pick a random port at startup' was unchecked. 4) Allowed remote access (HTTP) from port 7713 and configured username/password authentication. Made sure 'Only allow these IP addresses' was unchecked. 5) Then set my firewall to allow incoming connections from port 7712 and 7713 (TCP). * I DID NOT log into my router and configure port forwarding for these ports (or any for that matter). When I hit the 'Test Port' button (Transmission > Network) to test port 7712, it says 'Port is OPEN'. Cool. ----- So what is my post about? Well there are some instructions on this page that confuse the heck outta me: https://airvpn.org/faq/p2p/ I do not understand what is being communicated here... "If you forward a port for a p2p torrent client, do NOT remap it to a different local port and make sure that the torrent client port matches the remotely forwarded port number" - What is meant by "do not remap it to a different local port"? Am I supposed to log into my router and setup port forwarding for port 7712 & 7713? "do NOT forward on your router the same ports you use on your Bittorrent or eMule client (or any other listening service) while connected to the VPN" - Doesn't this contradict the previous instruction? What is the correct way to configure port forwarding so that my P2P client will work with my android remote app? (and seed)