Issue with deploying multiple instances of PostHog using Docker in same VM

Hello Docker Community,

I’m encountering issues while attempting to deploy multiple instances of PostHog using Docker. I initially deployed one instance successfully using the following script:

/bin/bash -c "$(curl -fsSL"

This script prompted the version and domain URL, and the deployment included services such as Redis, PostHog, ClickHouse, Zookeeper, Kafka, TemporalIO, Minio, and Caddy.

When I tried to deploy another instance using the same script, I faced a port conflict issue. I resolved this by modifying the port configurations in various Docker Compose files. Here are the files I modified:

Root Directory:

  • docker-compose.yml
  • docker-compose-base.yml
  • .env
  • caddyfile

Inside posthog Directory:

  • docker-compose-base.yml
  • docker-compose-hobby.yml
  • docker-compose-dev-full.yml
  • docker-compose-dev.yml

After resolving the port conflict, the website is now showing a blank page. I suspect there might be an issue with the configurations or ports, but I’m not sure where to look.

Steps Taken:

  1. Modified ports to resolve conflicts.
  2. Checked configurations in various Docker Compose files.

Request for Help:

I would appreciate any guidance or insights from the Docker community on why the website is displaying a blank page after successfully deploying multiple instances. If anyone has experience with deploying multiple instances of PostHog or troubleshooting similar issues, your assistance would be invaluable.


Thank you in advance for your help!

To answer your question we would indeed need to know posthog and face the same issue. There is not much information we can work with here. An empty page could mean many thing but docker logs could give you an idea which service failed if that is logged.

docker compose logs

Have you considered asking the question on GitHub?

If multiple instances are not supported by the installer, it could also be a feature request.

You can also check the documentation and search for any clue what parameters the installer supports:

And open the script on GitHub to look for variables.