Support & Troubleshooting

Stuck? Since QueryGlow is self-hosted, you have full visibility into its logs and configuration, and one command checks most of it for you.

Start Here: ./queryglow doctor

In your QueryGlow directory on the server, run:

./queryglow doctor          # checks the host and the install
./queryglow doctor --fix    # applies four safe repairs
./queryglow doctor --report # support report without any .env value
./queryglow status          # installed and running version, containers, last update

doctor checks Docker, .env permissions and secrets, containers, health, versions, ports, the nginx config, DNS, the certificate and free disk. Paste the --report output into your support email; it contains no secrets.
status tells you which version you run. The app also shows it in the sidebar footer, next to the gear icon.
Update first. Many fixes ship in releases: 1.3.0 fixed JSON cells showing [object Object], OpenAI models that rejected Ask AI requests, Safari on iOS asking for the password twice, and a slow CockroachDB connection test. Run ./queryglow update (how updates work).

Before You Ask

Quick checks for the most common questions:

• Query blocked? Safe Mode may be on. Check QUERYGLOW_ALLOW_DESTRUCTIVE in your .env.
• Connection failed? Verify the database is reachable: telnet hostname port
• Container won't start? Check the logs: ./queryglow logs -f (or docker compose -f docker-compose.production.yml logs -f)
• Changed .env and nothing happened? A restart does not read it again. Recreate the container: docker compose -f docker-compose.production.yml up -d --force-recreate queryglow
• HTTPS certificate issues? Make sure DNS points to your server and ports 80 and 443 are open.

Need More Help?

Customers report bugs and request features in the GitHub repository they were invited to. Email works for everything, including questions before you buy.

GitHub issues (customers)Email Support

Questions before buying: [email protected]