Bandwidth Sharing
Fix a disabled Bandwidth Sharing (Proxy) protocol on your Bitping Node — connectivity and startup checks
Overview
The Bandwidth Sharing capability routes traffic through your node as a proxy. It has minimal requirements and is enabled in almost every configuration. If it shows as disabled, the cause is almost always a transient startup issue or missing internet access.
Common Fixes
Restart the node. Most often this is a transient startup issue and a restart re-runs the capability check.
Check your internet connection. The proxy needs a working outbound network connection. Confirm basic reachability:
curl -v https://bitping.com
If curl fails, fix the connectivity issue first (Troubleshooting Connectivity) and then restart the node.
Persistent Failures
If Bandwidth Sharing stays disabled after a restart on a healthy connection, contact [email protected] with the first few lines of bitpingd run showing capability checks — this is unusual.
See also: Troubleshooting Protocol Failures.