lub
/
mailu
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Update index.rst

Browse Source
master
Fionera 5 years ago committed by GitHub
parent e46153c0b1
commit 7a8395c927
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File

4
docs/kubernetes/mailu/index.rst
Unescape Escape View File

@ -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 - 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. - 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) - 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 .. code:: bash
kubectl -n mailu-mailserver get po kubectl -n mailu-mailserver get po
kubectl -n mailu-mailserver delete po/mailu-imap... kubectl -n mailu-mailserver delete po/mailu-admin...
Happy mailing! Happy mailing!

Write Preview
Loading…
Cancel
Save