From f54509c3f93386c93a3771e0da252bb7dc7fd329 Mon Sep 17 00:00:00 2001
From: Stefan Melmuk <509385+stefan0xC@users.noreply.github.com>
Date: Wed, 9 Jul 2025 15:00:52 +0200
Subject: [PATCH] remove id again because it does not get rendered

---
 Proxy-examples.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/Proxy-examples.md b/Proxy-examples.md
index 8113fd7..fe0cd04 100644
--- a/Proxy-examples.md
+++ b/Proxy-examples.md
@@ -13,7 +13,7 @@ Secure TLS protocol and cipher configurations for webservers can be generated us
 ***
 
 
-<details id="caddy2">
+<details>
 <summary>Caddy 2.x</summary><br/>
 
 Caddy 2 will automatically enable HTTPS in most circumstances, check the [docs](https://caddyserver.com/docs/automatic-https#activation).
@@ -101,7 +101,7 @@ If you prefer, you can also directly specify a value instead of substituting an
 ```
 </details>
 
-<details id="lighttpd">
+<details>
 <summary>lighttpd with sub-path (by FlakyPi)</summary><br/>
 
 In this example Vaultwarden will be available via https://shared.example.tld/vault/<br/>
@@ -144,7 +144,7 @@ You'll have to set `IP_HEADER` to `X-Forwarded-For` instead of `X-Real-IP` in th
 
 </details>
 
-<details id="nginx">
+<details>
 <summary>Nginx (by <a href="https://github.com/BlackDex" target="_blank">@BlackDex</a>)</summary><br/>
 
 ```nginx
@@ -231,7 +231,7 @@ If you run into 504 Gateway Timeout problems, tell nginx to wait longer for Vaul
 
 </details>
 
-<details id="nginx-with-subpath">
+<details>
 <summary>Nginx with sub-path (by <a href="https://github.com/BlackDex" target="_blank">@BlackDex</a>)</summary><br/>
 
 In this example Vaultwarden will be available via https://shared.example.tld/vault/<br/>
@@ -335,7 +335,7 @@ server {
 ```
 </details>
 
-<details id="nginx-nixos">
+<details>
 <summary>Nginx (NixOS) (by tklitschi, samdoshi)</summary><br/>
 
 Example NixOS nginx config. For more Information about NixOS Deployment see [Deployment Wiki page](https://github.com/dani-garcia/vaultwarden/wiki/Deployment-examples).
@@ -376,7 +376,7 @@ Example NixOS nginx config. For more Information about NixOS Deployment see [Dep
 ```
 </details>
 
-<details id="nginx-proxy-protocol">
+<details>
 <summary>Nginx with proxy_protocol in front (by dionysius)</summary><br/>
 
 In this example there is a downstream proxy communicating in [proxy_protocol in front of this nginx](https://docs.nginx.com/nginx/admin-guide/load-balancer/using-proxy-protocol/) (E.g. a [LXD proxy device with proxy_protocol enabled](https://linuxcontainers.org/lxd/docs/master/reference/devices_proxy/)). Nginx needs to correctly consume the protocol and headers to forward need to be set from the those. Lines marked with `# <---` have different contents than BlackDex's example.
@@ -465,7 +465,7 @@ server {
 ```
 </details>
 
-<details id="apache">
+<details>
 <summary>Apache (by fbartels)</summary><br/>
 
 Remember to enable `mod_proxy_wstunnel` and `mod_proxy_http`, for example with: `a2enmod proxy_wstunnel` and `a2enmod proxy_http`.
@@ -493,7 +493,7 @@ Remember to enable `mod_proxy_wstunnel` and `mod_proxy_http`, for example with:
 ```
 </details>
 
-<details id="apache-with-subpath">
+<details>
 <summary>Apache in a sub-location (by <a href=https://github.com/agentdr8 target=_blank>@agentdr8</a>)</summary><br/>
 Modify your docker start-up to include the sub-location.
 
@@ -566,7 +566,7 @@ labels:
 ```
 </details>
 
-<details id="traefik">
+<details>
 <summary>Traefik v2 (docker-compose example by hwwilliams, gzfrozen)</summary><br/>
 
 #### Traefik v1 labels migrated to Traefik v2
@@ -601,7 +601,7 @@ labels:
 ```
 </details>
 
-<details id="haproxy">
+<details>
 <summary>HAproxy (by <a href="https://github.com/BlackDex" target="_blank">@BlackDex</a>)</summary><br/>
 
 Add these lines to your haproxy configuration. 
@@ -626,8 +626,8 @@ backend vaultwarden_http
 ```
 </details>
 
-<details id="haproxy-kubernetes-ingress">
-<summary>HAproxy Kubernetes Ingress(by <a href="https://github.com/devinslick" target="_blank">@devinslick</a>)</summary><br/>
+<details>
+<summary>HAproxy Kubernetes Ingress (by <a href="https://github.com/devinslick" target="_blank">@devinslick</a>)</summary><br/>
 
 Controller installation details can be found here: https://www.haproxy.com/documentation/kubernetes-ingress/community/installation/on-prem/
 Note that the CF-Connecting-IP header is only required if you use cloudflare 
@@ -665,7 +665,7 @@ spec:
 ```
 </details>
 
-<details id="istio">
+<details>
 <summary>Istio k8s (by <a href="https://github.com/asenyaev" target="_blank">@asenyaev</a>)</summary><br/>
 
 ```gateway+vs
@@ -718,7 +718,7 @@ spec:
 ```
 </details>
 
-<details id="cloudflare-tunnel">
+<details>
 <summary>CloudFlare Tunnel (by <a href="https://github.com/calvin-li-developer" target="_blank">@calvin-li-developer</a>)</summary><br/>
 
 `docker-compose.yml`:
@@ -789,7 +789,7 @@ ingress:
 </details>
 
 <details>
-<summary id="pound">Pound</summary><br/>
+<summary>Pound</summary><br/>
 
 ```
 Alive		15