Sevenz 3 Posted ... (edited) I did search on "error 110", "port forward", and "Connection Timed Out" but nothing matches my problem. I'm not sure whether to post here or MerlinWRT forum but I'll just post on both. Little background on my network. I use MerlinWRT (Asus Router) plugged after some ZTE router (the one ISP gives). ISP gives me private IP, which in no way I can open any port, contacted them and I have to change to business plan for me to get a public IP. I have dealt with port forwarding when I signed up with AirVPN, everything worked fine but now I hit the wall for some reason. I`m running a server on Unraid and made 3 dockers for Nextcloud, Plex and Transmission. A few days ago everything is working fine, Nextcloud can be accessed from port 61466 (local 443), I can stream Plex (albeit slow, but good enough to watch from work) with port 61477 (local 32400), and transmission with port 9958 (local 9958). Now all that is working is port 9958 for torrent (green circle), Nextcloud and Plex get Error 110: Connection Timed Out when I press the check button (Dark grey circle). I haven't changed my prerouting/port forwarding much but I will list it below. #!/bin/sh iptables -I FORWARD -i br0 -o tun12 -j ACCEPT iptables -I FORWARD -i tun12 -o br0 -j ACCEPT iptables -I FORWARD -i br0 -o vlan1 -j DROP iptables -I INPUT -i tun12 -j REJECT iptables -t nat -A POSTROUTING -o tun12 -j MASQUERADE iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --match multiport --dports 8160,9958,24253,41588,61466,61477 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --match multiport --dports 8160,9958,24253,41588,61466,61477 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --match multiport --dports 8160,9958,24253,41588,61466,61477 -j DNAT --to-destination 192.168.2.140 iptables -t nat -I PREROUTING -i tun12 -p udp --match multiport --dports 8160,9958,24253,41588,61466,61477 -j DNAT --to-destination 192.168.2.140 This IP table from some other thread in Air helped me in the past. So I'm wondering why I get error 110: Connection Timed Out. Everything was working well until a few days ago. I checked that all 3 programs are running properly, I can access all three with local IP 192.168.2.140. In the Plex browser, I get Your server is signed in to Plex, but is not reachable from outside your network. Learn more Tip: It looks like your server may be connected to the internet through multiple routers or other network devices. Try connecting it directly to your primary device, or visit our support site for more information about troubleshooting this "Double-NAT" scenario. Learn more So yeah, I'm wondering if I'm actually under Double-NAT issue. But if I do, I shouldn't be able to connect to Transmission from outside, 2 ports (61466 & 61477) don't work, 1 port (9958) works. If my server is connected to VPN, shouldn't the route be like SERVER > VPN > INTERNET? Anyway, I tried to google and tried various methods but to no avail. Any help would greatly appreciated. Thanks! EDIT: I haven't tried several stuff like factory reset my router, and some others I can think of. I will post result when I've done those. Edited ... by sevenz Quote Share this post Link to post
Sevenz 3 Posted ... Fixed this after 2 days of restless nights. I will post for the sake of some others if they ever had trouble with this. Up until several days ago. I had working port forwards on my network. Originally I had port 61477 with local port 32400 (for plex) and 61466 with local port 443 (for owncloud). I used merlinwrt RT-87N with setting IP tables as follows. iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --match multiport --dports 61466,61477 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --match multiport --dports 61466,61477 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --match multiport --dports 61466,61477 -j DNAT --to-destination 192.168.2.140 iptables -t nat -I PREROUTING -i tun12 -p udp --match multiport --dports 61466,61477 -j DNAT --to-destination 192.168.2.140 Suddenly it breaks on me with no knowledge of what happens. So I tinkered with the router, IPtables, trials and errors, only to figure out that I need to forward it properly. End result, this is what I did AirVPN Port and Local port I made the same, 61466 and 61466, 61477 and 61477. Changed the IPtables in for the router manually via ssh with this code iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 9958 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 9958 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 9958 -j DNAT --to-destination 192.168.2.140 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 9958 -j DNAT --to-destination 192.168.2.140 iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 61477 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 61477 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 61477 -j DNAT --to-destination 192.168.2.140:32400 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 61477 -j DNAT --to-destination 192.168.2.140:32400 iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 61466 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 61466 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 61466 -j DNAT --to-destination 192.168.2.140:443 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 61466 -j DNAT --to-destination 192.168.2.140:443 On the prerouting IPtables I added port number which is to point to local port, so it becomes like this. Anyway, I don't know if this is correct, but this works for me. All ports opened and I can access plex and nextcloud mainly from work. Hopefully this will help some others who own Asus router and port forwarding AirVPN. Regards 1 go558a83nk reacted to this Quote Share this post Link to post
mannticleer 1 Posted ... Thanks for the follow-through. I'm in a somewhat related boat, but am stuck. I simply can't get 443 to forward correctly. I pointed my subdomain's A Record to my wan ip, and that's working. I attempted to use iptables to forward 443, but I guess I should instead be mapping my airvpn port (24181) to 443? I tried using your solution above, but it's not working. Dunno if I'm missing something basic. Quote Share this post Link to post