Troubleshooting
Running decentralized infrastructure can be tricky. These guides cover the most common issues operators encounter, with step-by-step fixes.
IPFS Troubleshooting
- •Node won't start or connect to peers
- •Pinning is stuck or extremely slow
- •Port 4001 blocked by firewall/ISP
- •CORS errors when using the API
- •High CPU or memory usage
- •Content not found on gateways after pinning
Nostr Troubleshooting
- •Relay won't accept WebSocket connections
- •TLS certificate errors
- •Events not propagating to other relays
- •High memory usage / database growth
- •Nginx WebSocket proxy issues
- •NIP-07 extension not detected in browser
Tor Troubleshooting
- •Hidden service not reachable
- •.onion address changed unexpectedly
- •Tor daemon won't start
- •Extremely slow page loads
- •Nginx not serving on the hidden service port
- •Security: leaked server IP
Arweave Troubleshooting
- •Upload failed or timed out
- •Insufficient funds error
- •Transaction stuck in pending
- •ArConnect wallet not connecting
- •arkb deploy errors
- •Content not visible on arweave.net
General Tips
- •Check logs first. Almost every issue leaves a trace in the logs. Use
journalctl -u service-name -ffor systemd services. - •Verify network access. Many issues are firewall-related. Use
ss -tlnpto check listening ports andcurlto test from outside. - •Keep software updated. Bugs get fixed. Security holes get patched. Run the latest stable release.
- •Ask the community. If you're stuck, reach out on Nostr or through our participation channels. Someone has probably hit the same issue.