-
Notifications
You must be signed in to change notification settings - Fork 89
http-addrindexrs, counterparty unable to connect to addrindexrs #350
Comments
Hey, something seems wrong with addrindexrs container. Try this: docker ps -a That will display a list of docker containers (if you can attach a screenshot it may be handy). Find the container id for addrindexrs. Then do this: docker inspect THAT_ID_YOU_FOUND Now it will display details for that container. Find network details and look for the container's ip, try to see if it matches "172.18.0.5" |
I am also encountering this issue when syncing a fednode today. @joslee7410 did you resolve it? The counterparty and http-addrindex config files reference a |
The config for addrindexr is taken directly from the https://github.com/CounterpartyXCP/federatednode/blob/master/docker-compose.tmpl.yml#L44-L82 |
Ok, I think there could be something happening here with the subnet ip addresses mismatching, but I don't know Docker well. I'm using Google Cloud to setup a fednode and here are tails of the different containers. Everything looks more or less like it's doing what it should except
|
But service (http-addrindexrs and counterparty) unable to connect addrindexrs(8432 port). Already make sure the port 8432 is using by addrindexrs container.
Please help, thank you.
The text was updated successfully, but these errors were encountered: