Overview

HTTP failures at startup are uncommon — this protocol has minimal system requirements. The node tests HTTP by making a request to bitping.com when it starts. If that request fails, HTTP shows as disabled.

Common Causes

Check your internet connection. The simplest cause is no working network. Confirm a basic HTTPS request succeeds:

curl -v https://bitping.com

Check for restrictive firewalls or proxies. Corporate firewalls or transparent proxies may block or interfere with outbound HTTPS traffic. If curl returns a TLS error or a 403 you didn’t expect, you’re likely behind a filtering proxy.

Check for DNS issues. If your node can’t resolve domain names, HTTP requests will also fail. The HTTP check needs to resolve bitping.com before it can even connect. See Troubleshooting Connectivity for DNS-specific debugging.

Verify From the Same Host

The most useful test is the one that runs from the same machine as the node:

# Resolves DNS and connects
curl -v https://bitping.com

# DNS-only check
nslookup bitping.com

If curl works but the node still reports HTTP as disabled, restart the node — capability checks run once at startup.

See also: Troubleshooting Protocol Failures.