Massprox Operator Runbook

Massprox Operator Runbook

Status as of 2026-11-05: Massprox is partially operational. The gatherer may be inactive. Verify live state before actions.

Access

Use the loopback operator surface:

ssh ubuntu@194.180.36.11
sudo -u massprox massprox-ops connect

Common commands:

• egress-test
• list-verified
• status
• token-create, token-rotate, token-revoke
• config-get, config-set
• audit-logs

Egress guard

Always run the egress test before operations:

sudo -u massprox massprox-ops egress-test

Expected: status is passed.

If it fails:

1. Stop affected services.
2. Check UID routing, IPv6 block, and DNS.
3. Fix and retest.
4. Start services only after pass.
5. Escalate if needed.

See Verify Egress Compliance.

Token lifecycle

• Create tokens with least privilege and expiry.
• Rotate tokens on schedule or after risk.
• Revoke unused or exposed tokens.
• Record token actions in audit logs.

Do not store token values in docs, git, or chat.

Audit

Record operator actions, config changes, token changes, and egress failures. Keep audit data in PostgreSQL suite when the service supports it.

Daily checks

sudo systemctl status mass-proxy-gather.service
sudo -u massprox massprox-ops egress-test
cat /home/ubuntu/search/proxies/mass-status.json

Troubleshooting

Symptom	Check	Action
Service not starting	journalctl -u mass-proxy-gather.service -n 50	Check egress guard and permissions
No verified proxies	Pool status and failure reasons	Check seeds, egress, timeouts
High failures	Egress test and proxy checks	Fix network, reduce load, review pool

Emergency

• Egress failure: stop services, fix guard, retest, escalate.
• Pool issues: pause gatherer, audit pool, rebuild if approved.
• Data issues: back up state, check integrity, restore if needed.

Related pages

• Massprox Architecture
• Massprox Configuration
• Verify Egress Compliance
• Search Restoration Runbook