Help with inital setup/configuration. My system is always marked as "down"

[Kamikaze01git]

Hello.
I use a Synology DS920+ (Intel Celeron J4125) with DSM 7.2.1-69057 and Portainer Community Edition 2.19.4
I try to follow mariushosting's explanation on how to deploy beszel on my Synology. But my system is always marked as "down".

I use volume2/dockers/ for my dockers, so my compose look like this:

services:
  beszel:
    container_name: Beszel
    image: henrygd/beszel:latest
    volumes:
      - /volume2/docker/beszel:/beszel_data:rw
    ports:
      - 8095:8090
    restart: on-failure:5

  beszel-agent:
    image: henrygd/beszel-agent
    container_name: Beszel-Agent
    network_mode: host
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      PORT: 45876
      KEY: #Your_Personal_Key
      FILESYSTEM: /dev/sda1
    restart: on-failure:5`

This works the way expected and in my LAN i can reach the docker with Port 8095 and create an admin account.
After that i try to add my system

Name: Synology
IP/HOST: 192.168.1.6
Port: 45876
Public Key: XXXXX

I copy the Public Key and paste it to the beszel-agent and update the docker.
Everything is okay, but my system (Synology) is always marked "down" in beszel.

This is the output from beszel docker:

2024/09/30 07:20:19 Server started at http://0.0.0.0:8090
├─ REST API: http://0.0.0.0:8090/api/
└─ Admin UI: http://0.0.0.0:8090/_/

This is the output from beszel-agent docker:

2024/09/30 07:32:21 WARN Partition details not found filesystem=/dev/sda1
2024/09/30 07:32:21 INFO Detected root device name=cachedev_0
2024/09/30 07:32:21 WARN Device not found in diskstats name=cachedev_0
2024/09/30 07:32:21 INFO Using I/O fallback name=md4
2024/09/30 07:32:21 INFO Detected network interface name=eth0 sent=314323649838 recv=1115989456495
2024/09/30 07:32:21 INFO Starting SSH server address=:45876

i also tried sda, sda0, sda2, sda3, sda4 and sda5... or dab, sdb0, sdb1, sdb2,... but nothing changed.
System always shown as "down" :(

I am sure i do something wrong, but i can not find my mistake.
Pls help me to get these great dashboard for my synology server :)

Thank you !!!

[henrygd]

Hi, please go to the logs page (/_/#/logs), look for any error logs related to that system and let me know what it says. You can try searching for "error" or "Failed to connect".

Here are some things you can try:

• Check that the IP for you Synology device is correct (192.168.1.6)
• Try running telnet 192.168.1.6 45876. This should connect and print the message "SSH-2.0-Go" if the agent is listening on the port.
• Add an extra_hosts property to your compose and use host.docker.internal to add the system. See this comment for more info.

[Kamikaze01git]

Hello @henrygd and thank you very much for your participation in my problem !!

I tried adding extra_hosts: -host.docker.internal but nothing changed. My System still shown as "down".

The LOG always throw the same Error:

Level | ERROR (8)
created | 2024-10-01 05:10:12.764 UTC
message | Failed to connect:
data.err | dial tcp 192.168.1.6:45876: i/o timeout
data.port | 45876
data.system | 192.168.1.6

I already disabled all Firewalls and VPNs etc... could it be a problem because i use an own volumen for my dockers?
volume2 is for dockers and volume1 is for the rest of the system.

i am not sure how to find out what i have to put in FILESYSTEM:
When i take a look in the /dev Folder on my system, there are a lot of entries. md0, md1, md2, etc... some entries for my two NVME (RAID1) and a lot of entries for my 4pcs HDDs (Syno Hybrid Raid). But there are no sda entries.
How can i find out what is the right filesystem, but i already tried nearly all of them.

synology throw this, when i try to telnet

root@Synology:/# telnet 192.168.1.6:45876
-ash: telnet: command not found

[henrygd]

Please try telnet 192.168.1.6 45876 from a laptop or other device in the same network if possible.

After adding extra_hosts to the compose file, did you remove the system in Beszel and add it again using host.docker.internal in the "Host / IP" field?

Don't worry about FILESYSTEM right now, it's not related to this connectivity issue.

[Kamikaze01git]

THAT do the trick :)
I forgot to put that in the "HOST/IP" field. haha
Now everything works like a charm :-)))

Thank u VERY MUCH for you help and your great work !!!

[henrygd]

No worries, glad you find it useful 👍