From 1c4790bd08d0696978845a0d8b29b1e45e06a880 Mon Sep 17 00:00:00 2001
From: LinuxServer-CI <ci@linuxserver.io>
Date: Thu, 5 May 2022 06:59:48 -0500
Subject: [PATCH] Bot Updating Documentation

---
 images/docker-quassel-web.md | 25 +++++++++++++++----------
 1 file changed, 15 insertions(+), 10 deletions(-)

diff --git a/images/docker-quassel-web.md b/images/docker-quassel-web.md
index 083eecbe9..be799f79b 100644
--- a/images/docker-quassel-web.md
+++ b/images/docker-quassel-web.md
@@ -21,17 +21,17 @@ title: quassel-web
 
 ## Supported Architectures
 
-Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
+We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
 
-Simply pulling `lscr.io/linuxserver/quassel-web` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
+Simply pulling `lscr.io/linuxserver/quassel-web:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
 
 The architectures supported by this image are:
 
-| Architecture | Tag |
-| :----: | --- |
-| x86-64 | amd64-latest |
-| arm64 | arm64v8-latest |
-| armhf | arm32v6-latest |
+| Architecture | Available | Tag |
+| :----: | :----: | ---- |
+| x86-64 | ✅ | amd64-\<version tag\> |
+| arm64 | ✅ | arm64v8-\<version tag\> |
+| armhf| ✅ | arm32v7-\<version tag\> |
 
 ## Application Setup
 
@@ -41,6 +41,11 @@ The configuration file using this method can be found at:
 /config/settings-user.js
 ```
 
+### Strict reverse proxies
+
+This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
+If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
+
 ## Usage
 
 To help you get started creating a container from this image you can either use docker-compose or the docker cli.
@@ -52,7 +57,7 @@ To help you get started creating a container from this image you can either use
 version: "2.1"
 services:
   quassel-web:
-    image: lscr.io/linuxserver/quassel-web
+    image: lscr.io/linuxserver/quassel-web:latest
     container_name: quassel-web
     environment:
       - PUID=1000
@@ -80,7 +85,7 @@ docker run -d \
   -p 64443:64443 \
   -v /path/to/data:/config \
   --restart unless-stopped \
-  lscr.io/linuxserver/quassel-web
+  lscr.io/linuxserver/quassel-web:latest
 ```
 
 ## Parameters
@@ -159,7 +164,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
 * Container version number
   * `docker inspect -f '{{ index .Config.Labels "build_version" }}' quassel-web`
 * Image version number
-  * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web`
+  * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web:latest`
 
 ## Versions