API Error Information

[nfkgdh]

Description

Hello !

I am new to homepage and selfhosting and I can't seem to get the widgets working. After a few seconds/minutes after refreshing the page, all my services are getting the API Error Information with 2 different error details.

Homepage is running in a docker container on Ubuntu Server, as are my other services. All containers are running and healthy.

(Edit : some formatting, I am a github newbie)

homepage version

v0.9.6 (805f119, Aug 11, 2024)

Installation method

Docker

Configuration

Docker Compose

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    environment:
      PUID: 1000
      PGID: 1000
    ports:
      - 3000:3000
    volumes:
      - ./config:/app/config
    restart: unless-stopped

services.yaml

- Media:
    - Plex:
        href: http://192.168.1.116:32400/
        description: Regarder films et séries
        icon: plex.png
        widget:
          type: tautulli
          url: http://192.168.1.116:11697
          key: apikey
          enableUser: true
          showEpisodeNumber: true
          expandOneStreamToTwoRows: false

    - qBittorrent:
        href: http://192.168.1.116:8080/
        description: Télécharger en toute sécurité
        icon: qbittorrent.png
        widget:
          type: qbittorrent
          url: http://192.168.1.116:8080
          username: user
          password: password
          leech: true
          download: true
          seed: true
          upload: true

    - Immich:
        href: http://192.168.1.116:2283/
        description: Voir et sauvegarder mes photos
        icon: immich.png
        widget:
           type: immich
           url: http://192.168.1.116:2283
           key: apikey
           users: false
           photos: true
           videos: true
           storage: true


    - Kiwix:
        href: http://192.168.1.116:23911/
        description: Lire et apprendre
        icon: kiwix-light.png


- Networking:
    - PiHole:
        href: http://192.168.1.116:800/admin
        description: DNS et DHCP
        icon: pi-hole.png
        widget:
          type: pihole
          url: http://192.168.1.116:800
          version: 5
          key: apikey

- Management:
    - Portainer:
        href: http://192.168.1.116:9000
        description: Gestion des conteneurs
        icon: portainer.png
        widget:
          type: portainer
          url: http://192.168.1.116:9000
          env: 2
          key: apikey
          running: true
          stopped: true
          total: true

Container Logs

[2024-09-04T11:57:50.489Z] error: <httpProxy> Error calling http://192.168.1.116:800/admin/api.php...
[2024-09-04T11:57:50.490Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:800
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 800
  }
]
[2024-09-04T11:57:50.492Z] error: <httpProxy> Error calling http://192.168.1.116:2283/api/server-info/stats...
[2024-09-04T11:57:50.493Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:2283
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 2283
  }
]
[2024-09-04T11:57:50.493Z] error: <credentialedProxyHandler> HTTP Error 500 calling http://192.168.1.116:2283/api/server-info/stats
[2024-09-04T11:57:50.494Z] error: <httpProxy> Error calling http://192.168.1.116:8080/api/v2/torrents/info...
[2024-09-04T11:57:50.494Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:8080
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 8080
  }
]
[2024-09-04T11:57:50.494Z] error: <qbittorrentProxyHandler> HTTP 500 getting data from qBittorrent.  Data: { error: [Object] }
[2024-09-04T11:57:50.495Z] error: <httpProxy> Error calling http://192.168.1.116:11697/api/v2...
[2024-09-04T11:57:50.495Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:11697
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 11697
  }
]
[2024-09-04T11:57:50.496Z] error: <httpProxy> Error calling http://192.168.1.116:2283/api/server-info/version...
[2024-09-04T11:57:50.496Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:2283
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 2283
  }
]
[2024-09-04T11:57:50.496Z] error: <credentialedProxyHandler> HTTP Error 500 calling http://192.168.1.116:2283/api/server-info/version
[2024-09-04T11:57:54.585Z] error: <httpProxy> Error calling http://192.168.1.116:9000/api/endpoints/2/docker/containers/json...
[2024-09-04T11:57:54.586Z] error: <httpProxy> [
  500,
  Error: connect ETIMEDOUT 192.168.1.116:9000
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '192.168.1.116',
    port: 9000
  }
]
[2024-09-04T11:57:54.586Z] error: <credentialedProxyHandler> HTTP Error 500 calling http://192.168.1.116:9000/api/endpoints/2/docker/containers/json?all=1
[2024-09-04T11:57:55.519Z] error: undefined
[2024-09-04T11:57:55.540Z] error: undefined

Browser Logs

No response

Troubleshooting

I followed the troubleshooting guide :

• I double checked the API keys and they are valid. Even tried recreating some to see if anything changes.

• It seems like i can ping the other containers from the homepage container (I'm not completely sure I used the right way though).

• Containers are on different networks but since I can reach them, I feel like it's not a problem.

• I could not run a curl command to check the API output because I was unable to install the command.

I feel like I tried everything I'm capable of and I am running out of ideas for what to try next.

[shamoon]

The fact that they all go off-line at the same time as highly suspicious for an networking problem (obviously) So it probably isn’t homepage per se

General putting containers that you want to be able to talk to each other other on the same network as a good idea. Then you can reference them using container_name instead of IP

Also basic things like re-create (not just restart) everything and update docker

[overflow-sudo]

Did you solve this? I have same issue

[NorthernScott]

I am having the same issue. I am running my instance on a Portainer LXC within Proxmox. I am having the API issue even with the internal "resources" information widget. The data will load correctly on page load but then I will get an API error after several seconds. Container logs only show 'Error: Undefined." No extra info in the debug log.

[NorthernScott]

I checked in the browser console and saw that I was getting a CORS error for each of the elements that was failing. My issue was being caused by a mismatch between the hostname and ip address that the container was running at.