Closed LuXc-NL closed 1 year ago
This is a post-install, please check here for troubleshooting advice, most likely there is a conflicting port on your machine. Closing this, since all docker-compose files are carefully tested and crafted to ensure there are no port conflicts, also elasticsearch is running on tcp/64298
and does not collide with other services.
I tried it on multiple machines and I can assure you the port is not used (for both ipphoney and elasticpot). You are correct about elasticsearch running on the port tcp/64298
.
Nevermind. I was blocking the following domains in my Pi-hole:
Working fine now.
After a clean install I noticed that ipphoney and elasticpot are down. Elasticpot is using port 9200 but this is already in use by elasticsearch.
Is it safe to change this port to e.g. 9300 in the docker-compose?
ipphoney is throwing the following error:
uname -a: