LDAPWeb/Zammad/docs/issues.md

Issues — Zammad

Terakhir Diperbarui: 2026-07-02

---

Known Issues

PostgreSQL 10.100.1.25 — PG 12, tidak kompatibel Zammad 7

• Status: Blocker untuk DB eksternal di .25
• Gejala: zammad-init loop / migrasi gagal saat POSTGRES_HOST=10.100.1.25
• Penyebab: Server .25 menjalankan PostgreSQL 12.12; Zammad 7 membutuhkan PostgreSQL 13+
• Workaround saat ini: Gunakan bundled PostgreSQL 17 di stack Docker (zammad-postgresql container)
• Solusi jangka panjang: Upgrade PG di .25 ke 13+ lalu migrasi DB Zammad

Elasticsearch 9 — CPU tidak support x86-64-v2

• Status: ES dinonaktifkan (ELASTICSEARCH_ENABLED=false)
• Gejala: Container zammad-elasticsearch crash: Fatal glibc error: CPU does not support x86-64-v2
• Dampak: Full-text search Zammad terbatas / nonaktif sampai ES kompatibel
• Opsi: Upgrade CPU VM Proxmox (host flags), atau deploy ES versi lama di host terpisah

storage.yml permission (container user zammad)

• Status: Fixed saat install
• Gejala: Permission denied @ rb_sysopen - /opt/zammad/config/storage.yml
• Fix: chmod 644 config/storage.yml di host (bukan 600 root-only)

CSRF token verification failed (setup wizard)

• Status: Fixed 2026-07-02
• Gejala: Error saat Create admin di wizard https://zammad.gisportal.id
• Penyebab: Nginx host terminate SSL; Zammad internal nginx pakai $scheme = http → cookie secure tidak cocok
• Fix: Tambah NGINX_SERVER_SCHEME=https + NGINX_SERVER_NAME=zammad.gisportal.id di .env, restart stack
• Ref: Zammad env vars

OSS upload 503 immediately after bucket create

• Status: Known / workaround
• Gejala: PutObject gagal 503 Service Unavailable tepat setelah createBucket
• Penyebab: QNAP QuObjects perlu waktu singkat setelah container baru dibuat
• Workaround: Retry 3–5x dengan jeda 3 detik (lihat scripts/oss-create-bucket.php)

---

LDAP sync — 3 user failed, 3 skipped

• Status: Open — minor, tidak blocking
• Gejala: First sync 64 user — 3 failed, 3 skipped
• Penyebab umum: atribut mail kosong di AD, akun service/disabled, duplikasi email
• Tindakan: Cek di System → Integrations → LDAP → Recent Logs; perbaiki AD; Start new

LDAP menu tidak muncul / URL tidak respon

• Status: Fixed 2026-07-02
• Gejala: User cari LDAP di Settings → Security (SAML) atau URL #settings/integration/ldap
• Penyebab: Zammad 7 memisahkan menu Settings vs System; LDAP ada di System → Integrations
• Fix: Gunakan https://zammad.gisportal.id/#system/integration/ldap

---

SMTP — SSL_read unexpected eof / DNS gagal di container

• Status: Fixed 2026-07-03
• Gejala:
  • sc138.idcloudhosting.cloud (465/587): SSL_read: unexpected eof while reading
  • sc138.idcloudhosting.cloud (587): getaddrinfo: No address associated with hostname
• Penyebab: DNS di dalam container Docker Zammad (127.0.0.11) tidak bisa resolve hostname eksternal. Koneksi SMTP gagal sebelum/saat TLS handshake.
• Fix: Tambah DNS resolver host di docker-compose.override.yml:

  dns:
    - 203.142.82.222
    - 203.142.84.222
  

  pada zammad-railsserver, zammad-scheduler, zammad-websocket, zammad-nginx — lalu docker compose up -d.
• Setelah fix: Uji ulang SMTP di Channels → Email dengan:

Field	Nilai
Host	sc138.idcloudhosting.cloud
Port	465
SSL	Yes (implicit)
SSL verification	Yes
User	support@geonet.co.id

Port 587 = STARTTLS (bukan SSL implicit) — jika dipakai, mode SSL harus STARTTLS, bukan SSL.

---

Fixed

Issue	Tanggal
SMTP DNS container Docker	2026-07-03
LDAP menu / URL salah	2026-07-02
CSRF setup wizard	2026-07-02
storage.yml permission	2026-07-02