Running Appwrite in docker through nginx

Hi team,

I'm trying to expose multiple local services (Appwrite, Ollama, PostHog) through a single Nginx reverse proxy port, tunneled via ngrok to a public domain — so that my mobile app can reach them at URLs like:

www.domain.com/appwrite/
www.domain.com/ollama/
www.domain.com/posthog/

The motivation is that mobile apps are strict about networking — querying localhost directly requires overriding the HTTP adapter, which I'd like to avoid.

My current setup:

• Nginx runs in Docker and joins Appwrite's existing Traefik network
• Nginx proxies /appwrite/ → appwrite-traefik:80
• ngrok tunnels the single Nginx port to the public endpoint

The issue: When I hit /appwrite/, Traefik returns a 301 redirect to /console/, which Nginx doesn't handle — so it falls back to my default route and returns a JSON status message instead of the Appwrite UI.

I've attached my nginx.conf and docker-compose.yml below. Is there a detailed guide for this kind of path-based proxying in front of Traefik? Or is there a recommended way to wire Nginx into Appwrite's network without interfering with Traefik's routing?

Thanks!

Hey team 👋 — here's a status update on the Appwrite + Nginx reverse proxy setup.

✅ RESOLVED
• Nginx is fully running and routing correctly on port 3030
• /console/ → 200 OK, proxying directly to appwrite-console container
• /appwrite/v1/* → API is reachable, returning proper Appwrite responses (401 on auth-protected routes as expected)
• /ollama/ and /posthog/ routes are configured and ready
• appwrite-console container joined the appwrite Docker network and is reachable by container name
• env.js manually patched: PUBLIC_APPWRITE_ENDPOINT now points to http://localhost:3030/appwrite/v1

⚠️ CURRENT BLOCKER
The Appwrite console UI loads correctly but lands on /console/onboarding/create-project with a 404 (Page not found). This is a SvelteKit router-level 404 — not an Nginx issue. The app initializes, calls the API, but gets redirected to an onboarding route that doesn't resolve properly.

Likely causes under investigation:
• PUBLIC_APPWRITE_ENDPOINT is hardcoded in the Docker image and doesn't pick up environment variables at runtime — required a manual docker cp to patch env.js (not persistent across restarts)
• The console may be hitting the API at a different base URL than expected
• First-time setup state in Appwrite may be interfering with routing

🔜 NEXT STEPS
• Inspect Fetch/XHR calls in browser devtools to confirm what API endpoint the console is calling
• Test direct access via localhost:8080 (Traefik port) to isolate whether the issue is Nginx or Appwrite state
• Find a persistent solution for injecting PUBLIC_APPWRITE_ENDPOINT without manual patching on every restart

Will update once the API call flow is confirmed. Happy to jump on a call if needed.

https://klipy.com/gifs/tobey-maguire-sad-1

Appwrite does not support running on a different base path. I would recommend running on a different subdomain

So the whole nginx set up is not gonna work 😭