Error on homepage nginx widget

[JGNi]

Hi
I'm trying to see which features this could give me https://gethomepage.dev/v0.7.2/widgets/services/nginx-proxy-manager/
But keeps ending up with this error:
API Error: Unknown error
URL: http://192.168.1.2:81/api/tokens
Raw Error:
{
"errno": -113,
"code": "EHOSTUNREACH",
"syscall": "connect",
"address": "192.168.1.2",
"port": 81
}
Any suggestions to what could be wrong?

[brypie]

I have this widget working fine - can you post your configuration for your one?
Looks like you may have the wrong url/IP address?

[JGNi]

• Nginx Proxy Manager:
  icon: nginx.png
  href: http://192.168.1.2:81
  description: Proxy
  widget:
  type: npm
  url: http://192.168.1.2
  username: [email protected]
  password: some_password

I use email and password as I use in http://192.168.1.2:81 to log in with.

[JGNi]

[JGNi]

I've also tried with :81 in the end

[brypie]

- Nginx Proxy Manager:
        icon: nginx.png
        href: my_url (https)/  ## trainling slash
        ping: my_url (https)  ## no trailing slash
#        description: Reverse Proxy Manager
        server: local
        container: nginx-proxy-manager
        widget:
            type: npm
            url: my_url (https)  ## no trailing slash
            username: [email protected]
            password: some_password

That's my whole setup for Nginx Proxy Manager in Homepage
Don't know if you need https in the url (I do)

[JGNi]

Not working. With the following config, without widget part:
- Nginx Proxy Manager:
icon: nginx.png
href: http://192.168.1.2:81/
ping: http://192.168.1.2
description: Proxy
container: Nginx-Proxy-Manager-Official

I get this:

With widget just API error.

[brypie]

Ok - let's break it down.

When you click on the above part of your homepage, does it link out to your nginx instance? If so, the first url is correct.

To get the ping working - you will need to add the port to the end of the url

If you get that working, then show the code for the widget...?

[brypie]

Just a thought - are you hosting homepage on the same server/network as nginx?

Yes - you would need the port number specified in the widget url if you are accessing via IP address.
(I have my nginx serving its own proxy address)

[fa-ve]

Running NPMPlus, a fork from NPM but does do the same:

My config:

- NPM Proxy:
    href: https://192.168.xxx.x:81
    ping: https://192.168.xxx.x:81
    icon: /icons/npm.png
    description: Reverse Proxy Manager
    server: unraid
    container: Nginx-Proxy-Manager-Plus
    showStats: false
    widget:
        type: npm
        url: https://192.168.xxx.x:81
        username: [email protected]
        password: [your password]

[JGNi]

- Nginx Proxy Manager:
        icon: nginx.png
        href: my_url (https)/  ## trainling slash
        ping: my_url (https)  ## no trailing slash
#        description: Reverse Proxy Manager
        server: local
        container: nginx-proxy-manager
        widget:
            type: npm
            url: my_url (https)  ## no trailing slash
            username: [email protected]
            password: some_password

That's my whole setup for Nginx Proxy Manager in Homepage Don't know if you need https in the url (I do)

Thanks. Looking at it now.

[creakypuppet]

Did this get resolved? Got the same issue after updating the NPM docker container.

This is the widget setup, the username & password work fine to login with. Clicking on the widget also redirects to the correct URL. If it helps I updated to v2.11.1, nothing else has been changed.

- NPM:
    icon: nginx.png
    href: http://192.168.1.26:82
    ping: http://192.168.1.26:82
    description: NPM
    widget:
      type: npm
      url: http://192.168.1.26:82
      username: [email protected]
      password: PASS

[JGNi]

Still not working here

[creakypuppet]

Mine is working fine now, redeployed both containers and now works.

[error420]

Still not working here

1. Make sure homepage is added to the npm network in addition to the existing network it lives on.
2. Use the Docker container name and port instead of the IP.

widget:
type: npm
url: http://npm-app-1:81
username: your username
password: your password
fields: ["enabled", "disabled", "total"]

This is what solved it for me.

[danielwerner86]

I have the same issue. I have two separate NPM instances, and it seems it only works on one. I tried with different admin credentials but as far as I understand only one works after rebooting the Homepage container - the one who answers the first, maybe.

Homepage are saying nothing in the logs, only API error on the GUI.
The NPM logs say: "[10/27/2024] [6:49:36 PM] [Express ] › ⚠ warning invalid signature"

EDIT: I can confirm the above - if I comment out the working instance in the config file and reboot homepage, the other one starts working.