Unable to get zulip-0 pod ready

I am deploying Zulip locally in China. I encountered a problem that zulip-0 pod is unable to be ready as READY column shows it's always 0/1 even after numerous restart attempts by the Minikube. I have reset the whole running period from 5 min to more than 15min, and the problem persists. When I run the describe command, it seems there is always the message: Startup probe failed: HTTP probe failed with statuscode: 403 `PS C:\Users\18014\docker-zulip-main\kubernetes\chart\zulip> kubectl describe pod zulip-0 Name: zulip-0 Namespace: default Priority: 0 Service Account: zulip Node: minikube/192.168.49.2 Start Time: Mon, 12 Jan 2026 10:58:53 +0800 Labels: app.kubernetes.io/instance=zulip app.kubernetes.io/name=zulip apps.kubernetes.io/pod-index=0 controller-revision-hash=zulip-76b695f649 statefulset.kubernetes.io/pod-name=zulip-0 Annotations: kubectl.kubernetes.io/restartedAt: 2026-01-12T10:05:09+08:00 Status: Running IP: 10.244.0.18 IPs: IP: 10.244.0.18 Controlled By: StatefulSet/zulip Containers: zulip: Container ID: docker://8a3eb1f311bfa4b89d09a648760f06ca98b2c25b7e05594952dab9b9cf52cd56 Image: zulip/docker-zulip:11.4-0 Image ID: docker-pullable://zulip/docker-zulip@sha256:5a5af5cc92efec9b817827241fb6a76a86b4da06ad84257418adb640dc1ec258 Ports: 25/TCP (smtp), 80/TCP (http), 443/TCP (https) Host Ports: 0/TCP (smtp), 0/TCP (http), 0/TCP (https) State: Running Started: Mon, 12 Jan 2026 12:21:32 +0800 Last State: Terminated Reason: Completed Exit Code: 0 Started: Mon, 12 Jan 2026 12:05:03 +0800 Finished: Mon, 12 Jan 2026 12:21:32 +0800 Ready: False Restart Count: 5 Liveness: http-get http://:http/health delay=10s timeout=5s period=10s #success=1 #failure=3 Startup: http-get http://:http/health delay=120s timeout=5s period=5s #success=1 #failure=180 Environment: DB_HOST: zulip-postgresql DB_HOST_PORT: 5432 DB_USER: zulip SETTING_MEMCACHED_LOCATION: zulip-memcached:11211 SETTING_RABBITMQ_HOST: zulip-rabbitmq SETTING_REDIS_HOST: zulip-redis-headless SECRETS_rabbitmq_password: ChTF SECRETS_postgres_password: ChTF SECRETS_memcached_password: ChTF SECRETS_redis_password: ChTF SECRETS_secret_key: ChTF DISABLE_HTTPS: true SECRETS_email_password: 123456789 SETTING_EMAIL_HOST: SETTING_EMAIL_HOST_USER: noreply@example.com SETTING_EMAIL_PORT: 587 SETTING_EMAIL_USE_SSL: False SETTING_EMAIL_USE_TLS: True SETTING_EXTERNAL_HOST: zulip.local SETTING_ZULIP_ADMINISTRATOR: admin@example.com SSL_CERTIFICATE_GENERATION: self-signed TRUST_GATEWAY_IP: true ZULIP_AUTH_BACKENDS: EmailAuthBackend Mounts: /data from zulip-persistent-storage (rw) /data/post-setup.d from zulip-post-setup-scripts (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-gwvbw (ro) Conditions: Type Status PodReadyToStartContainers True Initialized True Ready False ContainersReady False PodScheduled True Volumes: zulip-persistent-storage: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: zulip-data ReadOnly: false zulip-post-setup-scripts: Type: ConfigMap (a volume populated by a ConfigMap) Name: zulip-post-setup-scripts Optional: false kube-api-access-gwvbw: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt Optional: false DownwardAPI: true QoS Class: BestEffort Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Killing 6m52s (x5 over 73m) kubelet Container zulip failed startup probe, will be restarted Normal Pulled 6m44s (x6 over 89m) kubelet Container image "zulip/docker-zulip:11.4-0" already present on machine Normal Created 6m44s (x6 over 89m) kubelet Created container: zulip Normal Started 6m44s (x6 over 89m) kubelet Started container zulip Warning Unhealthy 41s (x951 over 87m) kubelet Startup probe failed: HTTP probe failed with statuscode: 403`