Blogs Engineering

Pointing Pezzo's Local Proxy at the Local Server: A Two-Line Docker Compose Fix

Pezzo's Docker Compose proxy reported to Pezzo Cloud and logged 'Invalid Pezzo Project ID'. Two lines point it at the local server instead.

TypeScriptpezzolabs/pezzoDocker ComposeLLMOpsconfiguration

A missing environment variable, and a default that pointed somewhere else.

Short answer

When Pezzo ran locally with Docker Compose, the proxy had no PEZZO_SERVER_URL, so its client fell back to the hosted default https://api.pezzo.ai. Requests reached the model provider, but the proxy logged "Invalid Pezzo Project ID" and nothing appeared in the local console. The fix sets the variable for the proxy service. It was merged as PR #355 and closed issue #299.

The fix

     env_file:
       - ./.env
       - ./apps/proxy/.env
+    environment:
+      - PEZZO_SERVER_URL=http://pezzo-server:3000

By the numbers

  • Repository: pezzolabs/pezzo, 3,279 stars (Nov 3, 2026), TypeScript, Apache-2.0
  • Files changed: 1
  • Lines: +2 / -0
  • Commits: 1
  • Opened and merged: Aug 21, 2026. Time to merge: 1 minute, 25 seconds
  • Review: merged by a maintainer

How the review went

The maintainer replied "Thanks for that. Merging." and merged it.

FAQ

Where can I read more?

See the pull request and the original issue, open since May 2024.

The goal

Self-hosted setups should talk to themselves by default. Making that explicit in the Compose file removes a confusing first-run failure.

Run the loop

Turn production signals into reviewed fixes.

Start a free trial and see how Prilog maps real incidents to code-level pull requests.