Travelling, and a site insists you're in the wrong country? Your PhoneRig phone is already sitting at home on your home internet. One command routes your browser through it.
Every PhoneRig runs an SSH server. The ssh command on your laptop has a built-in trick: dynamic forwarding (the -D flag) turns that connection into a SOCKS5 proxy. Point your browser at it and your traffic comes out of your home connection, at home. Nothing to install on the phone, no new ports opened, nothing extra to pay for.
Copy the exact command from the app - open the Address tab and expand the Travel proxy card. It fills in the real user, address and port for your phone, and picks the right address for reaching it from outside your home. The card has two modes: On a computer (the command above, for the laptop in front of you) and On another phone (a share command, for sending a second phone home). Pick the one you need.
The phone stays home, powered and on its charger, with the PhoneRig server running. To reach it from outside your home network, enable remote SSH first (Address tab → SSH) - the Travel proxy card then shows a command that works from anywhere.
Paste the command from the app into a terminal and sign in with your SSH password (shown in the app). Leave that terminal window open - it is the proxy. If your command mentions cloudflared, install that first: it's the tunnel client, one download.
Set your browser's SOCKS5 proxy to localhost port 1080 - exact clicks for each browser and system below.
Visit an IP-checking site (search "what is my IP"). It should now show your home city and provider, not the network you're sitting on.
Two depths, and you choose: one browser only (Firefox keeps the change inside Firefox, and undoing it is a single radio button) or the whole computer (the macOS system proxy sends Safari, Chrome and most other apps through it until you turn it back off). On Windows there is no system SOCKS setting, so the browser route is the one that works.
Settings → search "proxy" → Network Settings → Manual proxy configuration. SOCKS Host localhost, Port 1080, select SOCKS v5, and tick Proxy DNS when using SOCKS v5. Firefox is the easiest: the proxy applies to Firefox only, and switching back is one radio button.
Chrome follows the system proxy, so set it in macOS or Windows settings (next cards). Or run Chrome with its proxy flag from a terminal: --proxy-server="socks5://localhost:1080".
System Settings → Wi-Fi → Details… on your network → Proxies → enable SOCKS proxy, server localhost, port 1080. Applies to Safari and Chrome. Turn it off there when you're done.
Windows' built-in proxy setting speaks HTTP, not SOCKS, so the reliable route is Firefox (first card) - or Chrome with the flag above.
Phones take a different route: a computer on the same Wi-Fi shares the proxy and the phone points its Wi-Fi settings at it. Set up another phone →
Undo the proxy setting and close the terminal window. Traffic goes back to normal the moment either one stops.
An iPhone or a spare Android can browse through your home connection too - but a phone can't run the ssh command itself. So a computer on the same Wi-Fi runs it and shares the proxy with the network, and the phone points its Wi-Fi proxy setting at that computer.
Copy the exact command from the app - Travel proxy card, On another phone mode. The 0.0.0.0 is the whole difference: it tells the proxy to accept connections from other devices on the Wi-Fi, not only from the computer it runs on.
Any computer sitting on the same Wi-Fi as the phone you're setting up - yours, in the hotel room. Paste the command from the app's On another phone mode into a terminal, sign in, and leave that window open. It is the proxy.
macOS: System Settings → Wi-Fi → Details… on your network, read the IP address. Windows: open a Command Prompt, run ipconfig, read the IPv4 Address. It usually looks like 192.168.1.24.
Phones can only be sent to a SOCKS proxy through an auto-config (PAC) URL, so build yours below, then: iPhone - Settings → Wi-Fi → the ⓘ button next to the network → Configure Proxy → Automatic → paste the URL. Android - Wi-Fi settings → edit the network (pencil or long-press) → Advanced → Proxy → Proxy Auto-Config → paste the URL.
On the phone, visit an IP-checking site (search "what is my IP"). It should show your home city and provider. When you're done, set the proxy back to Off and close the terminal.
Your PAC URL - this is what goes in the phone's proxy setting. Type the address from step 2 and it fills in.
The URL is always https://phonerig.app/pac?socks= followed by the computer's IP address, a colon, and the port from the command (1080 unless you changed it), so with the example address above it is exactly the line shown. Swap in your own and you're done.
That 0.0.0.0 proxy accepts anyone on the same Wi-Fi, not just your phone. Fine on your home network; on shared Wi-Fi, close the terminal the moment you're done.
Plenty of hotel, café and guest networks stop devices from seeing each other at all. If the phone simply can't reach the computer, that's usually why - and nothing on either device will fix it. A hotspot both devices join works instead: a third phone's, or the computer's own (Windows: Mobile hotspot). The phone you're setting up can't use its own hotspot for this - its traffic never crosses it.
The proxy attaches to that one Wi-Fi network and covers everything the phone sends over it, not just the browser. Join a different network, or use mobile data, and it doesn't apply.
The PAC file offers no direct fallback. If the terminal closes or the tunnel drops, pages stop loading instead of quietly going out over the local network - better a page that won't load than believing you appear at home when you don't.
Android can run the tunnel itself. Install Termux (Play Store or F-Droid), run pkg install cloudflared openssh, then paste the app's normal On a computer command (the -D 1080 one) and leave Termux running. That opens the proxy on the phone's own 127.0.0.1:1080. Then SocksDroid (free) pointed at 127.0.0.1 port 1080 turns it into the whole phone's route home. More moving parts than the computer path, and it's on you to keep Termux alive.
We'd rather say it plainly than have you hunt: there is no iPhone-only version of this. The tunnel client doesn't run on iOS, and iOS won't hold an SSH session open in the background the way this needs. An iPhone needs a computer on the same Wi-Fi doing the sharing, which is the main path above.
Websites see your home connection and location, because that is where your traffic really exits. Region checks that expect your home country see your home country.
Between your laptop and your phone, everything rides inside SSH. The hotel or airport Wi-Fi you're on sees an encrypted connection to your home, not the sites you visit.
The exit is your own home internet - an address more identifying than any shared exit, because it's yours alone. If anonymity is what you need, use Tor or a VPN service; this feature is not that, and doesn't try to be.
Only apps configured to use the proxy go through it - your browser, if that's what you set. Everything else on the laptop uses the local network as usual.
Home phone off, unplugged, or offline means no proxy. Leave it on its charger with the server running - the app's status notification tells you it's up.
Browsing rides your home connection's upload speed, which is usually the slower direction. Fine for pages and mail; video may buffer.
The plain LAN command only works inside your home Wi-Fi. Enable remote SSH before you leave, and take the command the Travel proxy card shows after that.
The proxy lives exactly as long as the SSH connection. Laptop sleeps, connection drops: rerun the command and you're back.