"Uncaught TypeError: Cannot read properties of null (reading 'avatar')" When attempting to view several UI elements

[FatherOfCurses]

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
When attempting to view the following UI features, a blank page is displayed and the error "Uncaught TypeError: Cannot read properties of null (reading 'avatar')" displays in the console.

• /nginx/proxy (Proxy hosts)
• /certificates (Certificates)

Other UI sections will display.

The offending minified code appears to be at index-CGMbvQTG.js,

function $a({data: e, isFetching: t, onDelete: r, onRenew: n, onDownload: a, isFiltered: i}) { const l = Lr() , u = g.useMemo( () => [l.accessor(o => o.owner, { id: "owner", cell: o => { const f = o.getValue(); return c.jsx(Cr, { url: f.avatar, name: f.name }) }

Nginx Proxy Manager Version
v2.13.0

To Reproduce
Steps to reproduce the behavior:

1. Log in to Nginx Proxy Manager.
2. Click "Proxy Hosts" card or select "Hosts -> Proxy Hosts" from the menu
   Alternate bug behavior - Select "Certificates" from the menu

Expected behavior
The correct UI elements should display

Operating System
Using Nginx Proxy Manager in a Docker container on an Ubuntu Linux server.
Accessing via a Vivaldi browser on an Arch Linux system. Also tested with Firefox on Arch Linux and Vivaldi on Mac.
No errors in docker container logs.

[jc21]

Can you visit the Proxy Hosts page, open your browsers' dev tools, hard refresh the page and tell me:

1. if you see /api/nginx/proxy-hosts?expand=owner%2Caccess_list%2Ccertificate request in the network tab?
2. if so, do you see a "owner" property on the result of each proxy host item?

[phixxy]

I am having this issue as well.

1. I see the request
2. No I do not. Some of the owners are null.

At one point I remember forgetting my password and doing something to delete it and reset it, which I remember impacting the UI before, but wasn't a real issue for me. I may have deleted the whole account and set a new admin account or something. I assume this is related as the proxy host items with correct owner properties were all made after I reset the password/account. I will just reinstall npm since I am 99% sure that is the issue based on this information.

[FatherOfCurses]

Most of my entries are like this:

{
    "id": 21,
    "created_on": "2025-08-17 14:42:21",
    "modified_on": "2025-08-17 14:42:22",
    "owner_user_id": 2,
    "domain_names": [
        "spadina.289lake.com"
    ],
    "forward_host": "10.0.0.3",
    "forward_port": 80,
    "access_list_id": 0,
    "certificate_id": 8,
    "ssl_forced": false,
    "caching_enabled": false,
    "block_exploits": false,
    "advanced_config": "",
    "meta": {
        "letsencrypt_agree": false,
        "dns_challenge": false,
        "nginx_online": true,
        "nginx_err": null
    },
    "allow_websocket_upgrade": false,
    "http2_support": false,
    "forward_scheme": "http",
    "enabled": true,
    "locations": [],
    "hsts_enabled": false,
    "hsts_subdomains": false,
    "owner": {
        "id": 2,
        "created_on": "2025-04-07 17:33:34",
        "modified_on": "2025-11-04 17:05:53",
        "is_disabled": false,
        "email": "{nginxuseremail}",
        "name": "Colin Principe",
        "nickname": "Admin",
        "avatar": "//www.gravatar.com/avatar/0f9291e9a81c3f0f2d96f45c77b6ecc8?default=mm",
        "roles": [
            "admin"
        ]
    },
    "access_list": null,
    "certificate": {
        "id": 8,
        "created_on": "2025-04-06 20:19:01",
        "modified_on": "2025-10-04 08:04:49",
        "owner_user_id": 1,
        "is_deleted": false,
        "provider": "letsencrypt",
        "nice_name": "289lake.com, *.289lake.com",
        "domain_names": [
            "*.289lake.com",
            "289lake.com"
        ],
        "expires_on": "2026-01-02 11:06:13",
        "meta": {}
    }
}

but then some are like this:

{
    "id": 1,
    "created_on": "2025-04-06 13:58:48",
    "modified_on": "2025-04-10 13:27:28",
    "owner_user_id": 1,
    "domain_names": [
        "portainer.289lake.com"
    ],
    "forward_host": "10.0.0.5",
    "forward_port": 19443,
    "access_list_id": 0,
    "certificate_id": 8,
    "ssl_forced": true,
    "caching_enabled": false,
    "block_exploits": false,
    "advanced_config": "",
    "meta": {
        "letsencrypt_agree": false,
        "dns_challenge": false,
        "nginx_online": true,
        "nginx_err": null
    },
    "allow_websocket_upgrade": true,
    "http2_support": true,
    "forward_scheme": "https",
    "enabled": true,
    "locations": [],
    "hsts_enabled": true,
    "hsts_subdomains": true,
    "owner": null,
    "access_list": null,
    "certificate": {
        "id": 8,
        "created_on": "2025-04-06 20:19:01",
        "modified_on": "2025-10-04 08:04:49",
        "owner_user_id": 1,
        "is_deleted": false,
        "provider": "letsencrypt",
        "nice_name": "289lake.com, *.289lake.com",
        "domain_names": [
            "*.289lake.com",
            "289lake.com"
        ],
        "expires_on": "2026-01-02 11:06:13",
        "meta": {}
    }
}

[jc21]

Thanks @phixxy that was helpful, seems like this is possible when a user is deleted but they own other items.

Looking into it

[phixxy]

Glad to help, just reinstalled and set everything back up. The new UI is nice, thanks for the software. Have a great day!

[FatherOfCurses]

Wow! Amazing turnaround!

Confirmed that the docker image refreshed and my nginx server updated and hosts and certificates are displaying correctly.