SABnzbd Forums

Hi,

I'm on iPhone and Mac. Everything is working fine. I can use SABMobile whiles on my local network. But I can't access when away from home.
I think the issue is down to my ISP, it is an over the air wireless system and they won't let me control firewalls or portforwarding etc. Or maybe I'm doing something else wrong?
When I do try and connect, i just get 'wrong ip or unknown response from server'
any hints and tips would be great. thanks

If you can't do port forwarding, it's quite hard to reach inside systems from Internet. That's also a security advantage, BTW.

Hard stuff:
- setup a VPN from your system running SAB, and then tunnel back into that VPN
- setup IPv6 on your system running SAB, and then use a IPV4-to-IPv6 webproxy
- setup up a SSH tunnel to an outside server / VPS

I think the above doesn't help you.

Another solution: switch ISP to an ISP that does support & allow port forwarding

Thanks for the reply.
Sadly in my area I only have a couple of ISP to pick from.
It's a shame because I can use Bit Torrent and Torrent remote to add torrents to my Mac while away from home.
But if I want to add NZB to SABnzbd - the way I'm currently doing it is to use VNC and remote control my desktop to add NZB's.

Thanks anyway.

aquaboy wrote: It's a shame because I can use Bit Torrent and Torrent remote to add torrents to my Mac while away from home.

If you can't do port forwarding, how do you do that?

My VNC program (iTeleport) use's my gmail account too auto configure and connect.
uTorrent remote is turned on in preferences within uTorrent and then log onto via iphone safari at the URL remote.utorrent.com

So both programs kinda auto configure which is handy as I'm rubbish with networking!

https://remote.utorrent.com/ ... ah, that's cool. uTorrent probably sends keep-alives to that website to keep the port open.

yeah it works really well for me. But I wish SABMobile would work the same way :-) so I didn't have to configure anything! oh well. Thanks again.

https://remote.utorrent.com/srp/privacy says "In µTorrent Remote, your web browser serves as the client and your µTorrent client as the server. The µTorrent Remote servers act only as a channel between the two." and " This occurs entirely in your web browser, before the request is sent to µTorrent Remote for proxying to your µTorrent client."

So the route is: phone / web browser (client) -> uTorrent Remote (proxy) -> uTorrent client (server)

Communication is with rapton-i-92d067f9.utorrent.com:9004 , which is hosted on Amazon AWS:
I guess utorrent can pay for this based on the commercial stuff in the utorrent client.