Admin Webpage fails to update following upgrade

[brian.ward]

The issue I am facing:
Immediately following an upgrade to Pi-Hole:
The admin portal isn't updating any statistics.
I am able to "login" and edit settings, just cannot see any activity.
Yes I did clear the cache on my browser, and in fact downloaded a new browser to test.
The same outcome occurs

 DNS Queries all actually work, it's just the admin we portal that is not working post upgrade.

Details about my system:
Debian 10
Web front end is nginx instead of lighthttpd.

Pi-Hole: version = 5.2.4
Web Interface = 5.3.1
FTL = 5.5.1

What I have changed since installing Pi-hole:
Only ran:
pihole -up

I have tried to repair the install:
pihole -r
and
curl -sSL https://install.pi-hole.net | sudo bash

Debug Logs:
https://tricorder.pi-hole.net/te33usag1u
Server 1

https://tricorder.pi-hole.net/tnbiti2k3l
Server 2

[jfb]

You are running nginx, which is an unsupported web server. You will need to make some configuration changes to make this webserver work.

This thread may be of assistance:

Web Interface not reachable, pi-hole itself is working

Output for pihole -r pihole -r [✓] Root user check .;;,. .ccccc:,. :cccclll:. ..,, :ccccclll. ;ooodc 'ccll:;ll .oooodc .;cll.;;looo:. .. ','. .',,,,,,'. .',,,,,,,,,,. .',,,,,,,,,,,,.... ....''',,,,,,,'....... ......... .... ......... .......... .......... .......... .......... ......... .... ......... .…

[brian.ward]

Thanks for the rapid response.

Just wanted to re-state that this was all working prior to upgrading to the latest version of Pi-Hole.

Also I more or less followed the pihole documentation to do just this.

https://docs.pi-hole.net/guides/webserver/nginx/

While it's not the "Default" install, it's commonly used enough to have developer documentation.

[jfb]

@brian.ward

it's commonly used enough to have developer documentation.

That is not developer documentation. As noted on the web page:

• This is an unsupported configuration created by the community

Edit - because of very limited developer resources, some configurations are not officially supported by the developers, but will work with Pi-hole if configured properly. Because they are not supported, we don't test our installer and updater to work when those webservers are used. Something in the update process may have overwritten a configuration file you are using for nginx.