The host config template on the get started page (https://docs.shinzo.network/run/get-started/) tells you to write:
shinzo:
hub_base_url: testnet.shinzo.network:26657
But the Host client wants a bare hostname here and appends the port itself. The field comment in shinzo-host-client says it outright:
HubBaseURL string `yaml:"hub_base_url"` // ShinzoHub hostname only — no scheme, no port (e.g. "testnet.shinzo.network")
So following the quickstart as written, the host builds ws://testnet.shinzo.network:26657:26657/websocket and panics on startup:
panic: failed to start hosting: error starting event subscription: initial WebSocket connection failed: dial ws://testnet.shinzo.network:26657:26657/websocket: dial tcp: address testnet.shinzo.network:26657:26657: too many colons in address
The view fetch right before the panic fails the same way (invalid port ":26657:1317"), so both the lcd and rpc ports get doubled.
Fix is just dropping the port from the template:
shinzo:
hub_base_url: testnet.shinzo.network
Verified on ubuntu 26.04 with the ethereum-mainnet-latest images. With the port removed the host starts, connects to shinzohub, peers with the generator, and serves graphql fine.
One related thing while that page is open: it says no shinzohub registration is needed, which is true, but the host still opens a websocket to shinzohub on startup and panics if it can't connect. worth a sentence so people running fully offline don't get surprised by that.
The host config template on the get started page (https://docs.shinzo.network/run/get-started/) tells you to write:
But the Host client wants a bare hostname here and appends the port itself. The field comment in shinzo-host-client says it outright:
So following the quickstart as written, the host builds
ws://testnet.shinzo.network:26657:26657/websocketand panics on startup:The view fetch right before the panic fails the same way (
invalid port ":26657:1317"), so both the lcd and rpc ports get doubled.Fix is just dropping the port from the template:
Verified on ubuntu 26.04 with the
ethereum-mainnet-latestimages. With the port removed the host starts, connects to shinzohub, peers with the generator, and serves graphql fine.One related thing while that page is open: it says no shinzohub registration is needed, which is true, but the host still opens a websocket to shinzohub on startup and panics if it can't connect. worth a sentence so people running fully offline don't get surprised by that.