Jump to content
Not connected, Your IP: 3.129.63.214

Recommended Posts

I have done quite a bit of searching but unfortunately most of these issues end up being related to Windows firewalls or some other thing. I am running everything on a headless linux server from the command line, and mostly using docker containers to manage these processes.

I have generated a wireguard config file, and can successfully connect to the server, however, the open port I was assigned is consistently closed. Transmission's internal port tester shows the port as closed, and using the tester on the website results in a "Connection refused" error.

  • The service doing the listening is running when I do these tests.
  • Transmission is configured to use the forwarded port.
  • I restarted the connection after forwarding the port.
  • Turning off my firewall (UFW) doesn't make a difference.
  • This same setup worked flawlessly with mullvad (RIP)

Any other suggestions or ideas? I have two more days on my subscription to sort this out before I have to decide to keep the service or look elsewhere.

Share this post


Link to post
21 minutes ago, ohshitgorillas said:

Any other suggestions or ideas? I have two more days on my subscription to sort this out before I have to decide to keep the service or look elsewhere.


Please also open a ticket with professional support. You get an answer within hours.

NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT.

LZ1's New User Guide to AirVPN « Plenty of stuff for advanced users, too!

Want to contact me directly? All relevant methods are on my About me page.

Share this post


Link to post

I have, but I figured it can't hurt to reach out here, too. If I find a solution, I'll post it so that maybe someone else in a similar situation might get the help they need.

I'm looking at the documentation and wondering if I need something similar to the iptables rules listed here enforced within the container? It's not DD-WRT, but it is a manual connection so it's similar.

Share this post


Link to post

I was able to resolve the problem by using "network_mode: service:airvpn" under the transmission settings in docker-compose.yaml. Previously I was using a bridged network to connect the two, but apparently it needs to share the entire network space with the VPN container.

Share this post


Link to post
Guest
This topic is now closed to further replies.

×
×
  • Create New...