aboutsummaryrefslogtreecommitdiff
path: root/articles/2025/Mailcow-Docker-too-many-requests.html
blob: 619879ac0deb4514980e42bf360f91dbe3b1ed6a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<!doctype html>
<html lang="EN">
  <head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <link rel="stylesheet" href="/style.css">
    <title>Mailcow Docker too many requests</title>
  </head>
  <body>
    <header>
      <h1>Bloggings</h1>
      <a href="/index.php">Back</a>
      
    </header>
    
<main>
<article>
<h2>Mailcow Docker too many requests</h2>
<h3>2025-04-29</h3>
<h4>Dcker changes</h4>
<p>While updating Mailcow this morning Docker gave me a "too many requests" error.</p>
<p>It seems that Docker now limits the IPv6’s subnet instead of the IPv6 address itself, which 
could mean your pull limit is shared.</p>
<p>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.</p>
<p><a href="https://hub.docker.com/signup">Docker account creation</a></p>
<p>Once the account created, copy the personal access token, go back to your server and enter docker login -u (login)</p>
<p>Mailcow will now update without error.</p>
</article>
</main>
<footer>

<p>&nbsp;</p>

<p>§</p>
  </footer>
</body>
</html>