Homepage widget error (ETIMEDOUT / valid admin authorization token)

[LDannijs]

Hello!

I am trying to get the homepage widget for beszel working (https://gethomepage.dev/widgets/services/beszel/) but i am getting an error.

Going to the URL shows me:
{"code":401,"message":"The request requires valid admin authorization token to be set.","data":{}}

Here is how i have my service widget set up in homepage:

- Beszel:
      icon: sh-beszel-light.png
      href: http://192.168.1.75:8090/
      widget:
          type: beszel
          url: http://192.168.1.75:8090
          username: email
          password: password
          systemId: t082iox847jond2

[henrygd]

Hi, I didn't know this existed until now. That's neat. Thanks to whoever worked on this.

Looks like it's using the /api/admins/auth-with-password endpoint, so make sure you're using credentials for the admin account that you use to log into the PocketBase backend at /_/#/login.

[henrygd]

Pretty much. First create the network:

docker network create homepage_network

Then do what you showed, but also add a services block to identify the network:

services:
  homepage:
    networks:
      - homepage_network

networks:
  homepage_network:
    external: true

Do that for both files and bring them up again with docker compose up -d.

Then test connectivity again from the homepage container:

ping beszel
curl http://beszel:8090/api/admins/auth-with-password

[LDannijs]

Done all that, and it can ping it, but the curl still fails from inside the container: {"code":401,"message":"The request requires valid admin authorization token to be set.","data":{}}

Here are my compose files, might help you guys.

services:
  beszel:
    image: 'henrygd/beszel'
    container_name: 'beszel'
    restart: unless-stopped
    ports:
      - '8090:8090'
    environment:
      - CSP=frame-ancestors http://192.168.1.75:8090 http://192.168.1.75:3000
    volumes:
      - ./beszel_data:/beszel_data
    extra_hosts:
      - 'host.docker.internal:host-gateway'
    networks:
      - homepage_network

  beszel-agent:
    image: 'henrygd/beszel-agent'
    restart: unless-stopped
    network_mode: host
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      PORT: 45876
      KEY: 'ssh-ed25519 key'

networks:
  homepage_network:
    external: true

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    restart: unless-stopped
    ports:
      - 3000:3000
    volumes:
      - ./config:/app/config 
      - /var/run/docker.sock:/var/run/docker.sock 
    networks:
      - homepage_network

networks:
  homepage_network:
    external: true

[henrygd]

That's what you want!

The problem was that it couldn't connect at all before. Is the widget working in Homepage now by any chance?

[shamoon]

{"code":401,"message":"The request requires valid admin authorization token to be set.","data":{}} is expected since you're not actually passing the token, the curl was to test connectivity. It sounds like actually it is working now. The final thing is to change your homepage config to use that host, e.g.

....
    widget:
        url: http://beszel:8090

[LDannijs]

🥳 you guys are amazing. Thank you so much!

Is there a reason these containers need to be on the same network? Is my issue a specific edge case? since there isn't any documentation explaining this.

[henrygd]

No worries!

I'm not sure why the IP didn't work in this case. Sometimes using a LAN address that's outside the internal docker network does work, as long as the port is exposed correctly. But as a general rule, putting containers in a shared network is the most reliable way to connect them.

Thanks @shamoon for helping and for adding a Beszel widget to Homepage.

[LDannijs]

Thank you for making Beszel as well @henrygd. Despite its infancy its a great tool to have and works great!