From 420ceb49b53a8fa9d8ba8443e42e50cd7bd7cea9 Mon Sep 17 00:00:00 2001 From: Philip Wittamore Date: Sun, 12 Jul 2026 11:08:50 +0200 Subject: update --- .../2025/Mailcow-Docker-too-many-requests.html | 38 ++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100755 articles/2025/Mailcow-Docker-too-many-requests.html (limited to 'articles/2025/Mailcow-Docker-too-many-requests.html') diff --git a/articles/2025/Mailcow-Docker-too-many-requests.html b/articles/2025/Mailcow-Docker-too-many-requests.html new file mode 100755 index 0000000..619879a --- /dev/null +++ b/articles/2025/Mailcow-Docker-too-many-requests.html @@ -0,0 +1,38 @@ + + + + + + + Mailcow Docker too many requests + + +
+

Bloggings

+ Back + +
+ +
+
+

Mailcow Docker too many requests

+

2025-04-29

+

Dcker changes

+

While updating Mailcow this morning Docker gave me a "too many requests" error.

+

It seems that Docker now limits the IPv6’s subnet instead of the IPv6 address itself, which +could mean your pull limit is shared.

+

To fix this you can create a personal account at docker.com, this will allow 200 image pulls per 6 hours. +My Mailcow installation does 7 pulls for an update.

+

Docker account creation

+

Once the account created, copy the personal access token, go back to your server and enter docker login -u (login)

+

Mailcow will now update without error.

+
+
+ + + -- cgit v1.3.1