From f452733c645388f620747562d54f2d2668c35af3 Mon Sep 17 00:00:00 2001
From: Aniket <58530748+HandyHat@users.noreply.github.com>
Date: Mon, 31 Aug 2026 21:35:58 +0100
Subject: [PATCH] Mozilla SSL Config Generator has been replaced

---
 Proxy-examples.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Proxy-examples.md b/Proxy-examples.md
index 5591321..36ce011 100644
--- a/Proxy-examples.md
+++ b/Proxy-examples.md
@@ -7,7 +7,7 @@ The examples also assume that you have not encrypted the connection between the
 If you use [Docker Compose](https://docs.docker.com/compose/) to link containerized services together (e.g., Vaultwarden and a reverse proxy) you have to adapt the examples to take that into account (i.e. change `127.0.0.1:8000` to `service_name:80` where `service_name` typically would be `vaultwarden`). See [[Using Docker Compose|Using-Docker-Compose]] for an example of this.
 
 > [!TIP]
-Secure TLS protocol and cipher configurations for webservers can be generated using Mozilla's [SSL Configuration Generator](https://ssl-config.mozilla.org/). All supported browsers and the Mobile apps are known to work with the "Modern" configuration.
+Secure TLS protocol and cipher configurations for webservers can be generated using TLSref's [TLS Configurator](https://configurator.tlsref.org/) (formerly the Mozilla SSL Configuration Generator). All supported browsers and the Mobile apps are known to work with the "Modern" configuration.
 
 
 ***