From 46902bb2fbd99410de7aab9a7e9aa0f23e0383ae Mon Sep 17 00:00:00 2001
From: maxid <97409287+maxdorninger@users.noreply.github.com>
Date: Mon, 5 Jan 2026 17:09:52 +0100
Subject: [PATCH] add troubleshooting tips for Docker image pull issues

---
 Writerside/topics/troubleshooting.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/Writerside/topics/troubleshooting.md b/Writerside/topics/troubleshooting.md
index a529a20..5e8a650 100644
--- a/Writerside/topics/troubleshooting.md
+++ b/Writerside/topics/troubleshooting.md
@@ -43,4 +43,15 @@ your media library, hard linking will not work.
 - If you configured a category with a special save path,
   <a href="qBittorrent-Category.md">carefully read this page about MM with qBittorrent save paths.</a>
 
-<note>If it still doesn't work, <a href="https://github.com/maxdorninger/MediaManager/issues">please open an Issue.</a> It is possible that a bug is causing the issue.</note>
\ No newline at end of file
+<note>If it still doesn't work, <a href="https://github.com/maxdorninger/MediaManager/issues">please open an Issue.</a> It is possible that a bug is causing the issue.</note>
+
+## Docker Image Pull Issues
+
+- If you get a 401 or 403 error when pulling the image from GHCR, this is not a permission issue with the
+  repository/image. It errors because your Docker client is misconfigured.
+- This is not a MediaManager issue per se, so please don't open an issue about this on the MediaManager GitHub repo.
+
+### Possible Fixes:
+
+- [Unable to pull image from GitHub Container Registry (Stack Overflow)](https://stackoverflow.com/questions/74656167/unable-to-pull-image-from-github-container-registry-ghcr)
+- [Try pulling the image from Quay.io](configuration-overview.md#mediamanager-and-metadatarelay-docker-images)