VM Proxy: Guest or Host? VMware and VirtualBox Setup
Decide where the proxy belongs for a virtual machine, and prove with three tests that it is working.
Three places to set the proxy
Three places to set the proxy
Item
Inside the guest
On the host
Network adapter mode
What it changes
Apps in that virtual machine only
Apps on the host that read the system proxy
How the guest reaches the network, not which IP it shows
Host keeps its own IP
Yes
No, the host's apps change too
Not applicable
Good for
One machine, one fixed IP
Only the host's own browsing
NAT for simple access, bridged when the guest needs its own place on the network
Source: VirtualBox manual (NAT, bridged) and VMware Workstation Pro documentation excerpt, read on 17 November 2026; the host-versus-guest rows follow from each being its own operating system.
In NAT mode VirtualBox takes the guest's network frames, extracts the TCP/IP data and sends it out again through the host's operating system. For the outside world the traffic comes from the host's address, but that is network address translation, not the host's proxy dialog: the guest's apps still make direct connections unless the guest itself is told to use a proxy.
That is also why a host-level tool and a guest-level proxy can give different answers on an IP test, and why you should always test from inside the guest.
Leave the adapter on NAT unless the guest needs its own address on your network; in that case bridged mode puts it directly on the host's network. Do not use host-only, it has no route to the external network.
Step 2
Open the guest, not the host. In a Windows guest use Settings, Network & internet, Proxy; in a macOS guest use System Settings, Network. Or set the proxy in the guest's browser.
Step 3
Use the HTTP line, port 2222, for Chrome-family browsers in the guest: Chrome supports no authentication for SOCKS5. Keep the SOCKS5 line, port 3333, for tools that handle it.
In the guest, open ipinfo.io or run the curl lines below. Do the same on the host. The two IPs should be different: the guest shows the proxy, the host shows your own line.
Expected result Different IPs on guest and host.
Step 5
Run a WebRTC check in the guest's browser and a DNS check. Neither should show your home address.
# Inside the guest (Linux or macOS guest shell), HTTP line:
curl -x http://LOGIN:PASSWORD@HOST:2222 https://ipinfo.io/json
# SOCKS5 line, DNS also through the proxy:
curl -x socks5h://LOGIN:PASSWORD@HOST:3333 https://ipinfo.io/json
# Then, with no -x, the same request shows what the guest does without the proxy:
curl https://ipinfo.io/json
Example only: replace LOGIN, PASSWORD and HOST with the values from My assets. The third request is the control without the proxy.
ipinfo.io inside the guest shows the same IP as the host.
Check Whether the proxy was set in the guest or only on the host, and whether the app you tested reads the system proxy.
Fix Set it inside the guest, then test again with curl -x to separate the proxy from the app.
The IP is right but the WebRTC check shows another address.
Check The adapter mode and the browser: a bridged guest sits on the same network as the host, so a second address can appear.
Fix Follow the WebRTC guide for that browser and recheck inside the guest.
The proxy works with curl but the guest's browser fails.
Check Protocol and port: a Chrome-family browser needs the HTTP line on 2222 when a login is required.
Fix Switch the browser to the HTTP line and retry.
Stop when If curl also fails inside the guest, stop changing the browser and send a ticket with the order number.
Keep it simple: one machine, one IP, one account
A virtual machine does not change what a platform expects from an account. Give each account one fixed IP, do not share the account between people, follow the platform's terms and supported regions, and complete any verification it asks for honestly.
If you are choosing between a virtual machine, a VPS and a fingerprint browser, the comparison guide lays out what each one needs from the IP.
No. The guest is a separate operating system, so its network settings are its own. In NAT mode its traffic leaves through the host's network, but that is address translation, not the host proxy.
Check the exit IP, country and ISP your proxy really gives you in 30 seconds — and why IP databases disagree on the city. With our own test of three lookup services.
Product facts file of the site (values checked against the console, the backend and the price table in October and November 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, renewal rules, no free trial.
Read on 17 November 2026: in NAT mode the guest behaves like a computer behind a router, its traffic is resent through the host's operating system so outside machines see the host's address, and it gets a private address from a built-in DHCP server, usually on 10.0.2.0; bridged mode makes the guest appear plugged into the host's network; host-only has no route to the external network.
Read on 17 November 2026 from a search excerpt only: Workstation Pro 17 documents bridged, NAT, host-only and custom networking, and bridged networking gives the virtual machine direct access to an external Ethernet network.
Only the excerpt was read; check the full page for NAT details.
Read on 17 November 2026: no authentication methods are supported for SOCKSv5 in Chrome, and with a SOCKSv5 proxy name resolution is always done on the proxy side.
Ready to try it?
Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.