Closed mwinters-stuff closed 1 year ago
Ran into the same behaviour, problem was for me that subnet:
didn't the podCIDR.
@redimp Thanks, that resolved it - I had the subnet
entry, as the default value but nothing worked until I removed the entry from the configuration.
Closing.
Found this issue, helped me fix a related issue.
I was experiencing an infinite redirect when loading the web mailer ( also at sso.php
). After login I would see a ERR_TOO_MANY_REDIRECTS
after a while.
But I was able to login to the admin dashboard.
I also had the subnet:
configured as default `. I tried just setting
subnet: ""` hoping it would configure itself which It didn't ;).
Then I saw the redme states that this has to be update.
For me since I was using microk8s + calico I was able to find the pods subnet by looking for CALICO_IPV4POOL_CIDR
in microk8s kubectl describe daemonset calico-node -n kube-system
.
Now everything seems to work as expected with a minimal configuration like this.
domain: $DOMAIN
hostnames:
- $DOMAIN
initialAccount:
enabled: true
domain: $DOMAIN
password: ...
username: ...
logLevel: INFO
limits:
authRatelimit:
ip: 100/minute;3600/hour
user: 100/day
messageSizeLimitInMegabytes: 200
persistence:
size: 100Gi
secretKey: ...
ingress:
tls: true
annotations:
cert-manager.io/cluster-issuer: $ISSUER_NAME
subnet: $SUBNET
Found this issue, helped me fix a related issue.
I was experiencing an infinite redirect when loading the web mailer ( also at
sso.php
). After login I would see aERR_TOO_MANY_REDIRECTS
after a while. But I was able to login to the admin dashboard.I also had the
subnet:
configured as default`. I tried just setting
subnet: ""` hoping it would configure itself which It didn't ;). Then I saw the redme states that this has to be update.For me since I was using microk8s + calico I was able to find the pods subnet by looking for
CALICO_IPV4POOL_CIDR
inmicrok8s kubectl describe daemonset calico-node -n kube-system
.Now everything seems to work as expected with a minimal configuration like this.
domain: $DOMAIN hostnames: - $DOMAIN initialAccount: enabled: true domain: $DOMAIN password: ... username: ... logLevel: INFO limits: authRatelimit: ip: 100/minute;3600/hour user: 100/day messageSizeLimitInMegabytes: 200 persistence: size: 100Gi secretKey: ... ingress: tls: true annotations: cert-manager.io/cluster-issuer: $ISSUER_NAME subnet: $SUBNET
I encountered the same problem, but changing the subnet does not help, what should I do?
Environment & Version
2.0.10, Installed via Helm Chart Have existing 1.x install working fine.
Environment
Kubernetes, Helm charts, Traefik proxy.
Version
2.0.10
Description
I have installed onto a fresh database, after a failed upgrade from 1.0.x.
When logging into the administration interface, that works perfectlly.
When attempting to login to WebMail, I get the error "Too Many Redirects", ERR_TOO_MANY_REDIRECTS.
Looking at the network debugging, "sso.php" is doing the redirects to itself.
General
Response Headers
Request Headers
Replication Steps
The configuration is fairly default, with the usual hostnames and database configuration..
The traefik ingress route is:
Observed behaviour
Unable to get to the webmail interface.
Expected behaviour
Expect to get to the webmail interface.
Logs
Unable to find anything relevant in the logs.