Spun up a node on a public VPS — starts cleanly, HTTP /health is reachable from the internet, all good there. But the libp2p side seems quiet:
GET /api/v1/peers returns {"count":0,"peers":[]} indefinitely- At startup I get one
kademlia put_record failed (QuorumFailed) warning, then no peer / DHT / gossipsub activity in the logs at all
Configured the three official nodes as bootstrap peers:
GITLAWB_BOOTSTRAP_PEERS=https://node.gitlawb.com,https://node2.gitlawb.com,https://node3.gitlawb.com
Wondering if this is the right format — are those https:// HTTP URLs supposed to bootstrap libp2p too, or is there a separate env for libp2p multiaddrs? Also curious whether port 7546 on the official nodes is exposed publicly.
Running v0.3.8, federation-only (no PoS env set). Happy to share more logs if helpful.
DID: did:key:z6MksCGb4kWZnej4d6XeB3iHUWVnuE6CEhYuJ1iQHeWwtLgP
Spun up a node on a public VPS — starts cleanly, HTTP
/healthis reachable from the internet, all good there. But the libp2p side seems quiet:GET /api/v1/peersreturns{"count":0,"peers":[]}indefinitelykademlia put_record failed (QuorumFailed)warning, then no peer / DHT / gossipsub activity in the logs at allConfigured the three official nodes as bootstrap peers:
GITLAWB_BOOTSTRAP_PEERS=https://node.gitlawb.com,https://node2.gitlawb.com,https://node3.gitlawb.com
Wondering if this is the right format — are those
https://HTTP URLs supposed to bootstrap libp2p too, or is there a separate env for libp2p multiaddrs? Also curious whether port 7546 on the official nodes is exposed publicly.Running v0.3.8, federation-only (no PoS env set). Happy to share more logs if helpful.
DID:
did:key:z6MksCGb4kWZnej4d6XeB3iHUWVnuE6CEhYuJ1iQHeWwtLgP