NPM widget reporting wrong data

[mathieutreves]

Description

The NPM widget works without errors, but it reports an incorrect number for "enabled" and "disabled" proxies, while the "total" one is right. They total one is even correctly updated if I delete or add some proxy, while the other two remains at 0 all the time. There are no errors in the homepage logs.

homepage version

v0.9.11 (2245cdd)

Installation method

Docker

Configuration

- Nginx Proxy Manager:
        icon: /icons/nginx-proxy-manager.svg
        href: "{{HOMEPAGE_VAR_NPM_ADDRESS}}"
        server: my-docker 
        container: nginx
        widget:
            type: npm
            url: "{{HOMEPAGE_VAR_NPM_DOCKER}}"
            username: "{{HOMEPAGE_VAR_NPM_USERNAME}}"
            password: "{{HOMEPAGE_VAR_NPM_PASSWORD}}"

Container Logs

No response

Browser Logs

No response

Troubleshooting

/app # curl -L -k -u 'username:password' http://IP:81/api/nginx/proxy-hosts
{"error":{"code":403,"message":"Permission Denied"}}/app #

[shamoon]

/app # curl -L -k -u 'username:password' http://IP:81/api/nginx/proxy-hosts
{"error":{"code":403,"message":"Permission Denied"}}/app #

is not really helpful for anyone to try and answer this.

In general homepage just uses whatever data an api returns, indeed in this case:

homepage/src/widgets/npm/component.jsx

Lines 24 to 26 in 912ae0a

	const enabled = infoData.filter((c) => !!c.enabled).length;
	const disabled = infoData.filter((c) => !c.enabled).length;
	const total = infoData.length;

[shamoon]

Im saying if you want help you need to post the output of npm

[shamoon]

Which in this case you can get from your browser network tab, btw

[mathieutreves]

In the GET request for the NPM widget, in the response all the proxies have the correct info for their enabled state. Eg this one is the only host that is disabled, all the other ones have "enabled":true

{
    "id":18,  
    "created_on":"2024-11-04 21:12:42",
    "modified_on":"2024-11-04 21:15:28",
    "owner_user_id":1,
    "domain_names":["domain.com"],
    "forward_host":"192.168.8.1",
    "forward_port":443,
    "access_list_id":0,
    "certificate_id":1,
    "ssl_forced":true,
    "caching_enabled":false,
    "block_exploits":true,
    "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":false,
    "locations":[],
    "hsts_enabled":true,
    "hsts_subdomains":true
}

[shamoon]

I can't reproduce any issue here and no one else has reported it.

[
    {
        "id": 1,
        "created_on": "2024-10-16 14:51:35",
        "modified_on": "2024-10-16 14:51:36",
        "owner_user_id": 1,
        "domain_names": [
            "example.org"
        ],
        "forward_host": "localhost",
        "forward_port": 80,
        "access_list_id": 0,
        "certificate_id": 0,
        "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
    },
    {
        "id": 2,
        "created_on": "2024-10-16 14:53:16",
        "modified_on": "2024-10-16 14:53:19",
        "owner_user_id": 1,
        "domain_names": [
            "example2.org"
        ],
        "forward_host": "localhost",
        "forward_port": 81,
        "access_list_id": 0,
        "certificate_id": 0,
        "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": false,
        "locations": [],
        "hsts_enabled": false,
        "hsts_subdomains": false
    }
]

[mathieutreves]

Ok, thank you for trying

[marcolino7]

Hi,
I have same Issue, and as I saw was introduced by an update on NPM:

[shamoon]

Then I will ask you too to post the API output.

I tried above using latest and could not reproduce anything.

[marcolino7]

Then I will ask you too to post the API output.

I tried above using latest and could not reproduce anything.

Hi recreating the container does not help. Can you suggest me on how to collect the API output? Thanks

[seirdotexe]

Same here!

Homepage v0.9.11
NPM v2.12.1

[shamoon]

Nope

Try re-creating, not restarting, your containers

[chriswa81]

I can also confirm the error. Furthermore, this error was already reported 3 weeks ago (#4138) and should be known.

[shamoon]

Wow somehow I didn’t even remember doing all of that, ha. Thanks for the reminder, and sorry for forgetting.

I can put out a release later today, folks can use the dev image in the meantime which already has the fix.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.