diff --git a/site/docs/master/contributions/minio.md b/site/docs/master/contributions/minio.md
index 12daff4a1..86012b0b9 100644
--- a/site/docs/master/contributions/minio.md
+++ b/site/docs/master/contributions/minio.md
@@ -229,6 +229,20 @@ You must also get the Minio URL, which you can then specify as the value of the
 
 1.  Edit your `BackupStorageLocation` YAML, adding `publicUrl: <URL_FROM_PREVIOUS_STEP>` as a field under `spec.config`. You must include the `http://` or `https://` prefix.
 
+## Accessing logs with an HTTPS endpoint
+
+If you're using Minio with HTTPS, you may see unintelligible text in the output of `velero describe`, or `velero logs` commands.
+
+In order to fix this, you can add a public URL to the `BackupStorageLocation`.
+
+In a terminal, run the following:
+
+```shell
+kubectl patch -n velero backupstoragelocation default --type merge -p '{"spec":{"config":{"publicUrl":"https://<a public IP for your Minio instance>:9000"}}}'
+```
+
+If your certificate is self-signed, see the [documentation on self-signed certificates][32].
+
 ## Expose Minio outside your cluster with Kubernetes in Docker (KinD):
 
 Kubernetes in Docker currently does not have support for NodePort services (see [this issue](https://github.com/kubernetes-sigs/kind/issues/99)). In this case, you can use a port forward to access the Minio bucket.
@@ -249,6 +263,7 @@ kubectl edit backupstoragelocation default -n velero
 
 Add `publicUrl: http://localhost:9000` under the `spec.config` section.
 
+
 ### Work with Ingress
 
 Configuring Ingress for your cluster is out of scope for the Velero documentation. If you have already set up Ingress, however, it makes sense to continue with it while you run the example Velero configuration with Minio.
@@ -265,3 +280,4 @@ In this case:
 [18]: ../debugging-restores.md
 [26]: https://github.com/vmware-tanzu/velero/releases
 [30]: https://godoc.org/github.com/robfig/cron
+[32]: ../self-signed-certificates.md
diff --git a/site/docs/v1.3.2/contributions/minio.md b/site/docs/v1.3.2/contributions/minio.md
index 12daff4a1..2a72c9a4a 100644
--- a/site/docs/v1.3.2/contributions/minio.md
+++ b/site/docs/v1.3.2/contributions/minio.md
@@ -229,6 +229,20 @@ You must also get the Minio URL, which you can then specify as the value of the
 
 1.  Edit your `BackupStorageLocation` YAML, adding `publicUrl: <URL_FROM_PREVIOUS_STEP>` as a field under `spec.config`. You must include the `http://` or `https://` prefix.
 
+## Accessing logs with an HTTPS endpoint
+
+If you're using Minio with HTTPS, you may see unintelligible text in the output of `velero describe`, or `velero logs` commands.
+
+In order to fix this, you can add a public URL to the `BackupStorageLocation`.
+
+In a terminal, run the following:
+
+```shell
+kubectl patch -n velero backupstoragelocation default --type merge -p '{"spec":{"config":{"publicUrl":"https://<a public IP for your Minio instance>:9000"}}}'
+```
+
+Note that Velero does not support custom, self-signed certificates prior to v1.4.0.
+
 ## Expose Minio outside your cluster with Kubernetes in Docker (KinD):
 
 Kubernetes in Docker currently does not have support for NodePort services (see [this issue](https://github.com/kubernetes-sigs/kind/issues/99)). In this case, you can use a port forward to access the Minio bucket.
diff --git a/site/docs/v1.4-pre/contributions/minio.md b/site/docs/v1.4-pre/contributions/minio.md
index 12daff4a1..86012b0b9 100644
--- a/site/docs/v1.4-pre/contributions/minio.md
+++ b/site/docs/v1.4-pre/contributions/minio.md
@@ -229,6 +229,20 @@ You must also get the Minio URL, which you can then specify as the value of the
 
 1.  Edit your `BackupStorageLocation` YAML, adding `publicUrl: <URL_FROM_PREVIOUS_STEP>` as a field under `spec.config`. You must include the `http://` or `https://` prefix.
 
+## Accessing logs with an HTTPS endpoint
+
+If you're using Minio with HTTPS, you may see unintelligible text in the output of `velero describe`, or `velero logs` commands.
+
+In order to fix this, you can add a public URL to the `BackupStorageLocation`.
+
+In a terminal, run the following:
+
+```shell
+kubectl patch -n velero backupstoragelocation default --type merge -p '{"spec":{"config":{"publicUrl":"https://<a public IP for your Minio instance>:9000"}}}'
+```
+
+If your certificate is self-signed, see the [documentation on self-signed certificates][32].
+
 ## Expose Minio outside your cluster with Kubernetes in Docker (KinD):
 
 Kubernetes in Docker currently does not have support for NodePort services (see [this issue](https://github.com/kubernetes-sigs/kind/issues/99)). In this case, you can use a port forward to access the Minio bucket.
@@ -249,6 +263,7 @@ kubectl edit backupstoragelocation default -n velero
 
 Add `publicUrl: http://localhost:9000` under the `spec.config` section.
 
+
 ### Work with Ingress
 
 Configuring Ingress for your cluster is out of scope for the Velero documentation. If you have already set up Ingress, however, it makes sense to continue with it while you run the example Velero configuration with Minio.
@@ -265,3 +280,4 @@ In this case:
 [18]: ../debugging-restores.md
 [26]: https://github.com/vmware-tanzu/velero/releases
 [30]: https://godoc.org/github.com/robfig/cron
+[32]: ../self-signed-certificates.md