chain_id / unknown protocol in flextesa-sandbox

[uid2532]

With tqtezos/flextesa:20211025 (as it is currently in docker-compose.flextesa.yml):

Indexer: ERR error="Invalid chain_id: NetXgbFy27eBoxH (state) != NetXzcB5DmnBoxG (head)"

Updating docker-compose.flextesa.yml to:

image: tqtezos/flextesa:20211206 command: hangzbox start

Indexer: ERR error="Unknown protocol: PtHangz2aRngywmSRGGvrcTyMbbdpWdpFKuS4uMWxg2RaH9i1qx"

Looks like the indexer expects Hangzhou for the flextesa sandbox chain_id but then, if flextesa is ran with hangzbox, the indexer does not recognise the protocol.

[uid2532]

Can you please update bakingbad/bcdhub-indexer docker hub image?

[852Kerfunkle]

As a workaround, you can just build the latest images locally with make stable-images.

[uid2532]

As a workaround, you can just build the latest images locally with make stable-images.

Thanks. Just a note that for the workaround to work you need to first pull the golang:1.15-alpine, postgres:12 and docker.elastic.co/elasticsearch/elasticsearch:7.5.1 images and also update docker-compose.flextesa.yml as mentioned above.

[m-kus]

Chain id mismatch usually means that you have indexed one network and then switched to another one. Wiping the indexer database should help

[uid2532]

Chain id mismatch usually means that you have indexed one network and then switched to another one. Wiping the indexer database should help

I think it's just that the docker hub indexer image is not updated with Hangzhou. I was able to run it following @852Kerfunkle comment above with a few modifications.