From 756c791fc6602b6ae287b7bb770153b2c2ba1f32 Mon Sep 17 00:00:00 2001
From: crocs <34723037+pairofcrocs@users.noreply.github.com>
Date: Mon, 6 Nov 2023 19:04:25 -0600
Subject: [PATCH] Update unraid.md

---
 mkdocs/docs/installation/unraid.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/mkdocs/docs/installation/unraid.md b/mkdocs/docs/installation/unraid.md
index b39f2db..7e3f91a 100644
--- a/mkdocs/docs/installation/unraid.md
+++ b/mkdocs/docs/installation/unraid.md
@@ -13,6 +13,7 @@ Tube Archivist, and all if it's dependencies are located in the [community appli
 This is the easiest container to setup of the thee, just make sure that you do not have any port conflicts, and that your `/data` is mounted to the correct path. The other containers will map to the same root directory (/mnt/user/appdata/TubeArchivist).
 
 If you need to install `TubeArchivist-RedisJSON`on a different port, you'll have to follow [these steps](docker-compose.md#redis-on-a-custom-port) later on when installing the `TubeArchivist` container.
+If you're running into port collision, recreate the steps outline in the [docker compose installation instructions.](https://docs.tubearchivist.com/installation/docker-compose/#redis-on-a-custom-port)
 
 Make sure and start Redis and the ElasticSearch containers approximately one minute before starting `TubeArchivist`