-
Type:
Problem report
-
Resolution: Unresolved
-
Priority:
Major
-
None
-
Affects Version/s: 7.4.9
-
Component/s: None
-
None
Affected product/component:
- Zabbix Docker images
- zabbix-web-nginx-pgsql (Alpine variants)
- Entrypoint libraries: templates/entrypoints/lib/php.sh, templates/entrypoints/lib/nginx.sh
Two regressions were introduced after entrypoint refactoring for Alpine web images:
HA regression (alpine-7.4.9)
Frontend falls back to default/static server host handling instead of DB-driven HA node selection behavior seen in 7.4.8.
HTTPS regression (alpine-latest, alpine-7.4-latest)
Web startup logs warning:
**** Impossible to enable HTTPS virtual host
even with valid cert files present.
Affected / Not Affected
Affected
- zabbix/zabbix-web-nginx-pgsql:alpine-7.4.9 (HA regression)
- zabbix/zabbix-web-nginx-pgsql:alpine-latest, alpine-7.4-latest (HTTPS vhost regression during the window before fix release)
Known good
- zabbix/zabbix-web-nginx-pgsql:alpine-7.4.8 (HA works as expected),
- zabbix/zabbix-web-nginx-pgsql:7.4-alpine-latest as reported by customer for HTTPS startup behavior
Reproduction steps:
- Run web container with PostgreSQL backend, HA server setup, and no explicit ZBX_SERVER_HOST override for HA autodetection.
- Use SSL cert volume mount at /etc/ssl/nginx containing ssl.crt, ssl.key, dhparam.pem.
- Compare image tags:
- alpine-7.4.8
- alpine-7.4.9
- alpine-latest / alpine-7.4-latest
Observed
- 7.4.9: frontend connects as if default/static server target is used, not DB-driven HA selection.
- alpine-latest / alpine-7.4-latest: warning Impossible to enable HTTPS virtual host; nginx SSL vhost not enabled.
Expected
- Same HA node resolution behavior as 7.4.8.
- HTTPS vhost enabled when required cert files exist and nginx_ssl.conf is present.