[BUG] - SnappyMail automaticly log out after few seconds
Describe the bug Hey. I'm having a problem with Snappy Mail. It logs me out after a few seconds. It logs in correctly, shows me my sent messages, and after a moment (a few seconds) it logs me out and returns to the login page.
Expected behavior Do not log out automatically.
Environment (please complete the following information):
- Helm Chart Version: [2.4.0]
- Helm Version: [e.g., v3.12.3]
- Kubernetes Version: [e.g., 1.32.1]
- Kubernetes Platform: [Self Hosted]
- Mailu Version: [2024.06.43]
Values.yaml Configuration
Please provide your values.yaml configuration file or the relevant parts of it (ensure sensitive data is redacted).
webmail:
## @param webmail.enabled Enable deployment of webmail
enabled: true
## @param webmail.uri URI to access webmail
uri: /webmail
## @param webmail.type Type of webmail to deploy (`roundcube` or `snappymail`)
type: snappymail
## @param webmail.roundcubePlugins List of Roundcube plugins to enable
roundcubePlugins:
- archive
- zipdownload
- markasjunk
- managesieve
- enigma
- carddav
- mailu
## @param webmail.logLevel Override default log level
logLevel: "DEBUG"
## Pod image
## @param webmail.image.repository Pod image repository
## @param webmail.image.tag Pod image tag (defaults to mailuVersion if set, otherwise Chart.AppVersion)
## @param webmail.image.pullPolicy Pod image pull policy
image:
repository: mailu/webmail
tag: ""
pullPolicy: IfNotPresent
## Pod persistence (if not using single_pvc)
## @param webmail.persistence.size Pod pvc size
## @param webmail.persistence.storageClass Pod pvc storage class
## @param webmail.persistence.accessModes Pod pvc access modes
## @param webmail.persistence.claimNameOverride Pod pvc name override
## @param webmail.persistence.annotations Pod pvc annotations
persistence:
size: 20Gi
storageClass: dataclass
accessModes: [ReadWriteOnce]
claimNameOverride: ""
annotations: {}
## Pod resource requests and limits
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## We usually recommend not to specify default resources and to leave this as a conscious
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube. If you do want to specify resources, uncomment the following
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
## @param webmail.resources.limits The resources limits for the container
## @param webmail.resources.requests The requested resources for the container
##
resources:
## Example:
## limits:
## cpu: 200m
## memory: 200Mi
limits: {}
## Examples:
## requests:
## cpu: 100m
## memory: 100Mi
requests: {}
## Liveness probe values
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
## @param webmail.livenessProbe.enabled Enable livenessProbe
## @param webmail.livenessProbe.failureThreshold Failure threshold for livenessProbe
## @param webmail.livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
## @param webmail.livenessProbe.periodSeconds Period seconds for livenessProbe
## @param webmail.livenessProbe.successThreshold Success threshold for livenessProbe
## @param webmail.livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
livenessProbe:
enabled: true
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
## Readiness probe values
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
## @param webmail.readinessProbe.enabled Enable readinessProbe
## @param webmail.readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
## @param webmail.readinessProbe.periodSeconds Period seconds for readinessProbe
## @param webmail.readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
## @param webmail.readinessProbe.failureThreshold Failure threshold for readinessProbe
## @param webmail.readinessProbe.successThreshold Success threshold for readinessProbe
readinessProbe:
enabled: true
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
## Startup probe values
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes
## @param webmail.startupProbe.enabled Enable startupProbe
## @param webmail.startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
## @param webmail.startupProbe.periodSeconds Period seconds for startupProbe
## @param webmail.startupProbe.timeoutSeconds Timeout seconds for startupProbe
## @param webmail.startupProbe.failureThreshold Failure threshold for startupProbe
## @param webmail.startupProbe.successThreshold Success threshold for startupProbe
startupProbe:
enabled: false
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
## @param webmail.podLabels Add extra labels to pod
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
podLabels: {}
## @param webmail.podAnnotations Add extra annotations to the pod
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
podAnnotations: {}
## ref: https://kubernetes.io/docs/user-guide/node-selection/
## @param webmail.nodeSelector Node labels selector for pod assignment
nodeSelector: {}
## @param webmail.initContainers Add additional init containers to the pod
## ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
## e.g:
## initContainers:
## - name: your-image-name
## image: your-image
## imagePullPolicy: Always
## command: ['sh', '-c', 'echo "hello world"']
initContainers: []
## @param webmail.priorityClassName Pods' priorityClassName
priorityClassName: ""
## @param webmail.podSecurityContext.enabled Enabled pods' Security Context
## @param webmail.podSecurityContext.fsGroup Set pods' Security Context fsGroup
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
podSecurityContext:
enabled: false
fsGroup: 1001
## @param webmail.containerSecurityContext.enabled Enabled containers' Security Context
## @param webmail.containerSecurityContext.runAsUser Set containers' Security Context runAsUser
## @param webmail.containerSecurityContext.runAsNonRoot Set container's Security Context runAsNonRoot
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
containerSecurityContext:
enabled: false
runAsUser: 1001
runAsNonRoot: false
## @param webmail.terminationGracePeriodSeconds In seconds, time given to the pod to terminate gracefully
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods
terminationGracePeriodSeconds: 2
## @param webmail.affinity Affinity for webmail pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
affinity: {}
## @param webmail.tolerations Tolerations for pod assignment
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []
## @param webmail.revisionHistoryLimit Configure the revisionHistoryLimit of the deployment
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#revision-history-limit
revisionHistoryLimit: 3
## @param webmail.hostAliases Pod pod host aliases
## ref: https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
hostAliases: []
## @param webmail.schedulerName Name of the k8s scheduler (other than default)
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
schedulerName: ""
# Service parameters
service:
## @param webmail.service.annotations Admin service annotations
annotations: {}
## @param webmail.topologySpreadConstraints Topology Spread Constraints for pod assignment
## ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
topologySpreadConstraints: []
## Strategy to use to update Pods
## @param webmail.updateStrategy.type Can be set to RollingUpdate or OnDelete
updateStrategy:
type: RollingUpdate
## @param webmail.extraEnvVars Extra environment variable to pass to the running container
## For example:
# extraEnvVars:
# - name: MAILU_FRONT_SERVICE_PORT_SMTP_AUTH
# value: "587"
# extraEnvVars: []
## @param webmail.extraEnvVarsCM Name of existing ConfigMap containing extra environment variables to mount in the pod
extraEnvVarsCM: ""
## @param webmail.extraEnvVarsSecret Name of existing Secret containing extra environment variables to mount in the pod
extraEnvVarsSecret: ""
## @param webmail.extraVolumeMounts Optionally specify extra list of additional volumeMounts for the pod
extraVolumeMounts: []
## @param webmail.extraVolumes Optionally specify extra list of additional volumes for the pod(s)
extraVolumes: []
## @param webmail.extraContainers Add additional containers to the pod
extraContainers: []
Additional information Log from Front Pod:
[25/Sep/2025:10:43:58 +0200] "POST /webmail/?/Json/&q[]=/0/ HTTP/1.1" 200 63 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /sso/logout HTTP/1.1" 302 279 "https://mailu.pl/webmail/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /sso/login?url=https://mailu.pl/sso/logout HTTP/1.1" 200 2219 "https://mailu.pl/webmail/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /static/vendor.css HTTP/1.1" 304 0 "https://mailu.pl/sso/login?url=https://mailu.pl/sso/logout" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /static/app.css HTTP/1.1" 304 0 "https://mailu.pl/sso/login?url=https://mailu.pl/sso/logout" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /static/app.js HTTP/1.1" 304 0 "https://mailu.pl/sso/login?url=https://mailu.pl/sso/logout" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0"
[25/Sep/2025:10:43:58 +0200] "GET /static/vendor.js HTTP/1.1" 304 0 "https://mailu.pl/sso/login?url=https://mailu.pl/sso/logout" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36 Edg/140.0.0.0
Round Cube works fine.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Have you checked https://github.com/Mailu/Mailu/issues/3689 ?