Monero Monero Mining Started Sep 12, 2026 7:00 PM

p2pool-mini with xmrig but node is on another machine

4 replies - 217 views - 1 thanks - 0 tippers - 5 watchers

Sep 12, 2026 7:00 PM
#1
p2pool xmrig port

Hi all,

My node is on "machine A", which is old and weak and only has a couple threads.

"Machine B" doesn't have a node but has 32 threads that I want to use to mine on p2pool-mini.

I asked duckduckgo how to mine on Machine B and point it to my node on machine A. It gave me the following instructions:

Mining on P2Pool with XMRig from a Different Machine

To successfully mine on P2Pool using XMRig while your Monero node is hosted on a different machine, follow these steps:
Requirements

Monero Node: Ensure your Monero node is fully synchronized and running.
XMRig: Download and install XMRig on the machine where you will be mining.
Firewall Configuration: Make sure the firewall on both machines allows traffic on the necessary ports.

Configuration Steps

Point XMRig to P2Pool Node:
    In your XMRig configuration or command line, specify the IP address of your P2Pool node and use port 3333.
    Example command:

    ./xmrig -o YOUR_P2POOL_NODE_IP:3333

Firewall Settings:
    Ensure that the firewall on the machine running the P2Pool node allows incoming connections on port 3333.
    You may also need to open port 37889 for P2Pool's peer-to-peer communication.

Additional Tips

Use a Configuration File: Instead of command-line flags, consider using a config.json file for XMRig. This can help avoid mistakes and simplify the setup.
Monitor Your Mining: You can check your mining progress by entering your wallet address on the P2Pool Observer to see your statistics.

Summary of Ports
Port Number Purpose
3333 XMRig connection to P2Pool node
37889 P2Pool peer-to-peer communication

By following these steps, you can effectively mine on P2Pool using XMRig while your Monero node operates on a separate machine.

me talking again- Is it truly this simple? Or are these instructions inadequate? I'm asking you guys/gals humans because AI notoriously gives wrong info and I'm trying to avoid headaches.

Thanks all

1 thanks - 0 tippers - 5 watchers

Replies

Page 1 of 1 - 4 total
Sep 13, 2026 4:55 AM
#2

I believe you can use xmrig proxy to accomplish this.

1 thanks - nemesis - 0 tippers
Sep 14, 2026 12:27 AM Edited Sep 14, 2026 5:04 AM
#4

@xbmrtc could be wrong, but don't think that would help in this setup. The proxy is to point multiple xmrigs to a single p2pool instance and would require xmrig on the box that isn't being used to mine

Signature

principles over profit

0 thanks - 0 tippers
Sep 18, 2026 12:03 PM
#5

@dweeb Yes it's that easy. I've never mined on the same hardware running the node/daemons. IMO the daemons should always be ran on separate server style systems with good ECC and a UPS while the workers just mine.

As for the AIs advice on ports it seems a little off this is my p2pool-mini run flags:p2pool --mini --stratum 0.0.0.0:3332 --p2p-external-port 37888 --out-peers 25 --in-peers 5 --local-api --light-mode --stratum-ban-time 1 --full-validation --data-dir /tmp/p2pool-mini --data-api /tmp/p2pool-json --wallet <wallet_main_addr> --subaddress <wallet_sub_addr>
I use stratum 3332 so I can have the option to run multiple p2pool (mini/nano/main) nodes without conflicting with each other. But as you can see the port for mini is 37888 not 37889 I belive that one is for main. So make sure to port-forward the correct one. Also don't port-forward stratum 3333 or whatever you plan to use for the workers (not needed, maybe unsafe).

And just for refence this is my xmrig run opts: xmrig -4 -a rx/0 <node_ip>:3332 -u x+1200000 --randomx-no-rdmsr --argon2-impl=SSSE3 --randomx-1gb-pages --huge-pages-jit --randomx-mode=fast --cpu-no-yield --print-time=10 --http-host=0.0.0.0 --http-port=80
I use this on 3 systems and get around 155 Kh/s on p2pool-mini. If your hashrate is very low ~20-50 Kh/s range you may want to check out p2pool-nano.

0 thanks - 0 tippers

Post A Reply

You must be logged in to reply. Login or register.