debian 13 apache2 update breaks zabbix apache2 config

[sperkins74]

Hello All

The latest apache2 fix in debian13 release breaks the zabbix config.

apache fires an error on the entry ProxyTimeout 300 /etc/zabbix/apache.conf and does not start.

i have tried reinstalling the previous version of apache but oddly... same issue

i have tried a vanilla install of zabbix 7 on a fresh debian 13 (which of course installs the latest apache version), and i have the same issue.

if i comment out ProxyTimeout 300 the site seems not associated with php, however some troubleshooting provides a quick workaround

comment out
ProxyTimeout 300

and

<FilesMatch \.(php|phar)$>
SetHandler "proxy:unix:/var/run/php/zabbix.sock|fcgi://localhost"
</FilesMatch>

and restart apache2

and zabbix is back, however i am not sure if the above workaround is good enough.

Is anyone else having this issue with zabbix ? other non zabbix websites we have are fine

Thanks
Sebastian

[troffasky]

What is the actual error logged by Apache about this line of config?

[sperkins74]

the full discussion is here :

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/513274-zabbix-7-0-26-update-on-ubuntu-22-04

long story short, the latest zabbix release (v7 in my case) delivered a php-fpm apache conf instead of php, i suspect the zabbix installation to reload apache...

2 days later apache patch got applied, restarts apache2, which fails

[Antimidas]

The problem is specific to 7.0.26. It does not exist with 7.025 or earlier. It appears it has to do with their switching from mod_php to php-fpm. There is a bug being tracked at https://support.zabbix.com/browse/ZBX-27764. I have seen a few people come up with workarounds, but my preference is to wait for them to fix it and stick w ith 7.0.25 for the front-end servers. I had no issues with 7.0.26 on t he database and server instances.

[LDZPLN1]

I ran into the same issue this morning I narrowed it down to Apache failing to start as well. I enabled proxy_http (a2enmod proxy_http) which got rid of the proxytimeout error, but caused PHP pages to not be interpreted and served as raw text.

I fixed it by grabbing the apache.conf file off a working install prior to the 7.0.26 update and copied it to my /etc/zabbix folder and restarted Apache. That resolved everything for me.

[solution]

Same problem here after updating to 7.4.10.
Since I already had php-fpm, I needed to restart php-fpm to recognize the new "zabbix" pool.

Wellington

[irontmp]

I ran into the same issue this morning and, while checking 5 lions megaways demo argentina, I narrowed it down to Apache failing to start as well. I enabled proxy_http (a2enmod proxy_http), which got rid of the ProxyTimeout error, but caused PHP pages to not be interpreted and served as raw text.

I fixed it by grabbing the apache.conf file off a working install prior to the 7.0.26 update and copied it to my /etc/zabbix folder and restarted Apache. That resolved everything for me.

Yes, I’m seeing the same issue. It appears to be related to the new Zabbix Apache config expecting PHP-FPM. Commenting out those lines works if PHP is already handled another way, but it is more of a workaround than a proper fix. Check the actual PHP socket with: ls -l /run/php/ Then either update the Zabbix Apache config to use the correct socket, or remove the PHP-FPM handler if you are using mod_php. Also run: apache2ctl -t before restarting Apache.

[kaileyketchum]

Hi Sebastian,

This looks related to recent Apache 2.4 changes where some proxy directives behave differently or require the correct modules enabled (especially mod_proxy_fcgi and updated syntax handling for ProxyTimeout in certain builds).

Since it affects fresh installs too, it’s likely not a Zabbix issue but an Apache packaging change in Debian 13. I would double-check enabled modules and compare /etc/apache2/mods-enabled/ between working and broken setups.

Also worth testing with a minimal vhost to confirm whether the directive itself is being rejected or just the combined config.

I haven’t seen this in other setups like ios dash, so it may be specific to how Debian patched Apache.

Your workaround is valid as a temporary fix, but I’d treat it as a config compatibility issue rather than a Zabbix problem.