diff --git a/roles/custom/matrix-nginx-proxy/defaults/main.yml b/roles/custom/matrix-nginx-proxy/defaults/main.yml
index ca4a15e7240..15dec40ca26 100644
--- a/roles/custom/matrix-nginx-proxy/defaults/main.yml
+++ b/roles/custom/matrix-nginx-proxy/defaults/main.yml
@@ -489,9 +489,9 @@ matrix_nginx_proxy_self_check_validate_certificates: true
 
 # Controls whether redirects will be followed when checking the `/.well-known/matrix/client` resource.
 #
-# As per the spec (https://matrix.org/docs/spec/client_server/r0.6.0#well-known-uri), it shouldn't be,
-# so we default to not following redirects as well.
-matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: none
+# As per the spec (https://spec.matrix.org/v1.4/client-server-api/#well-known-uri), it shouldn't be,
+# but in real life all client apps and servers accept the 301 redirect.
+matrix_nginx_proxy_self_check_well_known_matrix_client_follow_redirects: safe
 
 # For OCSP purposes, we need to define a resolver at the `server{}` level or `http{}` level (we do the latter).
 #