You set up your solo mining rig in the basement, pointed it at your node, and left it running. Three days later you realize you haven’t checked on it once — and you’re not home for another week.
That was me last summer when I went to visit my grandparents. My Kaspa node was happily crunching away in the basement, but I had no idea if it was still mining, if the power had gone out, or if my hashrate had dropped to zero. I spent the entire first day worrying about it until I finally set up remote access.
Here’s what the numbers say: If you’re solo mining and your rig goes down for even 24 hours, you’re burning electricity costs without any chance of hitting a block — and in solo mining, blocks are found through probability, not guarantees. Each hour of downtime means fewer attempts in what is essentially a lottery system, where even with consistent uptime your chances of finding a block remain probabilistic and highly variable. Depending on your setup, that could be anywhere from $5 to $50 wasted in electricity. More importantly, you’re losing lottery tickets in the block race.
This guide covers how to set up proper remote monitoring for your solo mining operation using TeamViewer. I tested this for two months before writing about it, running it across four different mining nodes simultaneously.
Why Solo Mining Remote Monitoring Actually Matters
Most pool miners can check their stats from a web dashboard. You’re solo mining. Your node runs on your hardware. No pool dashboard exists.
When you’re solo mining, you need direct access to:
- Your mining software’s real-time hashrate
- Your node’s sync status and block height
- GPU/ASIC temperatures and power consumption
- System logs for crashes or errors
- Network connectivity to your node
I run four solo mining setups: one Kaspa node with IceRiver KS3, one Ergo node with AMD GPUs running lolMiner, one Monero node with XMRig, and one Alephium node with a small IceRiver AL0. Before I set up remote monitoring, I was physically checking them every morning and evening.
That works when you’re home. Doesn’t work when you’re not.
TeamViewer vs Other Remote Management Tools for Solo Mining
I tested five different remote access solutions before settling on TeamViewer for most of my setups. Here’s what actually matters for solo mining scenarios:
TeamViewer — Free for personal use, works behind NAT without port forwarding, cross-platform. Handles Windows mining rigs and Linux nodes equally well. I use this on three of my four setups.
Chrome Remote Desktop — Also free, slightly simpler setup, but only works when Chrome is running. If your mining rig crashes hard, you can’t access it. I tried this first and switched away after one crash locked me out.
AnyDesk — Similar to TeamViewer, also free for personal use. Slightly faster in my testing, but less reliable connection stability when my home IP changes. Some people prefer it.
SSH (for Linux nodes) — Command-line only, requires port forwarding or VPN, but uses almost zero resources. I use this for my Monero node which runs headless on Ubuntu. If you’re comfortable with terminal commands, this is actually the most efficient option.
VNC (TightVNC/RealVNC) — Requires manual port forwarding, more technical setup, but completely free and open source. Worth considering if you’re running everything on a local network and don’t need internet access.
Based on my testing: TeamViewer for Windows mining rigs, SSH for Linux nodes. That combination covers 95% of solo mining remote monitoring needs.
Setting Up TeamViewer for Solo Mining Remote Access
I’m walking through the Windows setup here because that’s what most GPU miners run. Linux SSH setup comes later in this article.
Step 1: Download and Install TeamViewer
Go to teamviewer.com and download the full version (not QuickSupport). During installation, select “Personal / Non-commercial use” — this keeps it free. Install it on both your mining rig and whatever device you’ll use for remote access (laptop, phone, tablet).
Installation takes about 3 minutes. Default settings work fine for most solo mining setups.
Step 2: Set Up Unattended Access
This is the important part. You need unattended access so you can connect even when nobody’s physically at the mining rig.
Open TeamViewer on your mining rig. Click “Connection” → “Set up unattended access”. Create a TeamViewer account (free). Set a strong password for this specific device — write it down somewhere secure.
Under “Extras” → “Options” → “General”, enable “Start TeamViewer with Windows”. This ensures it’s always running when your mining rig boots up.
Worth noting: TeamViewer assigns your mining rig a permanent ID number. Mine is something like 1 234 567 890. You’ll use this ID to connect from anywhere.
Step 3: Configure Security Settings
Under “Extras” → “Options” → “Security”:
- Set “Personal password (for unattended access)” to a strong unique password
- Enable “Deny incoming LAN connections” (prevents local network attacks)
- Under “Advanced”, set “Access control” to “Confirm all” for the first week
That last setting means you’ll get a confirmation popup every time you try to connect. I ran this way for the first week just to verify no unauthorized connection attempts were happening. After that, switch to “Grant access” for your own account.
Step 4: Test Remote Connection
Install TeamViewer on your phone or laptop. Sign in with the same account. Your mining rig should appear in “My Computers”. Click it, enter your password, and you’re in.
First time I did this, I was at school checking on my Kaspa miner. Worked perfectly over 4G mobile data. Felt like magic.
Monitoring Your Solo Mining Node Through TeamViewer
Now that you’ve got remote access, here’s what to actually check and how often.
Daily Morning Check (2 minutes):
- Open your mining software — confirm hashrate matches expected numbers
- Check your node’s block height — should match network height
- Quick glance at GPU/ASIC temperatures
- Verify uptime hasn’t reset (no unexpected crashes)
I do this every morning at 7 AM. Takes about 90 seconds per rig. If everything looks good, I’m done. If something’s wrong, I investigate further.
Weekly Deep Check (10-15 minutes):
- Review full mining logs for errors or warnings
- Check Windows Event Viewer for system crashes
- Verify node is fully synced (compare block height to block explorer)
- Test network connectivity and latency to node RPC port
- Review power consumption trends (has anything changed?)
I do this every Sunday evening. Caught three issues this way that daily checks missed: one dying GPU fan, one SSD running out of space, and one node that had silently stopped syncing due to a peer connection issue.
What to Look For in Your Mining Software
Different mining software displays different information. Here’s what matters:
For lolMiner (GPU mining Ergo, for example): Check that all GPUs show their expected hashrate. My RX 6600 XT runs about 130 MH/s on Autolykos. If it drops below 120 MH/s, something’s wrong. Also verify “Shares Accepted” shows recent timestamps.
For XMRig (CPU mining Monero): Confirm hashrate is stable and “accepted” shares appear every few seconds. My Ryzen 5 5600 runs about 7.5 KH/s. If it drops to 6 KH/s, thermal throttling is likely happening.
For ASICs like the IceRiver KS3: Check the web interface via TeamViewer’s browser. Verify all hashboards show green status, temperatures stay under 65°C, and hashrate matches spec (8 TH/s for KS3).
Advanced Remote Monitoring: SSH for Linux Solo Mining Nodes
My Monero node runs on Ubuntu Server with no GUI. TeamViewer doesn’t make sense here. SSH is the right tool.
Basic SSH Setup for Remote Node Access
Most Linux mining nodes already have SSH enabled by default. If not, install it:
sudo apt install openssh-server
Find your node’s local IP address:
ip addr show
From another computer on the same network, test connection:
ssh username@192.168.1.XXX
If that works, you’re good for local network access. For remote access from outside your home network, you need either port forwarding or a VPN.
Port Forwarding for SSH (Security Warning)
I need to be honest here: Opening SSH to the internet is a security risk. Bots constantly scan for open SSH ports and try default passwords. If you do this, you MUST:
- Change SSH to a non-standard port (not 22)
- Use SSH keys instead of passwords
- Install Fail2Ban to block brute-force attempts
- Keep your system updated
Personally, I don’t expose SSH directly to the internet. I use Tailscale instead.
Tailscale VPN for Secure Remote Access
This is what I actually use. Tailscale creates a private network between your devices. Free for personal use, stupidly simple to set up.
On your Linux mining node:
curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
On your laptop or phone, install Tailscale and sign in with the same account. Your mining node appears as a device with a permanent IP address (something like 100.64.x.x). SSH to that IP from anywhere.
I tested this from a coffee shop 20 miles from home. Connected to my Monero node instantly, checked XMRig stats, verified everything was running. Zero port forwarding, zero security headaches.
Monitoring Multiple Solo Mining Setups Simultaneously
Running four different solo mining nodes gets complicated fast. Here’s how I organize remote monitoring across all of them:
Device Naming Convention
In TeamViewer, rename your devices clearly:
– “Kaspa-IceRiver-KS3-Basement”
– “Ergo-6600XT-Office”
– “Monero-Node-Ubuntu”
– “Alephium-AL0-Garage”
Sounds obvious, but when you’re checking four rigs at 7 AM before school, clear names prevent stupid mistakes like restarting the wrong miner.
Spreadsheet Tracking
I keep a Google Sheet with expected stats for each rig:
| Device | Expected Hashrate | Power Draw | Normal Temp Range | Block Odds (30 days) |
| KS3 | 8 TH/s | 3200W | 55-65°C | ~0.8% (Kaspa at current difficulty) |
| RX 6600 XT | 130 MH/s | 75W | 60-70°C | ~0.03% (Ergo at current difficulty) |
When I remote check each rig, I compare actual numbers to this sheet. Makes deviations immediately obvious.
Scheduled Checks
I set phone reminders:
– 7:00 AM daily: Quick check all rigs (5 minutes total)
– 8:00 PM Sunday: Deep check all rigs (30-40 minutes)
– Random checks when I’m bored in class
That last one happens more than I’d like to admit. Something satisfying about checking your mining stats during a boring lecture.
Mobile Remote Monitoring: TeamViewer on Phones
The TeamViewer mobile app works surprisingly well for quick checks. I use it more than the desktop version.
Download TeamViewer from App Store or Google Play. Sign in with your account. Your mining rigs appear under “My Computers”. Tap to connect.
Mobile Interface Tips:
The screen is obviously smaller. I use landscape mode for better visibility. TeamViewer has a “whiteboard” mode that lets you zoom into specific screen areas — useful for reading small mining software text.
For ASIC web interfaces, switch to “View” → “Quality” → “Optimize Speed” in TeamViewer settings. Makes web pages load faster over mobile data.
Battery drain is real. TeamViewer uses about 15-20% battery per hour of active use on my phone. I don’t leave it connected — quick 2-minute checks only.
Data Usage
I tracked this for a month. Quick 2-minute checks use about 5-10 MB of mobile data each. Not much, but 3 checks per day adds up to ~1 GB per month. Worth noting if you have a limited data plan.
Common Remote Monitoring Problems and Solutions
Problem: TeamViewer says “Not Ready. Please check your connection”
This means your mining rig isn’t connected to the internet or TeamViewer isn’t running. In most cases, this happens after a Windows update forces a restart and TeamViewer doesn’t auto-start.
Solution: Set up Windows to auto-login (search “netplwiz”), and verify TeamViewer starts with Windows. I also run a simple batch script on startup that launches my mining software 30 seconds after boot — gives TeamViewer time to connect first.
Problem: Connection works but screen is black
Usually means your monitor is off or in sleep mode. Your GPU is still mining fine, you just can’t see the screen.
Solution: Under TeamViewer’s “View” menu, try “Show black screen” or “Disable remote input”. Sometimes toggling these fixes display issues. For headless mining rigs, install a virtual display adapter.
Problem: Remote connection is extremely slow
Could be your home internet upload speed, or TeamViewer quality settings.
Solution: Under “View” → “Quality”, switch to “Optimize Speed” instead of “Optimize Quality”. Also check your home internet upload speed — if it’s under 5 Mbps, remote desktop will always be sluggish. I have 50 Mbps upload and TeamViewer runs smoothly.
Problem: Can’t access ASIC web interface through TeamViewer
TeamViewer connects to your PC, not directly to your ASIC. You need to access the ASIC’s web interface through a browser on the remote PC.
Solution: Connect via TeamViewer, open Chrome/Firefox on your mining rig, navigate to your ASIC’s IP address (usually something like 192.168.1.100). This gives you access to the ASIC’s control panel.
Security Considerations for Solo Mining Remote Access
You’re giving remote access to a computer that controls valuable mining hardware. Security matters.
Strong Passwords
Use a unique password for TeamViewer that’s different from your Windows password. I use a password manager (Bitwarden, free) to generate 20+ character random passwords.
Two-Factor Authentication
TeamViewer supports 2FA through their account settings. Enable it. Takes 30 extra seconds to log in, prevents unauthorized access if someone gets your password.
Regular Software Updates
Both TeamViewer and your mining rig’s OS need regular updates. I check monthly. Windows updates are annoying because they force restarts, but running outdated software on an always-online mining rig is worse.
Network Isolation
Worth considering: Put your mining rigs on a separate network from your personal devices. I run a separate guest WiFi network for all mining equipment. If someone compromises my mining rig, they can’t access my main computer or phone.
This requires a router that supports guest networks or VLANs. Not essential, but I sleep better knowing my mining gear is isolated.
Cost-Benefit Analysis: Is Remote Monitoring Worth It?
Here’s the honest math on whether remote monitoring makes sense for your solo mining operation.
Costs:
- TeamViewer: Free for personal use
- Time to set up: 30-60 minutes initial setup
- Mobile data usage: ~1 GB/month (~$3 if you need to upgrade your plan)
- Extra PC resources: TeamViewer uses about 100-200 MB RAM and minimal CPU
Benefits:
- Catch downtime within hours instead of days
- Prevent wasted electricity from crashed miners
- Respond to orphan blocks or node sync issues immediately
- Peace of mind when traveling
My Kaspa rig uses 3200W. At $0.12/kWh, that’s $9.22 per day in electricity — a substantial recurring expense that represents one of the largest ongoing costs in any mining operation. Electricity costs compound quickly: over a month, this single rig consumes $276.60 in power, making uptime monitoring critical for cost management. If remote monitoring lets me catch one 24-hour crash per month that I’d otherwise miss, I save $9.22 in wasted power costs. The setup paid for itself in one month.
For smaller setups (like my 75W GPU rig), the electricity savings are less dramatic — about $0.22 per day. But the peace of mind still makes it worth the 30 minutes of setup time.
Based on my testing: If you’re solo mining anything beyond a single GPU, remote monitoring is worth it.
Hidden Gem: Automated Monitoring Scripts
This is something most people don’t think about, but it’s actually the most efficient monitoring solution I’ve found.
Instead of manually checking your rigs, write a simple script that checks automatically and alerts you when something’s wrong.
Windows PowerShell Script Example:
I run this script every 30 minutes via Windows Task Scheduler on my Kaspa mining rig:
$process = Get-Process "lolMiner" -ErrorAction SilentlyContinue
if ($process -eq $null) {
# Mining software not running - send alert
Send-MailMessage -To "your@email.com" -From "miner@alert.com" -Subject "Kaspa Miner Down" -Body "lolMiner process not detected" -SmtpServer "smtp.gmail.com" -Port 587 -UseSsl -Credential (Get-Credential)
}
Takes about 15 minutes to set up properly, but then I only get alerts when something’s actually wrong. No more daily manual checks unless there’s an issue.
I’ve expanded this to also check:
- GPU temperature (alert if over 75°C)
- Disk space (alert if under 10 GB free)
- Internet connectivity (ping test to 8.8.8.8)
- Node sync status (compare local block height to block explorer API)
This naturally depends on your comfort with scripting. If you’re not technical, stick with manual TeamViewer checks. But if you want to level up your monitoring, automated scripts are the way.
FAQ: Solo Mining Remote Monitoring Questions
Does TeamViewer slow down my mining hashrate?
In my testing, no measurable impact. TeamViewer uses about 0.5-1% CPU when idle, maybe 3-5% CPU when actively connected. GPU mining and ASIC mining don’t touch CPU resources, so there’s no hashrate impact. CPU mining shows about 1-2% hashrate reduction when someone’s actively connected via TeamViewer, but returns to normal when disconnected. I measured this over a full week with my Monero CPU miner.
Can I monitor my solo mining node from a different country?
Yes, TeamViewer works globally. I connected to my home mining rigs from a vacation in another country — worked exactly the same as local connections. Latency was slightly higher (about 200ms instead of 50ms), but for monitoring purposes that doesn’t matter. Just be aware of data usage if you’re on international roaming rates.
What happens if my internet goes down — can I still mine?
Your miner needs internet to solo mine (it connects to your node, which connects to the network). If internet goes down, mining stops. TeamViewer obviously won’t work either. Worth noting: Some ISP outages are resolved within minutes. I’ve had three internet outages this year — two were under 15 minutes, one was 4 hours. Remote monitoring can’t help with internet outages, but it can alert you quickly so you know what’s happening.
Is SSH access more secure than TeamViewer for Linux mining nodes?
SSH with key-based authentication and Fail2Ban is probably more secure than TeamViewer for technical users. TeamViewer routes through their servers; SSH can be direct (if you trust your network security). I use both: TeamViewer for convenience on Windows rigs, SSH through Tailscale VPN for Linux nodes. Neither is inherently insecure if configured properly, but SSH requires more technical knowledge to set up correctly.
Can I restart my mining rig remotely if it crashes?
Sort of. You can remotely restart Windows through TeamViewer (Start → Power → Restart). But if your rig crashes hard enough that Windows is unresponsive, TeamViewer won’t help. For hard crashes, you need physical access or a smart power switch. I use TP-Link Kasa smart plugs on two of my rigs — I can power cycle them remotely through the phone app. Costs about $15 per plug. Worth it for critical mining rigs.