"cannot read properties of null"/broken UI upon fresh install via jc21/nginx-proxy-manager:latest

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
Brand new shiny install via docker compose. No stale data directories, and the container was brought up w/ docker compose up --force-recreate --build

After the initial administrative user creation, the the web gui is for all intents an purposes, unusable. Clicking the hosts tab bings up a small blank menu:

I also notice the user is displayed oddly.

"Standard user"? -- I thought that was supposed to be "Administrator"

These errors are also appearing in the docker logs:

app-1  | [9/9/2026] [8:30:06 PM] [Express  ] › ℹ  info      Creating a new user in setup mode
app-1  | [9/9/2026] [8:30:07 PM] [Express  ] › ⚠  warning   Cannot read properties of null (reading 'id')
app-1  | [9/9/2026] [8:30:07 PM] [Remote Version] › ℹ  info      Fetching https://api.github.com/repos/NginxProxyManager/nginx-proxy-manager/releases/latest
app-1  | [9/9/2026] [8:30:07 PM] [Access   ] › ✖  error     reports:hosts 1 Permission Denied
app-1  | [9/9/2026] [8:30:08 PM] [Express  ] › ⚠  warning   Cannot read properties of null (reading 'id')
app-1  | [9/9/2026] [8:30:08 PM] [Access   ] › ✖  error     reports:hosts 1 Permission Denied
app-1  | [9/9/2026] [8:30:10 PM] [Express  ] › ⚠  warning   Cannot read properties of null (reading 'id')
app-1  | [9/9/2026] [8:30:11 PM] [Access   ] › ✖  error     reports:hosts 1 Permission Denied
app-1  | [9/9/2026] [8:30:15 PM] [Express  ] › ⚠  warning   Cannot read properties of null (reading 'id')
app-1  | [9/9/2026] [8:30:15 PM] [Access   ] › ✖  error     reports:hosts 1 Permission Denied
Gracefully Stopping... press Ctrl+C again to force

Nginx Proxy Manager Version
2.15.1, however I get the behavior with every version I've tried from 2.13.0 and later. 2.12.6 appears to be "functional"
Note that installing via 2.12.6, and then upgrading to 2.13.0 causes the behavior to re-appear.

Strangely, I have a much older instance of nginx proxy manager that has been upgraded numerous times, and is running 2.15.1 successfully.

I do notice the host OS, on the working version is still back on Rocky 9.5, but I thought that was the point of docker to abstract those host OS variables out? I can snapshot it, and then try a host OS upgrade to see if it breaks the install.

To Reproduce
Steps to reproduce the behavior:

1. Use the attached docker-compose.yml in an empty directory.
2. docker compose up --force-recreate --build
3. Create initial administrative user.
4. Click host tab. It fails.

Expected behavior
Beyond the vague hope of it spitting out a winning lottery number? :-) I'd like to create the first proxy host.

Screenshots
See attachments.

Operating System
Host OS is: "Rocky Linux 9.8 (Blue Onyx)"

docker/docker compose are from the Microsoft moby repositories.

[root@docker03 nginx-proxy-manager]# docker compose version
Docker Compose version 5.5.0-1
[root@docker03 nginx-proxy-manager]# docker version
Client:
Version: 29.7.2-2
API version: 1.55
Go version: go1.26.6
Git commit: a7dcaa6fdb6ed04aacbfdc76357fdae01605609e
Built: Mon Aug 17 00:00:00 2026
OS/Arch: linux/amd64
Context: default

Server:
Engine:
Version: 29.7.2-2
API version: 1.55 (minimum version 1.40)
Go version: go1.26.6
Git commit: 6a43e3d5afddf4111da0f864bbc7cae5d7e95001
Built: Mon Aug 17 00:00:00 2026
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 2.3.4-2
GitCommit: db8809540e1a7a9da5d518876894933ff55692ab
runc:
Version: 1.5.1-9
GitCommit: 8f2685a471d3347a686ad3909783d8aafc6bb208
docker-init:
Version: 0.19.0
GitCommit:

Additional context
docker-compose.yml

Start with the attached docker-compose.yml and reproduce the issue on a fresh install using the listed Docker commands. Trace initial administrative-user creation and the reports:hosts permission errors alongside the browser failure and null-id warnings. Done means a new installation shows the user as Administrator, opens the Hosts tab, and allows creation of the first proxy host without these errors.