From 5712f28b45fdf308694a324b4e2374a131faf06a Mon Sep 17 00:00:00 2001
From: Kyle Robinson <84939608+kylernocturnalnerd@users.noreply.github.com>
Date: Sat, 31 Dec 2022 00:58:10 -0500
Subject: [PATCH] Updated Running changedetection.io behind a reverse proxy
 (markdown)

---
 Running-changedetection.io-behind-a-reverse-proxy.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Running-changedetection.io-behind-a-reverse-proxy.md b/Running-changedetection.io-behind-a-reverse-proxy.md
index 3506b41..98efb41 100644
--- a/Running-changedetection.io-behind-a-reverse-proxy.md
+++ b/Running-changedetection.io-behind-a-reverse-proxy.md
@@ -1,3 +1,6 @@
+Before moving on, if your endpoint looks like this: `https://domain.com/subdirectory_dedicated_to_changedetector`
+Please review [this article](https://github.com/dgtlmoon/changedetection.io/wiki/Running-changedetection.io-behind-a-reverse-proxy-sub-directory) then come back here
+
 You need to enable the `USE_X_SETTINGS` environment variable in changedetection.io for it to respect HTTP headers sent from the reverse proxy (such as `Host`, `X-Forwarded-Prefix` and `X-Forwarded-Proto`).
 
 The easiest way is to create an extra docker-compose YML file and run it with the shipped version.