From 62952f92476886569a7c73cd5c2f4ec46af80ddb Mon Sep 17 00:00:00 2001 From: Alan Grainger <16197738+alangrainger@users.noreply.github.com> Date: Mon, 21 Jul 2025 12:30:27 +0200 Subject: [PATCH] Update README.md --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1888d7c..f66a136 100644 --- a/README.md +++ b/README.md @@ -31,6 +31,7 @@ Setup takes less than a minute, and you never need to touch it again as all of y - [IPP options](#immich-public-proxy-options) - [lightGallery](#lightgallery) - [Custom error pages](#customising-your-error-response-pages) + - [Serving from multiple domains](#serving-from-multiple-domains) - [Troubleshooting](#troubleshooting) - [Feature requests](#feature-requests) @@ -208,7 +209,9 @@ See [Custom responses](docs/custom-responses.md) for more details. If you're serving the same IPP from multiple domains, instead of setting the public URL in your docker-compose file, you can set it dynamically via a HTTP header in the request from your reverse proxy to IPP. -Set a custom `publicBaseUrl` header on each request with the value of your public base URL (example `https://your-proxy-url.com`). +1. Remove the `PUBLIC_BASE_URL` environment variable from your docker-compose file. + +2. Set a custom `publicBaseUrl` header on each request with the value of your public base URL (example `https://your-proxy-url.com`). ## Troubleshooting