diff --git a/Reverse-Proxy-Diagnostics-Troubleshooting.md b/Reverse-Proxy-Diagnostics-Troubleshooting.md
index 44e5fdf..b354b8e 100644
--- a/Reverse-Proxy-Diagnostics-Troubleshooting.md
+++ b/Reverse-Proxy-Diagnostics-Troubleshooting.md
@@ -1,5 +1,8 @@
 See also:
 * Q&A: https://github.com/Kozea/Radicale/discussions/categories/q-a-reverse-proxy
+* Reference configurations
+  * Apache: https://github.com/Kozea/Radicale/tree/master/contrib/apache
+  * nginx: https://github.com/Kozea/Radicale/tree/master/contrib/nginx
 
 Precondition "radicale" server is running fine and accessable
 * Wiki: https://github.com/Kozea/Radicale/wiki/Server-Diagnostics---Troubleshooting
@@ -176,6 +179,19 @@ Connection: keep-alive
 Last-Modified: Wed, 13 Mar 2024 05:36:47 GMT
 ```
 
+# URI issue
+
+In case one is serving "Radicale" not on `/`, but e.g. on `/radicale`, check whether "X-Script-Name" is set to main part of the URI to tell Radicale on which "hook" it is responsible for:
+
+## Apache example for "/radicale"
+
+`RequestHeader    set X-Script-Name /radicale`
+
+## nginx example for "/radicale"
+
+`proxy_set_header  X-Script-Name /radicale;`
+
+
 # Packet Capture
 
 ## using ngrep