From 96d303b05eef0f87342263a8da9c9858c8ba0021 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9leste=20Wouters?= Date: Mon, 15 Dec 2025 01:59:24 +0100 Subject: [PATCH] cookbook/reverse-proxy: remove Buypass Go SSL Buypass Go SSL has stopped providing SSL/TLS certificates, including from their ACME API endpoints, as of October 2025, and the service is to be completely phased out by April 2026: https://community.buypass.com/t/y4y130p Remove them from the docs as an ACME-capable provider. --- doc/book/cookbook/reverse-proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/book/cookbook/reverse-proxy.md b/doc/book/cookbook/reverse-proxy.md index e4a0f6c3..d0f0c2bd 100644 --- a/doc/book/cookbook/reverse-proxy.md +++ b/doc/book/cookbook/reverse-proxy.md @@ -7,7 +7,7 @@ The main reason to add a reverse proxy in front of Garage is to provide TLS to y In production you will likely need your certificates signed by a certificate authority. The most automated way is to use a provider supporting the [ACME protocol](https://datatracker.ietf.org/doc/html/rfc8555) -such as [Let's Encrypt](https://letsencrypt.org/), [ZeroSSL](https://zerossl.com/) or [Buypass Go SSL](https://www.buypass.com/ssl/products/acme). +such as [Let's Encrypt](https://letsencrypt.org/) or [ZeroSSL](https://zerossl.com/). If you are only testing Garage, you can generate a self-signed certificate to follow the documentation: