Web UI 403 Forbidden Error after this morning's auto-update to Zabbix 7.0.0rc3

[DaveS]

Hello!
I was auto-updated this morning to Zabbix 7.0.0rc3. Zabbix-server and Zabbix-agent are up and running, but now I get a 403 Forbidden error when trying to access the Web UI. Not a firewall issue.

Any idea on how to restore and also how to avoid this from happening after each auto-update?

[DaveS]

Figured it out - had to update httpd.conf with the following:

<Directory />
AllowOverride none
Require all granted
</Directory>

[jkrauze]

You're using Apache for the webserver I assume? I have the same issue however I'm using nginx and I'm not exactly certain how to 'translate' this fix.

[kbrown900]

I have the same issue, but I cant find an httpd.conf file anywhere (no /etc/httpd at all apparently) is there a different location I should be looking?

[jkrauze]

I have the same issue, but I cant find an httpd.conf file anywhere (no /etc/httpd at all apparently) is there a different location I should be looking?

If you didn't choose Apache as your front-end you won't have an httpd.conf file. I'm also using nginx and I haven't found the corresponding solution for this. I'm hoping some more people are having this issue and may have a resolution / fix for it.

[pussycaat]

Hello!
I was auto-updated this morning to Zabbix 7.0.0rc3. Zabbix-server and Zabbix-agent are up and running, but now I get a 403 Forbidden error when trying to access the Web UI. Not a firewall issue.

Any idea on how to restore and also how to avoid this from happening after each auto-update?

Hello! I have same problem. zabbix7.0.0rc3 + nginix
I fixed strings in config

/etc/nginx/conf.d/zabbix.conf

add ui. because with new update files was migrated from /usr/share/zabbix/ to /usr/share/zabbix/ui

root /usr/share/zabbix/ui;
fastcgi_param DOCUMENT_ROOT /usr/share/zabbix/ui;
fastcgi_param SCRIPT_FILENAME /usr/share/zabbix/ui$fastcgi_script_name;
fastcgi_param PATH_TRANSLATED /usr/share/zabbix/ui$fastcgi_script_name;​

and restart nginx.service. Enjoy!
It's helps me, but I don't sure it's correct example to resolve this problem.

[Markku]

I think I saw the same error after upgrading 7.0.0rc2 to 7.0.0rc3. The solution was to restart Apache (sudo systemctl restart apache2).

Markku

[kbrown900]

I think I saw the same error after upgrading 7.0.0rc2 to 7.0.0rc3. The solution was to restart Apache (sudo systemctl restart apache2).

Markku

Did not work for me unfortunately. I did notice however prior to the upgrade my /usr/share/zabbix folder was full of files, and after there is only 2 folders and none of the php files...

[jkrauze]

Did not work for me unfortunately. I did notice however prior to the upgrade my /usr/share/zabbix folder was full of files, and after there is only 2 folders and none of the php files...

My installation was using nginx, so there's some fundamental configuration differences, but I've had no luck so far either. I did manage to get to the login screen by manually putting in URLs, such as https://www.domain.com/ui/index.php and attempted a SAML login, but it's broken after that. It's almost like either there was a folder permissions change, or some sort of "web url root folder" change or something like that.

[Markku]

A long shot, but have you tried uninstalling the frontend/web/apache/nginx-related Zabbix packages and then reinstall them? (plus of course restarting the services)

Be sure to backup the configuration files under /etc/zabbix (especially web) first.

Markku

[kbrown900]

A long shot, but have you tried uninstalling the frontend/web/apache/nginx-related Zabbix packages and then reinstall them? (plus of course restarting the services)

Be sure to backup the configuration files under /etc/zabbix (especially web) first.

Markku

Took a shot at the reinstall and I believe it seems to have worked! I did an apt purge (after backing up /web) of the frontend and reinstalled and it seems to have worked! I had to reset the permissions of the "zabbix.conf.php" file but other than that it seems to be running correctly now. Many thanks for the suggestion!

[espenta]

Had same sort of problem using Debian and going from rc1 to rc3. Got access denied on the web frontend after upgrade.

The apache log did not find the zabbix.php file, so it have been moved down to a /ui/ folder on my system after upgrade.
Setting this as root folder in apache sites-enabled fixed it for us:
DocumentRoot /usr/share/zabbix/ui

[Markku]

FYI I'm using Debian, and didn't have to make any of those modifications (and my /etc/apache2/conf-enabled/zabbix.conf has an Alias directive for /usr/share/zabbix/ui). So if you end up having to modify Zabbix-provided configuration files, maybe you are using some manually created configuration otherwise as well. That's totally fine of course. Or, maybe the upgrade procedure from rc1 to rc3 did something strange while rc2 to rc3 worked fine.

Markku

[RafalB]

Had same sort of problem using Debian and going from rc1 to rc3. Got access denied on the web frontend after upgrade.

The apache log did not find the zabbix.php file, so it have been moved down to a /ui/ folder on my system after upgrade.
Setting this as root folder in apache sites-enabled fixed it for us:
DocumentRoot /usr/share/zabbix/ui

That exactly what happened in my case on Ubuntu Server.
Thank you for sharing your discovery!