Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: SystemID changing when updating #335

Open
rcbop opened this issue Dec 18, 2024 · 6 comments
Open

Question: SystemID changing when updating #335

rcbop opened this issue Dec 18, 2024 · 6 comments
Labels
troubleshooting Maybe bug, maybe not

Comments

@rcbop
Copy link

rcbop commented Dec 18, 2024

Hello, I have a question does the systemID always change when my watchtower updates the beszel image to the latest version? Can I do something to persist this systemId?

I'm asking this because when it restarts and changes the systemId it's breaking this integration https://gethomepage.dev/widgets/services/beszel/

@henrygd
Copy link
Owner

henrygd commented Dec 18, 2024

Strange, I'm not sure why that would happen. This is something you noticed with previous releases as well?

If you look at the created date for the system on /_/#/collections?collection=systems does it indicate that it was recreated?

Are you using a config file to define systems by any chance?

I'll look further into it. Thanks for letting me know.

@henrygd henrygd added the troubleshooting Maybe bug, maybe not label Dec 18, 2024
@rcbop
Copy link
Author

rcbop commented Dec 23, 2024

Hey @henrygd
This is how I was setting this up:

 beszel:
    image: 'henrygd/beszel'
    container_name: 'beszel'
    restart: unless-stopped
    ports:
      - '8090:8090'
    volumes:
      - /opt/docker-services/data/config/beszel:/beszel_data
    extra_hosts:
      - 'host.docker.internal:host-gateway'
    networks:
      - traefik-network
    labels:
      - traefik.enable=true
      - traefik.http.routers.beszel.rule=Host(`beszel.mydomain.com`)
      - traefik.http.routers.beszel.entrypoints=websecure
      - traefik.http.services.beszel.loadbalancer.server.port=8090
      - homepage.group=Infrastructure
      - homepage.name=Beszel
      - homepage.icon=https://cdn.jsdelivr.net/gh/selfhst/icons/webp/beszel-light.webp
      - homepage.href=https://beszel.mydomain.com
      - homepage.description=Monitoring solution
      - homepage.widget.type=beszel
      - homepage.widget.url=https://beszel.mydomain.com
      - [email protected]
      - homepage.widget.password=xxxxxxx
      - homepage.widget.systemId=rrsa25j8p920ukn # <-- tried updating this to the latest change found in https://beszel.mydomain.com/_/#/collections?collectionId=2hz5ncl8tizk5nx&collection=_pb_users_auth_&filter=&sort=-%40rowid but no luck here

And now I get this error in the homepage UI.

API Error: Invalid character in header content ["Authorization"]
URL: https://beszel.mydomain.com/api/collections/systems/records?page=1&perPage=500&sort=%2Bcreated
Raw Error:
{
    "code": "ERR_INVALID_CHAR",
    "level": "error"
}

Everything should be on latest version since I'm running watchtower to pull the latest image from registries.

@henrygd
Copy link
Owner

henrygd commented Dec 23, 2024

Can you double check that watchtower updated Homepage to 0.10.2, which was released yesterday?

There were changes to the REST API in Beszel 0.9.0 that broke the widget (#336), but the new Homepage release has a fix.

Try adding version: 2 to the widget configuration as shown here: https://gethomepage.dev/widgets/services/beszel/

@rcbop
Copy link
Author

rcbop commented Dec 24, 2024

I tried, but something not working right. I believe the labels are picked up as strings and are not entering the conditional: #336 (comment)

@rcbop
Copy link
Author

rcbop commented Dec 24, 2024

Opened this to try to fix it gethomepage/homepage#4488

@rcbop
Copy link
Author

rcbop commented Dec 25, 2024

Just to link here that I'm having a different error now. gethomepage/homepage#4488 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
troubleshooting Maybe bug, maybe not
Projects
None yet
Development

No branches or pull requests

2 participants