Files
Funky (OpenClaw) 01bc8995c2 Fix VPS IP address (66.63.182.168 → 51.222.12.162) + Add Minecraft port forwarding
CRITICAL CORRECTION:
- Old deprecated VPS: 66.63.182.168 (DO NOT USE)
- Current VPS: 51.222.12.162 (vps-3fce361e.vps.ovh.ca, OVH Canada)
- WireGuard IP: 10.0.9.1 (confirmed via SSH)

Added Minecraft ATM10 port forwarding:
- External: 51.222.12.162:25568
- Internal: 10.0.10.46:25568 (via WireGuard tunnel)
- iptables DNAT + MASQUERADE rules configured
- Rules saved to /etc/iptables/rules.v4 (persists across reboots)
- SRV record: _minecraft._tcp.atmons.deadeyeg4ming.vip → 51.222.12.162:25568

Updated files:
- All 6 documentation files with correct VPS IP
- Added port forwarding section to NETWORK-ARCHITECTURE.md
2026-02-06 02:55:11 +00:00

81 lines
2.8 KiB
Markdown

# TOOLS.md - Local Notes
Skills define *how* tools work. This file is for *your* specifics — the stuff that's unique to your setup.
## Fred's Homelab Infrastructure
### Network
- Main Network: 10.0.10.0/24
- VPN: WireGuard tunnel at 10.0.9.0/24
- VPS WireGuard IP: 10.0.9.1 (51.222.12.162 - vps.nianticbooks.com)
- UCG Ultra WireGuard IP: 10.0.9.2 (WireGuard client mode)
- VPS: 51.222.12.162 (vps.nianticbooks.com) running Caddy reverse proxy
- Handles: *.nianticbooks.com and *.deadeyeg4ming.vip
### Proxmox Hosts
- Main Proxmox host: 10.0.10.3 (main-pve)
- HP DL380: Proxmox host running my container
### Key Services (LXC Containers)
- Home Assistant: 10.0.10.24 - Smart home automation
- n8n: 10.0.10.22 (CT 106) - Workflow automation
- Uptime Kuma: 10.0.10.26 (CT 128) - Service monitoring
- OpenClaw Gateway: 10.0.10.28 (CT 130) - AI agent coordination (that's me!)
- Running as LXC container on HP DL380
- No sound card/audio output on this container
- Step-CA: 10.0.10.15 (CT 115) - Internal certificate authority
### Paired Nodes
- **Fred's iMac**: 10.0.10.11 - OpenClaw desktop app node
- Provides: Camera, screen recording, canvas display, notifications
- Potential audio output for TTS
- Near Fred but screen visibility limited
- **Known Issue:** `nodes screen_record` fails with "The operation could not be completed" (OpenClaw 2026.2.1 bug)
- **Workaround:** Use native `screencapture` command instead:
```bash
# Record 3 seconds of screen
screencapture -T 3 -V 3 /tmp/screen-recording.mp4
```
### Current Projects
- Homelab infrastructure management
- 3D printing projects
- Android head unit/carputer for truck
## Location
- Weather location: Niantic, IL 62551
## Tasks & Organization
- Wants to use Apple Reminders/Tasks on iPhone
- Need to explore integration options
## n8n Workflow Automation
**Instance:** http://10.0.10.22:5678
**API Key:** `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiI1ZTVjZTQ2Zi1iNmUyLTQyMGEtYmUzMC1iYzQzYThlMDA1YjMiLCJpc3MiOiJuOG4iLCJhdWQiOiJwdWJsaWMtYXBpIiwiaWF0IjoxNzcwMDk3NDEwfQ.7NBimIPNlVH_Jif-3FU-9MSPfPUP1ILSznKGR1JzpE8`
**User:** OpenClaw (API access granted Feb 3, 2026)
**Active Workflows:**
- Prometheus alerts → Discord/Email/Pushover
- Backup verification (daily @ 6 AM)
- SSL certificate expiration monitor
- Service health monitor (every 5 min via Uptime Kuma)
- Task overdue alerts (every 4 hours)
- Uptime Kuma webhook → alerts
**API Usage:**
```bash
# List all workflows
curl -H "X-N8N-API-KEY: <key>" http://10.0.10.22:5678/api/v1/workflows
# Get specific workflow
curl -H "X-N8N-API-KEY: <key>" http://10.0.10.22:5678/api/v1/workflows/{id}
# Trigger workflow
curl -X POST -H "X-N8N-API-KEY: <key>" http://10.0.10.22:5678/api/v1/workflows/{id}/execute
```
---
Add whatever helps you do your job. This is your cheat sheet.