From 7a8395c927aee56123b6a6d523f18075afe0e317 Mon Sep 17 00:00:00 2001 From: Fionera Date: Mon, 30 Sep 2019 19:24:44 +0200 Subject: [PATCH] Update index.rst --- docs/kubernetes/mailu/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/kubernetes/mailu/index.rst b/docs/kubernetes/mailu/index.rst index ab5f3ca4..6068fb9c 100644 --- a/docs/kubernetes/mailu/index.rst +++ b/docs/kubernetes/mailu/index.rst @@ -211,11 +211,11 @@ If the login problem still persists, or more specific, happens now and then and - Depending on your network configuration you could still see some ``allow_nets check failed`` results in the logs. This means that the IP is not allowed a login - If this is happening your network plugin has troubles with the Nginx Ingress Controller using the ``hostNetwork: true`` option. Known cases: Flannel and Calico. - You should uncomment ``POD_ADDRESS_RANGE`` in the ``configmap.yaml`` file and add the IP range of your pod network bridge (the range that sadly has failed the ``allowed_nets`` test) -- Delete the IMAP pod and wait for it to restart +- Delete the Admin pod and wait for it to restart .. code:: bash kubectl -n mailu-mailserver get po - kubectl -n mailu-mailserver delete po/mailu-imap... + kubectl -n mailu-mailserver delete po/mailu-admin... Happy mailing!