From a4edfa353fb8ef2f904b50e24e756349796ae1eb Mon Sep 17 00:00:00 2001
From: Varac <varac@varac.net>
Date: Thu, 21 Nov 2019 14:26:19 +0100
Subject: [PATCH] Requested changes from review
---
docs/troubleshooting.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 0bc29fc4f..5c2572caf 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -1,6 +1,6 @@
# Troubleshooting
-Note: `cluster$` indicates that the commands should be run on your OAS cluster.
+Note: `cluster$` indicates that the commands should be run as root on your OAS cluster.
## HTTPS Certificates
@@ -10,6 +10,12 @@ services. If you experience invalid SSL certificates (i.e. your browser warns yo
when visiting Nextcloud (`https://files.YOUR.CLUSTER.DOMAIN`) here's how to
debug this:
+Did you create your cluster using the `--acme-live-environment` argument ?
+Please check the resulting value of the `acme_staging` key in
+`clusters/YOUR_CLUSTERNAME/settings.yml`. If this is set to `true`, certificates
+are fetched from the [Let's Encrypt staging API](https://letsencrypt.org/docs/staging-environment/),
+which can't be validated by default in your browser.
+
Are all pods in the `cert-manager` namespace in the `READY` state ?
cluster$ kubectl -n cert-manager get pods
--
GitLab