Skip to content

Zulip server not able to connect to database #494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
saad946 opened this issue Apr 11, 2025 · 5 comments
Open

Zulip server not able to connect to database #494

saad946 opened this issue Apr 11, 2025 · 5 comments

Comments

@saad946
Copy link

saad946 commented Apr 11, 2025 •
edited
Loading

Title: Zulip Pod Stuck in CrashLoopBackOff - "Waiting for database server to allow connections..."
`Executing Zulip configuration ...

Description: We are deploying Zulip in a Kubernetes cluster. All the dependencies (PostgreSQL, Redis, RabbitMQ, Memcached) are running and healthy, but the Zulip container is stuck in a crash loop. From the logs, it seems to be waiting for a database connection indefinitely, and then restarts.

Problem: Zulip fails at the bootstrap phase with the following log message:

=== Begin Bootstrap Phase === Waiting for database server to allow connections ... 

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: zulip
  namespace: zulip
spec:
  serviceName: "zulip"
  replicas: 1
  selector:
    matchLabels:
      app: zulip
  template:
    metadata:
      labels:
        app: zulip
    spec:
      containers:
      - name: zulip
        image: zulip/docker-zulip:10.1-0
        ports:
        - containerPort: 80
        - containerPort: 443
        envFrom:
        - configMapRef:
            name: zulip-env
        volumeMounts:
        - name: zulip-storage
          mountPath: /data
        resources:
          limits:
            cpu: "1"
            memory: 2Gi
          requests:
            cpu: "500m"
            memory: 1Gi
  volumeClaimTemplates:
  - metadata:
      name: zulip-storage
    spec:
      accessModes: ["ReadWriteOnce"]
      resources:
        requests:
          storage: 20Gi
      storageClassName: standard



apiVersion: v1
kind: ConfigMap
metadata:
  name: zulip-env
  namespace: zulip
data:
  DB_HOST: "database"
  DB_HOST_PORT: "5432"
  DB_USER: "zulip"
  POSTGRES_DB: "zulip"
  POSTGRES_USER: "zulip"
  POSTGRES_PASSWORD: "BbAhcpK3tByeYUV"
  RABBITMQ_DEFAULT_USER: "zulip"
  RABBITMQ_DEFAULT_PASS: "wMYHr9n0xmVMkHq"
  MEMCACHED_PASSWORD: "uADWGsdvKew7S5I"
  REDIS_PASSWORD: "97uQnHDjijCVVVB"

  SSL_CERTIFICATE_GENERATION: "self-signed"
  SETTING_MEMCACHED_LOCATION: "memcached.zulip.svc.cluster.local:11211"
  SETTING_RABBITMQ_HOST: "rabbitmq.zulip.svc.cluster.local"
  SETTING_REDIS_HOST: "redis.zulip.svc.cluster.local"
  SETTING_REMOTE_POSTGRES_HOST: "postgres.zulip.svc.cluster.local"

  SECRETS_rabbitmq_password: "wMYHr9n0xmVMkHq"
  SECRETS_postgres_password: "BbAhcpK3tByeYUV"
  SECRETS_memcached_password: "uADWGsdvKew7S5I"
  SECRETS_redis_password: "97uQnHDjijCVVVB"
  SECRETS_secret_key: "<redacted>"



kubectl get svc -n zulip

NAME        TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)        AGE
memcached   ClusterIP      34.118.227.118   <none>          11211/TCP      12m
postgres    ClusterIP      34.118.232.92    <none>          5432/TCP       12m
rabbitmq    ClusterIP      34.118.239.178   <none>          5672/TCP       12m
redis       ClusterIP      34.118.235.145   <none>          6379/TCP       12m
zulip       LoadBalancer   34.118.237.206   34.42.150.178   80:30887/TCP   8m




kubectl get pods -n zulip

NAME                         READY   STATUS             RESTARTS      AGE
memcached-6895d6bb4c-kj4t2   1/1     Running            0             12m
postgres-0                   1/1     Running            0             12m
rabbitmq-0                   1/1     Running            0             12m
redis-546b47bf66-scpqw       1/1     Running            0             12m
zulip-0                      0/1     CrashLoopBackOff   4 (25s ago)   8m

All databases are using same config map for simplicity,

Highly appreciate if someone can help us out in this.
@saad946
Copy link
Author

saad946 commented Apr 11, 2025

After setting DB_HOST: "database" to "postgres.zulip.svc.cluster.local"
zulip can connect to database but now facing issue while accessing its UI

Image

@saad946
Copy link
Author

saad946 commented Apr 11, 2025

These are zulip server logs, and also they are stuck at this point

=== Begin Initial Configuration Phase ===
Preparing and linking the uploads folder ...
Prepared and linked the uploads directory.
Executing puppet configuration ...
Disabling https in nginx.
/usr/lib/x86_64-linux-gnu/rubygems-integration/3.2.0/gems/ruby-augeas-0.5.0/lib/augeas.rb:48: warning: undefining the allocator of T_DATA class Augeas
Notice: Compiled catalog for zulip-0.zulip.zulip.svc.cluster.local in environment production in 3.96 seconds
Notice: /Stage[main]/Zulip::Profile::Base/File[/etc/zulip/settings.py]/ensure: created
Notice: /Stage[main]/Zulip::Profile::Base/File[/etc/zulip/zulip-secrets.conf]/ensure: created
Notice: /Stage[main]/Zulip::App_frontend_base/File[/etc/zulip/uwsgi.ini]/content: content changed '{sha256}1dd85be94be70e2d8eacd46de695d0c3d7cc3fd947ee8cddf622275ffeeaf887' to '{sha256}5cb676ae4bd709706063625cbecbc5ec759290f26edb0f14b66c8a494019a613'
Notice: /Stage[main]/Zulip::App_frontend_base/File[/etc/nginx/zulip-include/s3-cache]/content: content changed '{sha256}e7ce5a61cbb36a4f71e17cb4c78a1aad417adb6c9f42ca62112db63b3c06201d' to '{sha256}2b29ccea2734bc5db74e218ed94c8dca3f26ae66f3ee3bab21c2bd663ca56a5c'
Notice: /Stage[main]/Zulip::Profile::App_frontend/File[/etc/nginx/sites-available/zulip-enterprise]/content: content changed '{sha256}1d508d3290ccbff4c6a3005f2c0182a028b80e5a9b76b3369838d3914a224405' to '{sha256}afded9a8fddbac084843c64934f8f7863580aefd6354e0468a1c3c95de536238'
Notice: /Stage[main]/Zulip::Nginx/Service[nginx]: Triggered 'refresh' from 2 events
Notice: /Stage[main]/Zulip::Supervisor/Service[supervisor]: Triggered 'refresh' from 1 event
Notice: Applied catalog in 0.54 seconds
Executing nginx configuration ...
Nginx configuration succeeded.
Certificates configuration succeeded.
Setting database configuration ...
Setting key "REMOTE_POSTGRES_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "REMOTE_POSTGRES_PORT", type "string" in file "/etc/zulip/settings.py".
Setting key "REMOTE_POSTGRES_SSLMODE", type "string" in file "/etc/zulip/settings.py".
Database configuration succeeded.
Setting Zulip secrets ...
Generating Zulip secrets ...
generate_secrets: No new secrets to generate.
Secrets generation succeeded.
Zulip secrets configuration succeeded.
Activating authentication backends ...
Setting key "AUTHENTICATION_BACKENDS", type "array" in file "/etc/zulip/settings.py".
Adding authentication backend "EmailAuthBackend".
Authentication backend activation succeeded.
Executing Zulip configuration ...
Setting key "EMAIL_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "EMAIL_HOST_USER", type "string" in file "/etc/zulip/settings.py".
Setting key "EMAIL_PORT", type "integer" in file "/etc/zulip/settings.py".
Setting key "EMAIL_USE_SSL", type "bool" in file "/etc/zulip/settings.py".
Setting key "EMAIL_USE_TLS", type "bool" in file "/etc/zulip/settings.py".
Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
Setting key "POSTGRES_USER", type "string" in file "/etc/zulip/settings.py".
Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "RABBITMQ_USER", type "string" in file "/etc/zulip/settings.py".
Setting key "RATE_LIMITING", type "bool" in file "/etc/zulip/settings.py".
Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "REDIS_PORT", type "integer" in file "/etc/zulip/settings.py".
Setting key "REMOTE_POSTGRES_HOST", type "string" in file "/etc/zulip/settings.py".
Setting key "REMOTE_POSTGRES_PORT", type "integer" in file "/etc/zulip/settings.py".
Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
Zulip configuration succeeded.
Auto backup enabled.
=== End Initial Configuration Phase ===
=== Begin Bootstrap Phase ===
Waiting for database server to allow connections ...
Executing Zulip first start init ...
First Start Init not needed. Continuing.
Running new database migrations...
Operations to perform:
  Apply all migrations: analytics, auth, confirmation, contenttypes, otp_static, otp_totp, phonenumber, sessions, social_django, zerver
Running migrations:
  No migrations to apply.
Database migrations completed.
Post setup scripts execution ...
No post-setup.d folder found. Continuing.
=== End Bootstrap Phase ===
=== Begin Run Phase ===
Starting Zulip using supervisor with "/etc/supervisor/supervisord.conf" config ...

Certbot is not scheduled to run.
2025-04-11 13:26:17,381 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-04-11 13:26:17,382 WARN No file matches via include "/etc/supervisor/conf.d/*.conf"
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/cron.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/go-camo.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/nginx.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/smokescreen.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/zulip-once.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/zulip.conf" during parsing
2025-04-11 13:26:17,382 INFO Included extra file "/etc/supervisor/conf.d/zulip/zulip_db.conf" during parsing
2025-04-11 13:26:17,386 INFO RPC interface 'supervisor' initialized
2025-04-11 13:26:17,386 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-04-11 13:26:17,386 INFO supervisord started with pid 1
2025-04-11 13:26:18,389 INFO spawned: 'go-camo' with pid 317
2025-04-11 13:26:18,391 INFO spawned: 'smokescreen' with pid 318
2025-04-11 13:26:18,393 INFO spawned: 'zulip-django' with pid 319
2025-04-11 13:26:18,395 INFO spawned: 'zulip-tus' with pid 320
2025-04-11 13:26:18,398 INFO spawned: 'zulip-katex' with pid 321
2025-04-11 13:26:18,401 INFO spawned: 'zulip-tornado' with pid 322
2025-04-11 13:26:18,403 INFO spawned: 'zulip_deliver_scheduled_emails' with pid 323
2025-04-11 13:26:18,406 INFO spawned: 'zulip_deliver_scheduled_messages' with pid 324
2025-04-11 13:26:18,484 INFO spawned: 'process-fts-updates' with pid 325
2025-04-11 13:26:18,487 INFO spawned: 'cron' with pid 326
2025-04-11 13:26:18,490 INFO spawned: 'nginx' with pid 327
2025-04-11 13:26:18,494 INFO spawned: 'zulip_events_deferred_work' with pid 328
2025-04-11 13:26:18,584 INFO spawned: 'zulip_events_digest_emails' with pid 329
2025-04-11 13:26:18,587 INFO spawned: 'zulip_events_email_mirror' with pid 330
2025-04-11 13:26:18,590 INFO spawned: 'zulip_events_embed_links' with pid 331
2025-04-11 13:26:18,593 INFO spawned: 'zulip_events_embedded_bots' with pid 332
2025-04-11 13:26:18,597 INFO spawned: 'zulip_events_email_senders' with pid 333
2025-04-11 13:26:18,687 INFO spawned: 'zulip_events_deferred_email_senders' with pid 334
2025-04-11 13:26:18,690 INFO spawned: 'zulip_events_missedmessage_emails' with pid 335
2025-04-11 13:26:18,693 INFO spawned: 'zulip_events_missedmessage_mobile_notifications' with pid 336
2025-04-11 13:26:18,784 INFO spawned: 'zulip_events_outgoing_webhooks' with pid 337
2025-04-11 13:26:18,787 INFO spawned: 'zulip_events_thumbnail' with pid 338
2025-04-11 13:26:18,791 INFO spawned: 'zulip_events_user_activity' with pid 339
2025-04-11 13:26:18,794 INFO spawned: 'zulip_events_user_activity_interval' with pid 340
2025-04-11 13:26:18,795 INFO reaped unknown pid 316 (exit status 0)
2025-04-11 13:26:19,884 INFO success: go-camo entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,884 INFO success: smokescreen entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,884 INFO success: zulip-django entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,884 INFO success: zulip-tus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,884 INFO success: zulip-katex entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,884 INFO success: zulip-tornado entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_deliver_scheduled_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_deliver_scheduled_messages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: process-fts-updates entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_deferred_work entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_digest_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_email_mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_embed_links entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_embedded_bots entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_email_senders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_deferred_email_senders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_missedmessage_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_missedmessage_mobile_notifications entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_outgoing_webhooks entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_thumbnail entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_user_activity entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-11 13:26:19,885 INFO success: zulip_events_user_activity_interval entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

@saad946
Copy link
Author

saad946 commented Apr 11, 2025

Thats the error log:

saad@cloudshell:~$ kubectl exec -it zulip-0 -n zulip -- /bin/bash
root@zulip-0:/# cat /var/log/zulip/django.log | tail -n 100
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.22; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:10.087 INFO [zr] 172.21.1.22     GET     500  4.7s (+start: 198ms) /register/ (unauth@root via Mozilla)
[pid: 376|app: 0|req: 1/3] 172.21.1.22 () {80 vars in 1593 bytes} [Fri Apr 11 13:42:05 2025] GET /register/ => generated 0 bytes in 4901 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:08.685 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.22; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:10.986 INFO [zr] 172.21.1.22     GET     500  2.5s (+start: 100ms) /register/ (unauth@root via Mozilla)
[pid: 383|app: 0|req: 2/4] 172.21.1.22 () {80 vars in 1592 bytes} [Fri Apr 11 13:42:08 2025] GET /register/ => generated 0 bytes in 2599 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:07.387 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.22; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:11.186 INFO [zr] 172.21.1.22     GET     500  7.3s (+start: 498ms) /register/ (unauth@root via Mozilla)
[pid: 380|app: 0|req: 1/5] 172.21.1.22 () {80 vars in 1593 bytes} [Fri Apr 11 13:42:03 2025] GET /register/ => generated 0 bytes in 7800 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:11.185 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.26; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:11.295 INFO [zr] 172.21.1.26     GET     500 210ms (+start: 98ms) /register/ (unauth@root via Mozilla)
[pid: 383|app: 0|req: 3/6] 172.21.1.26 () {80 vars in 1593 bytes} [Fri Apr 11 13:42:10 2025] GET /register/ => generated 0 bytes in 308 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:11.400 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.26; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:11.589 INFO [zr] 172.21.1.26     GET     500 192ms (+start: 101ms) /register/ (unauth@root via Mozilla)
[pid: 383|app: 0|req: 4/7] 172.21.1.26 () {80 vars in 1592 bytes} [Fri Apr 11 13:42:11 2025] GET /register/ => generated 7078 bytes in 294 msecs (HTTP/1.1 500) 4 headers in 156 bytes (1 switches on core 0)
2025-04-11 13:42:11.688 INFO [zr] 172.21.1.26     GET     404 501ms (db: 193ms/2q) /favicon.ico (unauth@root via Mozilla)
[pid: 380|app: 0|req: 2/8] 172.21.1.26 () {76 vars in 1462 bytes} [Fri Apr 11 13:42:11 2025] GET /favicon.ico => generated 0 bytes in 501 msecs (HTTP/1.1 404) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:08.695 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 172.21.1.26; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:11.786 INFO [zr] 172.21.1.26     GET     500  3.1s (+start: 98ms) /register/ (unauth@root via Mozilla)
[pid: 385|app: 0|req: 2/9] 172.21.1.26 () {80 vars in 1593 bytes} [Fri Apr 11 13:42:08 2025] GET /register/ => generated 0 bytes in 3200 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:10.396 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 10.168.1.1; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:12.786 INFO [zr] 10.168.1.1      GET     500  2.6s (+start: 100ms) /register/ (unauth@root via Mozilla)
[pid: 376|app: 0|req: 2/10] 10.168.1.1 () {80 vars in 1590 bytes} [Fri Apr 11 13:42:10 2025] GET /register/ => generated 0 bytes in 2698 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)
2025-04-11 13:42:13.092 ERR  [django.request] Internal Server Error: /register/
Traceback (most recent call last):
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/.venv/lib/python3.12/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = middleware_method(
               ^^^^^^^^^^^^^^^^^^
  File "/home/zulip/deployments/2025-03-29-01-42-39/zerver/middleware.py", line 683, in process_view
    raise ProxyMisconfigurationError(proxy_state_header)
zerver.middleware.ProxyMisconfigurationError: Reverse proxy misconfiguration: No proxies configured in Zulip, but proxy headers detected from proxy at 10.168.1.1; see https://zulip.readthedocs.io/en/latest/production/reverse-proxies.html
2025-04-11 13:42:13.285 INFO [zr] 10.168.1.1      GET     500  3.0s (+start: 296ms) /register/ (unauth@root via Mozilla)
[pid: 389|app: 0|req: 1/11] 10.168.1.1 () {80 vars in 1590 bytes} [Fri Apr 11 13:42:09 2025] GET /register/ => generated 0 bytes in 3298 msecs (HTTP/1.1 500) 4 headers in 0 bytes (0 switches on core 0)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@saad946