Beszel install help

[Cyberwasp]

Has anyone installed Beszel. It's a container used to monitor the nas. Trying it using the yaml file however, it keeps stopping and starting. I looked at the logs but no clues. TIA

 

[Rusty]

Can you share the compose file and the logs?

 

[Cyberwasp]

Here's the compose file, s for the logs do you mean the ones in container manager, "if so it just shows me starting and stopping it. I just noticed something, maybe running the wrong compose file, not sure. I don't have an Nvidia but those are marked as comments.


services:
beszel:
image: 'henrygd/beszel'
container_name: 'beszel'
restart: unless-stopped
ports:
- '8090:8090'
volumes:
- ./beszel_data:/beszel_data
extra_hosts:
- 'host.docker.internal:host-gateway'
beszel-agent:
image: 'henrygd/beszel-agent' #Add -nvidia for nvidia gpus
container_name: 'beszel-agent'
restart: unless-stopped
network_mode: host
# runtime: nvidia # when using beszel-agent-nvidia
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
PORT: 45876
KEY: '...'
# FILESYSTEM: /dev/sda1 # set to the correct filesystem for disk I/O stats
# NVIDIA_VISIBLE_DEVICES: all # when using beszel-agent-nvidia
# NVIDIA_DRIVER_CAPABILITIES: utility # when using beszel-agent-nvidia

 

[Cyberwasp]

Found the log, it's from the Beszel-agent :
2026/03/20 01:56:19 Failed to load public keys:failed to parse key: ..., error: ssh: no key found

 

[jwd630]

You'll get the key value from your Beszel hub, which you'll have to have set up separately somewhere, perhaps in another container.

Did you actually put that value in the compose file? The log entry makes me think you literally have '...' in there. Once you have the hub set up you'll add a system to it, a process that includes generating a public key that the client uses to authenticate to your hub. Lots of non-Synology specific information Beszel | Simple, lightweight server monitoring.

 

[Cyberwasp]

I didn't put anything in the file. Copied from Github, pasted and built as the video suggested. I think this one's beyond my skill level, so I'll skip it, buy thank you!

 

[dimfil]

I didn't put anything in the file. Copied from Github, pasted and built as the video suggested. I think this one's beyond my skill level, so I'll skip it, buy thank you!

I used compose file from here and it worked OK. Select the appropriate compose file to deploy both hub and agent in the same project and update KEY and TOKEN variables as described there.

 

[Cyberwasp]

I tried your compose file and got the same results. the container starts and stops about 5 seconds later and loops.

 

[dimfil]

I tried your compose file and got the same results. the container starts and stops about 5 seconds later and loops.

You should have two containers starting, beszel and beszel-agent. Beszel will start and beszel-agent will stop on first deploy. Then you have to edit token and key as you will get from hub when you press "Add System" and then redeploy the compose file. Remember to use /beszel_socket/beszel.sock as Host/IP in the Add System window.
I hope you have used the correct docker compose file which deploys both hub and agent. Just to be sure, it is the following, and my advice is to replace relative paths (the "dot" in volume path definition) with absolute ones e.g. - ./beszel_data:/beszel_data will become - /volume1/docker/beszel_data:/beszel_data. Remember to create the folders in advance.

services:
  beszel:
    image: henrygd/beszel:latest
    container_name: beszel
    restart: unless-stopped
    environment:
      APP_URL: http://localhost:8090
    ports:
      - 8090:8090
    volumes:
      - ./beszel_data:/beszel_data
      - ./beszel_socket:/beszel_socket

  beszel-agent:
    image: henrygd/beszel-agent:latest
    container_name: beszel-agent
    restart: unless-stopped
    network_mode: host
    volumes:
      - ./beszel_agent_data:/var/lib/beszel-agent
      - ./beszel_socket:/beszel_socket
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      LISTEN: /beszel_socket/beszel.sock
      HUB_URL: http://localhost:8090
      TOKEN: <token>
      KEY: "<key>"

Edit: Just for reference, my current compose file is as follows:

services:
  beszel:
    image: henrygd/beszel:latest
    container_name: beszel
    restart: unless-stopped
    ports:
      - 8091:8090
    volumes:
      - /volume2/docker/beszel/beszel_data:/beszel_data
      - /volume2/docker/beszel/beszel_socket:/beszel_socket

  beszel-agent:
    image: henrygd/beszel-agent:latest
    container_name: beszel-agent
    restart: unless-stopped
    network_mode: host
    volumes:
      - /volume2/docker/beszel/beszel_agent_data:/var/lib/beszel-agent
      - /volume2/docker/beszel/beszel_socket:/beszel_socket
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      LISTEN: /beszel_socket/beszel.sock
      HUB_URL: http://192.168.178.5:8091
      TOKEN: xxxxxxxxxx # get it from Add System window
      KEY: "xxxxxxxxxx" # get it from Add System window

 

[Cyberwasp]

You mentioned a hub which am guessing is a web interface. However, nothing happens other than the agent starting and stopping

 

[dimfil]

You mentioned a hub which am guessing is a web interface. However, nothing happens other than the agent starting and stopping

Hub is the main Beszel container from the conpose file above. It provides the web interface too (port 8091 in my case). For every system you want to monitor you need the agent that connects to the hub. Both included in the above docker compose.
After the first start of the docker project, you need to go to the web ui, get the token and key by adding a system, stop the project, edit the compose file with these values and then restart it.
This is the process and it should work.