From 77bf739ce277117eb27fc795c2d4c417d3f484d3 Mon Sep 17 00:00:00 2001 From: "(skovati) Luke" Date: Tue, 6 Feb 2024 12:27:01 -0800 Subject: [PATCH] add self-signed cert info box --- docs/deployment/advanced-reverse-proxy.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/deployment/advanced-reverse-proxy.md b/docs/deployment/advanced-reverse-proxy.md index d132fec..3943a53 100644 --- a/docs/deployment/advanced-reverse-proxy.md +++ b/docs/deployment/advanced-reverse-proxy.md @@ -39,3 +39,15 @@ docker compose -f docker-compose.yml -f ./proxy/docker-compose-proxy.yml up -d - ``` You can now visit `https://here-is-the-domain-you.set`, which will prompt you to trust a self-signed certificate, and then forward you to Aerie as usual! + +:::info Accepting self-signed certificates +You will need to accept self-signed certificates for Aerie UI, Hasura, _and_ the Gateway. +Visit the following three URLs and follow the instructions to allow self-signed certs: +- `https://here-is-the-domain-you.set` +- `https://here-is-the-domain-you.set:8080/console` +- `https://here-is-the-domain-you.set:9000` + +Aerie will *not* function correctly if all three certificates are not accepted. + +This manual process can be avoided if you are able to use a testing certificate for this domain that is signed by your authorities. +:::