How to Set Up a Virtual Proxy Server on Proxmox at Home and Connect It to an Anti-Detect Browser

```html

A home server on Proxmox is not just a NAS and media center. Many arbitrage specialists and SMM experts already use it as a platform for their own proxy servers: they set up a virtual machine, configure Squid or 3proxy, and get a personal IP without a subscription fee. Let's explore how it works, why it's needed, and in which cases it's better to opt for ready-made residential proxies instead of a homemade solution.

What is Proxmox and why is it useful for arbitrage

Proxmox VE (Virtual Environment) is a free virtualization platform based on Linux that is installed directly on the hardware. Roughly speaking, it is an operating system that can run dozens of other operating systems simultaneously. Each of them is a separate virtual machine (VM) or container (LXC), isolated from the others.

For arbitrage specialists and SMM experts, this opens up an interesting opportunity: to set up one or more virtual machines, install a proxy server on each, and use a home IP as the traffic exit point. This is especially relevant if you have a "white" static IP from your provider at home — then you get a permanent address that belongs to a physical person, not a data center.

Why is this important? Because Facebook, Instagram, and TikTok can distinguish between data center IPs and home addresses. When you connect with a data center IP, security systems immediately see "suspicious" activity. A home IP looks like a regular user. This is why many arbitrage specialists are looking for ways to obtain a "live" IP without unnecessary costs.

In this scheme, Proxmox acts as a management platform: it allows you to quickly create, clone, and delete virtual machines with proxy servers, manage resources (how much RAM and CPU to allocate to each), take snapshots (instant copies of the state), and restore the system within minutes in case of failure. All this is done through a convenient web interface without the command line — just open a browser and go to your server's address.

Who is primarily interested:

• Arbitrage specialists who want to save on proxies and already have a home server
• SMM experts with a small number of accounts (up to 5-10)
• Those whose provider issues a static "white" IP
• People who want to understand how proxies work internally

How a virtual proxy server works on a hypervisor

The working scheme is simple. Imagine: you have a mini-PC or an old computer at home. Proxmox is installed on it. Inside Proxmox, a virtual machine with Ubuntu or Debian is running. On this virtual machine, a proxy server (Squid, 3proxy, or Dante for SOCKS5) is installed. You open Dolphin Anty, enter the IP of your home server and the port — and that's it, your browser profile goes online through your home IP.

Technically, the chain looks like this:

1. The anti-detect browser (Dolphin, AdsPower, GoLogin) sends a request to the IP of your home server, port 3128 (HTTP) or 1080 (SOCKS5)
2. Proxmox receives the request and redirects it to the virtual machine (via NAT or bridge network)
3. The proxy server inside the VM processes the request and sends it to the internet
4. The response returns through the same chain
5. Facebook or Instagram sees the IP of your home provider — a regular home address

An important point: if you want the proxy to be accessible from the outside (not just from the home network), you need to set up port forwarding on the router. This is a standard operation — in the router settings, you specify that incoming connections on port 3128 are redirected to the IP of your virtual machine within the network.

For multiple proxies on different ports, you create several virtual machines (or several instances of the proxy server on one VM) and forward each port separately. For example: 3128 → VM1, 3129 → VM2, 3130 → VM3. Each profile in the anti-detect browser gets its port — and formally "different" proxies, although all will have the same home address IP.

What you need to get started: hardware, network, IP

Before you rush to set up — check if you have everything necessary. A home proxy on Proxmox makes sense only under certain conditions.

Hardware

Proxmox does not require powerful hardware to run simple proxy servers. One proxy server consumes minimal resources — about 256-512 MB of RAM and a fraction of one CPU core. For 5-10 proxies, a machine with 4 GB of RAM and a dual-core processor will suffice. Suitable options include: mini-PCs like Intel NUC, Raspberry Pi 4 (with limitations), an old laptop or desktop, as well as specialized servers like HP ProLiant MicroServer.

Configuration	RAM	CPU	Number of proxies
Minimum	4 GB	2 cores	1-3
Average	8 GB	4 cores	5-15
Comfortable	16 GB	6-8 cores	20-50

Internet and IP

This is the most important point. Check with your provider:

• Static IP — necessary for stable operation. If the IP is dynamic (changes with each reconnection), the proxy will "disappear." A static IP costs 100-300 rubles per month with most providers.
• "White" IP — an IP accessible directly from the internet. If the provider issues a "gray" IP (behind NAT), port forwarding won't work without additional solutions (VPN tunnel, frp, ngrok).
• Upload speed — proxy traffic goes through your upload channel. For 5-10 accounts, 20-50 Mbps upload will suffice.

Creating a virtual machine for proxy in Proxmox

We assume that Proxmox is already installed and accessible at https://192.168.x.x:8006. If not — download the ISO from the official website proxmox.com and install it like a regular OS from a flash drive.

Step 1: Download the Ubuntu Server ISO image

In the Proxmox web interface, go to Datacenter → your node → local (storage). Click ISO Images → Download from URL. Paste the link for Ubuntu Server 22.04 LTS (find the current one on ubuntu.com). Click Query URL → Download. Wait for the download to complete.

Step 2: Create a virtual machine

Click the Create VM button in the upper right corner. Fill in the parameters:

• General → Name: proxy-01 (any understandable name)
• OS → ISO image: select the downloaded Ubuntu Server
• System: leave as default (BIOS, IDE)
• Disks → Disk size: 8 GB — more than enough for a proxy server
• CPU → Cores: 1 (sufficient for one proxy)
• Memory → RAM: 512 MB (you can use 256 MB for LXC container)
• Network → Bridge: vmbr0 (standard bridge, connected to the physical interface)

Click Finish. The virtual machine is created but not yet started.

Step 3: Install Ubuntu Server

Select the created VM in the left menu → click Start → open Console. Go through the standard Ubuntu installation: select the language, disk partitioning (Use entire disk), set a username and password. When asked about installing additional packages, select OpenSSH server — this will allow you to connect to the VM via SSH without the Proxmox console. After installation, the VM will reboot and be ready for use.

Installing and configuring Squid or 3proxy

There are several popular proxy servers for home use. Let's discuss the two most common options.

Option A: Squid (HTTP/HTTPS proxy)

Squid is a classic HTTP proxy. It is suitable for most anti-detect browsers that support HTTP/HTTPS proxies. The installation and basic configuration looks like this:

# Connect to the VM via SSH or through the Proxmox console
# Update packages and install Squid
sudo apt update && sudo apt install squid -y

# Create a backup of the config
sudo cp /etc/squid/squid.conf /etc/squid/squid.conf.bak

# Open the config for editing
sudo nano /etc/squid/squid.conf

Replace the contents of the file with the minimal working configuration:

# Proxy port
http_port 3128

# Authorization by login and password
auth_param basic program /usr/lib/squid/basic_ncsa_auth /etc/squid/passwd
auth_param basic realm Proxy Auth Required
acl authenticated proxy_auth REQUIRED

# Allow access only to authorized users
http_access allow authenticated
http_access deny all

# Hide server information
forwarded_for delete
via off

Create a user for authorization:

# Install the utility for creating passwords
sudo apt install apache2-utils -y

# Create a file with the user (replace myuser and mypassword)
sudo htpasswd -c /etc/squid/passwd myuser
# Enter the password twice when prompted

# Restart Squid
sudo systemctl restart squid
sudo systemctl enable squid

Option B: 3proxy (HTTP + SOCKS5)

3proxy is a more flexible solution that supports both HTTP and SOCKS5 protocols simultaneously. SOCKS5 is preferable for working with Facebook Ads and Instagram — it transmits less information about the client. Installation:

# Install dependencies and build from source
sudo apt install build-essential git -y
git clone https://github.com/z3APA3A/3proxy.git
cd 3proxy
make -f Makefile.Linux
sudo make -f Makefile.Linux install

# Create the configuration file
sudo nano /etc/3proxy/3proxy.cfg

Minimal configuration for SOCKS5 with authorization:

# Users (login:type:password)
users myuser:CL:mypassword

# Logging
log /var/log/3proxy.log D
logformat "- +_L%t.%. %N.%p %E %U %C:%c %R:%r %O %I %h %T"

# Authorization
auth strong

# SOCKS5 proxy on port 1080
allow myuser
socks -p1080

# HTTP proxy on port 3128 (optional)
allow myuser
proxy -p3128

After configuration, don't forget to open the necessary ports in the Ubuntu firewall:

sudo ufw allow 3128/tcp
sudo ufw allow 1080/tcp
sudo ufw enable

And set up port forwarding on your router: external port 3128 (or 1080) → internal IP of the virtual machine (e.g., 192.168.1.100) → port 3128 (or 1080).

Connecting the proxy in Dolphin Anty, AdsPower, and GoLogin

After the proxy server is set up and the ports are forwarded, connecting it to the anti-detect browser takes just a few minutes. Let's go through it step by step for each browser.

Dolphin Anty

1. Open Dolphin Anty → go to the Proxy section (left menu)
2. Click Add Proxy
3. Select type: SOCKS5 (if you set up 3proxy) or HTTP (Squid)
4. Enter IP — your external home IP (find it at 2ip.ru)
5. Enter Port — 1080 (SOCKS5) or 3128 (HTTP)
6. Enter Login and Password — those set during configuration
7. Click Check Proxy — it should show your home IP and country
8. Save and assign the proxy to the desired browser profile

AdsPower

1. Open AdsPower → Browser Profiles → New Profile
2. In the Proxy section, select the connection type: Custom Proxy
3. Protocol type: SOCKS5 or HTTP
4. Host: your external IP, Port: 1080 or 3128
5. Login and password: data from the proxy server config
6. Click Test Proxy — make sure it shows your home address
7. Save the profile and launch the browser

GoLogin

1. Open GoLogin → Create Profile
2. In the Proxy section, select Custom Proxy
3. Enter the data in the format: socks5://myuser:mypassword@YOUR_IP:1080
4. Click the check button — GoLogin will show the geolocation and IP type
5. Save and launch the profile

Security: authorization, firewall, isolation

An open proxy server without protection is a disaster. Bots scan the internet for open proxies and start using them for spam and attacks. Your home IP will end up on blacklists within hours. Therefore, security is a mandatory requirement, not an option.

1. Mandatory authorization

We have already set up authorization by login and password in the configurations above. Ensure that the proxy does not allow any requests without the correct credentials. Check: try to connect to the proxy without a login and password — it should deny access.

2. Firewall at the Proxmox level

Proxmox has a built-in firewall. Activate it and restrict access to the proxy ports only from the necessary IP addresses (for example, only from your office or VPN IP). Go to Datacenter → Firewall → Add. Create a rule: Direction — IN, Action — ACCEPT, Source — your allowed IP, Dest. Port — 3128 or 1080. All other incoming connections to these ports will be blocked.

3. Isolation of virtual machines

If you are running multiple VMs with proxies, ensure that they are isolated from each other. Use separate VLANs or configure firewall rules so that VMs cannot "see" each other within the Proxmox network. This is important if one of the proxy servers gets compromised — it should not have access to the others.

4. Regular updates

Set up automatic security updates on each VM:

sudo apt install unattended-upgrades -y
sudo dpkg-reconfigure unattended-upgrades
# Select "Yes" for automatic security updates

5. Log monitoring

Periodically check the proxy server logs for suspicious activity. In Squid, the logs are located at /var/log/squid/access.log. If you see requests from unknown IPs — immediately change the password and check the firewall rules.

Limitations of a home proxy and when it won't help

A home proxy on Proxmox is an interesting solution, but it has serious limitations that you need to be aware of in advance. Otherwise, you will waste time on setup and be disappointed with the results.

Limitation	What's the problem	Criticality
One external IP	All accounts use one IP — banning one = risk for all	High
No IP rotation	IP is constant — activity patterns can be easily tracked	High
Dependence on home internet	Power or internet outage — all proxies go down	Medium
Fixed geolocation	Cannot choose a country or city — only your real address	Medium
Upload speed	Home bandwidth is shared among all proxies and personal traffic	Low
Setup time	2-4 hours for initial setup, support requires time	Low

The main issue is one IP for everything. If you manage 10 Facebook accounts through one home IP, and Facebook decides to block that address (for example, due to complaints about one of the accounts) — all 10 accounts will be affected simultaneously. This is called "chain-ban" and is a nightmare for any arbitrage specialist.

When a home proxy doesn't solve the problem

There are scenarios where a home proxy on Proxmox is a bad solution, and it's better to use professional tools right away.

Scenario 1: Large-scale Facebook account farming

If you are farming 20, 50, or 100 Facebook Ads accounts — a home IP is categorically unsuitable. Each account needs a unique IP with a unique history. Facebook actively analyzes from which addresses accounts are created, and if it sees 50 accounts from one IP — it blocks them all at once. For farming, you need mobile proxies with rotation — they mimic the behavior of real mobile users and are significantly less likely to be blocked.

Scenario 2: Working with accounts from another country

You live in Russia, but you need to manage accounts registered in the USA, Germany, or the UK. A home Russian IP will immediately raise suspicions with Instagram or Facebook — the geolocation does not match the account history. You need residential proxies with IPs from the required country.

Scenario 3: Scraping marketplaces in large volumes

If you are scraping Wildberries, Ozon, or Avito with thousands of requests per hour — your home IP will be blocked within minutes. Wildberries and Ozon have serious protection against scraping from one IP. For high-frequency scraping, you need a pool of dozens or hundreds of IPs with rotation. In this case, data center proxies are optimal — they are faster and cheaper than residential ones when working with marketplaces that do not check IP types as strictly as social networks.

Scenario 4: Need reliability 24/7

Advertising campaigns cannot wait. If the power goes out at home or the provider conducts maintenance — all proxies will go down, and advertising accounts will lose connection. For critical tasks, a home solution is too unreliable. Professional proxy providers guarantee 99.9% uptime with redundancy.

Conclusion: home Proxmox or purchased proxy — what to choose

A home proxy server on Proxmox is an interesting technical project that provides insight into how proxies work internally. If you already have a home server, a static white IP, and a couple of free hours — why not give it a try? For personal use or testing, this is a workable solution.

However, for serious work — account farming, managing client profiles on Instagram and TikTok, traffic arbitrage through Facebook Ads — a home proxy has critical limitations: one IP for all accounts, no rotation, no choice of geolocation, dependence on home internet. These limitations make it unsuitable for professional multi-accounting.

If you plan to work with multiple accounts on social networks or run ads through Facebook Ads and TikTok Ads — we recommend considering residential proxies: each account gets a unique IP of a real home user, with the option to choose the country and city, and IP rotation on demand or on a schedule. This addresses the very issues that a home Proxmox proxy cannot solve.

Both approaches are not mutually exclusive. Many arbitrage specialists use home Proxmox for testing combinations and studying tools, while for live campaigns, they connect professional proxies with the necessary geolocation and IP pool. This is a sensible combination: saving where possible and investing where it impacts results.