Pools 17
Miners N/A
Workers N/A
Software and troubleshooting

Set up an SSL mining proxy

Last updated: 18 November 2026

Send every rig through one server you control: what an SSL mining proxy is, when to use one, how to set it up, and why it clears the shared worker warning.

What is an SSL mining proxy?

A mining proxy is one small server that you rent and control. Your rigs connect to it instead of to the pool. It holds a single encrypted connection out to the pool on their behalf.

Nothing about your mining changes. The same shares are submitted, the same worker names are used and the payouts are identical. Only the path changes.

It is called an SSL proxy because the link from your proxy to the pool is encrypted with TLS. Your rigs only talk to your own server, on a port you choose. So a network that blocks the pool hostname or the mining ports sees nothing it recognises.

Without a proxy, each rig connects to the pool on its own, and a network block stops all of them. With a proxy, the rigs connect to one server you rent, which holds a single encrypted link to the pool.
One link out instead of one per rig.

When do you actually need one?

Most miners never need a proxy. Use one only when one of these is true.

  • Your ISP or your country blocks the pool hostname or the mining ports, and changing DNS did not fix it.
  • You run rigs in more than one place and want them to reach the pool through a single route.
  • You have many rigs behind one slow or unstable uplink and want one connection out instead of dozens.
  • The pool tells you the same worker name is used from several countries, and those rigs really are all yours.
  • You run rented GPUs in many places at once, such as SaladCloud replicas or many vast.ai instances. Without a proxy, the wallet can be flagged as a botnet.

If none of those is true, a proxy only adds a machine that can fail. Mine directly.

Why a proxy clears the shared worker name warning

Your dashboard warns when one worker name is seen from more than one country. It must also come from places nearest to different mining servers. To the pool, that looks like one name used by more than one person.

A name seen only inside one country never triggers the warning. If your rigs really are spread out, each one shows up as its own origin.

Sending them all through one proxy means the pool sees a single origin, so the warning stops. Giving each rig its own worker name fixes the same thing without a proxy. That is the simpler answer when the rigs are all in one place.

The same worker name arriving from three countries reads as shared. The same three rigs behind one proxy reach the pool as a single origin.
The pool judges by where the connection comes from, not by who owns the rigs.

Why does a rented GPU fleet need a proxy?

A rented fleet connects from as many IPs as it has machines, often in many countries. One wallet on that many IPs is how a botnet looks, so it gets flagged.

Behind your proxy, the same fleet reaches the pool as one connection from one place. The article on why a wallet on many IPs is flagged has the details.

What you need

  • A small virtual server in a country that can reach the pool. The cheapest tier is enough: a proxy forwards bytes, it does not hash.
  • Root access on it, and the ability to open one inbound port for your rigs.
  • The pool hostname you want to reach, from the list further down.

The simplest setup: stunnel

stunnel wraps a plain connection in TLS. Your rigs speak plain stratum to the proxy on your own port. stunnel then speaks TLS to the pool.

Install stunnel from your distribution, then use a configuration of this shape.

/etc/stunnel/stunnel.conf
[mining]
client = yes
accept = 0.0.0.0:4444
connect = de.pearl.herominers.com:1200
verifyChain = no
  • Start the service.
  • Point one rig at your proxy address on port 4444, with a plain stratum URL.
  • Check that the miner connects and its shares are accepted. If so, the path works.
  • Only then move the rest of the rigs over.

Replace the connect line with the host and port of the coin you mine. Keep the accept line on an address your rigs can reach and nothing else can. A proxy open to the whole internet will be found and used by strangers.

How do you lock a proxy that rented machines reach over the internet?

A rented fleet cannot be fenced off by IP address. Its machines change, and each one connects from somewhere else. So the proxy port has to be open to the whole internet.

Lock it with a shared key instead. stunnel calls it a PSK, a pre-shared key. A machine without the key is refused, and every link to the proxy is encrypted.

  • Create a random key on the proxy, for example with openssl rand -hex 32.
  • Write it to /etc/stunnel/psk.txt as one line: a name, a colon and the key, such as fleet:YOUR-KEY.
  • Let only stunnel read that file, because the key is the lock.

On the proxy, one section takes your machines in with the key, and a second one carries their traffic to the pool over TLS:

/etc/stunnel/stunnel.conf
[fleet-in]
accept = 0.0.0.0:4444
connect = 127.0.0.1:4445
PSKsecrets = /etc/stunnel/psk.txt

[pool-out]
client = yes
accept = 127.0.0.1:4445
connect = de.pearl.herominers.com:1200
verifyChain = no

Every rented machine runs stunnel too, with the same key file and this section. Its miner then mines to 127.0.0.1:4444:

/etc/stunnel/stunnel.conf
[to-proxy]
client = yes
accept = 127.0.0.1:4444
connect = YOUR-PROXY-IP:4444
PSKsecrets = /etc/stunnel/psk.txt

On SaladCloud, put stunnel in the container image. Pass the key as an environment variable, and let the start script write it to the file before it starts the miner.

Test one machine first. A machine with a wrong key, or with no key, is refused before it reaches the pool.

The alternative: nginx stream

If the proxy already runs nginx, its stream module does the same job. It keeps everything in one configuration file.

nginx.conf
stream {
  server {
    listen 4444;
    proxy_ssl on;
    proxy_pass de.pearl.herominers.com:1200;
  }
}

This needs nginx built with the stream module, which most distribution packages include. Reload nginx and test with one rig, exactly as above.

How to point your rigs at the proxy

Change only the pool address in each rig. The wallet address, the worker name and every other option stay as they are.

miner command
-o stratum+tcp://YOUR-PROXY-IP:4444 -u YOUR_WALLET.rig1 -p x

Give each rig its own worker name, even behind a proxy. The proxy hides where the rigs are. So the worker name is the only thing left that tells them apart on your dashboard.

Which host to connect to

Every HeroMiners stratum port accepts both plain and TLS connections, for example de.pearl.herominers.com:1200. Every HeroMiners coin is listed below.

Pick the region closest to your proxy, not to your rigs. The proxy is the machine that holds the connection.

Put the region prefix in front of the host you pick.
CoinHost
Alephiumalephium.herominers.com
Beambeam.herominers.com
Confluxconflux.herominers.com
Ergoergo.herominers.com
Ethereum Classicetc.herominers.com
Kaspakaspa.herominers.com
Moneromonero.herominers.com
Pearlpearl.herominers.com
QRLqrl.herominers.com
Quai Networkquai.herominers.com
Quantusquantus.herominers.com
Qubitcoinqubitcoin.herominers.com
Ravencoinravencoin.herominers.com
Warthogwarthog.herominers.com
Xelisxelis.herominers.com
Zanozano.herominers.com
Zephyrzephyr.herominers.com

Each pool lists its regional hostnames and ports on its How to Mine page. Put the region prefix in front of the host, for example de.pearl.herominers.com.

Common mistakes

  • Leaving the proxy port open to the internet. Restrict it to your own addresses with a firewall rule.
  • Renting the proxy in the same country that is doing the blocking. Pick one that can reach the pool.
  • Moving every rig at once. Move one, confirm accepted shares, then move the rest.
  • Expecting more hashrate. A proxy changes the route, never the work. If anything, it adds a few milliseconds.
  • Forgetting the proxy exists. It is another machine that can go down, so watch it like a rig.

Is a proxy worth it?

If a block is stopping you from mining at all, yes. A proxy is the cheapest way around it.

If you are only clearing a warning on your dashboard, give each rig its own worker name. It is free and does the same job. Use a proxy when the route is the problem, not the names.

Ready to put this into practice?
Pick a coin on the pools overview and open its How to Mine guide for a ready-to-run command.
Choose a pool