Beszel widget returning "API Error: No items returned from beszel API" #4723
-
DescriptionI can't get beszel integration to work with homepage. I get "API Error: No items returned from beszel API" on the Beszel widget. I followed the troubleshooting in the docs, from within the homepage container, I could ping, nslookup and curl the beszel IP/domain name/URL with no issues. I had doubts about my usage of a reverse proxy, so I eliminated its involvement completely by using http://ip:port directly, still no luck. Issuing Furthermore, logging into Beszel's pocketbase, I could see tens of failed login attempts due to "invalid login credentials". All coming from docker network specific IPs. Sample below.
Needless to say, I have triple checked the credentials, I have also tried creating a new user, still no luck. I am using Beszel 0.9.1. I have already gone through #4592, #4666, #4492 and #4439. homepage versionv0.10.9 (b5f4daa) Installation methodDocker Configurationservices.yaml
- Monitoring:
- Beszel:
href: http://192.168.0.152:8090
icon: beszel
widget:
type: beszel
url: http://192.168.0.152:8090
username: [email protected]
password: redacted
version: 2settings.yaml
title: My Lab
layout:
Monitoring:
# tab: First
style: row
columns: 4Container LogsBrowser LogsViewing the console logs while visiting the homepage, I get an error TroubleshootingPing
Curl
Checking the logs in Beszel's pocketbase, I could see an entry for this successful authentication through curl. I have tried downgrading back to beszel 0.9.0 but that didn't work too. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 11 replies
-
is not the same endpoint as the widget uses, if you look at your screenshot of the failed logins you’ll see the difference. I don’t exactly recall but I think you need elevated privileges to get the relevant info |
Beta Was this translation helpful? Give feedback.
-
|
I got the API endpoint from https://github.com/gethomepage/homepage/blob/dev/src/widgets/beszel/widget.js as the API troubleshooting guide suggests. The user details I supplied in the config belong to an admin in Beszel's pocketbase. |
Beta Was this translation helpful? Give feedback.
-
|
Again. That is not the URL that file shows: homepage/src/widgets/beszel/widget.js Lines 8 to 13 in 0615799 |
Beta Was this translation helpful? Give feedback.
-
|
Had the same issue, would be nice to have this detail in the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Ah yes, superusers. You were right, I did not supply the credentials of a superuser account. I mistakenly assumed that admin role is the same thing as superuser in pocketbase. I created a new superuser as follows: Then used the credentials from above in the widget config and everything is working now. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I am having the exact issue and my username is also a superuser but I still get the same error. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Don't you run this in a docker environment within the lxc? |
Beta Was this translation helpful? Give feedback.
-
|
Yes I do but I just used the Tteck Proxmox helper script to install it. |
Beta Was this translation helpful? Give feedback.
-
|
Then you can use the Docker exec command from above in your LXC Shell. But it didn’t Worked for me either |
Beta Was this translation helpful? Give feedback.
-
|
Not sure the commands as I am fairly new to it. I tried this command in the container but didnt work. |
Beta Was this translation helpful? Give feedback.
-
|
you have to be in the directory where you run your docker commands, e.g. docker compose up... and you have to make sure that the identifier of the container is correct |
Beta Was this translation helpful? Give feedback.
-
|
Ran the following on my docker host Here is my homepage services.yml config excerpt: yet I am still getting this error: |
Beta Was this translation helpful? Give feedback.
-
|
The data returned is <!DOCTYPE html>
<html lang="en" dir="ltr">
<head>
<meta charset="UTF-8" />
<link rel="icon" type="image/svg+xml" href="/static/favicon.svg" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Bezzel</title>
<script type="module" crossorigin src="/assets/index-DsP1TIUb.js"></script>
<link rel="stylesheet" crossorigin href="/assets/index-C5DxEAFN.css">
</head>
<body>
<div id="app"></div>
</body>
</html>so its not hitting the API. Either the URL is incorrect or the incorrect version setting is messing it up. Also, generally speaking adding a comment to someone else's support thread is not the best way to get help, as is the case here and very often, they are not usually actually the same problem at all. |
Beta Was this translation helpful? Give feedback.
Ah yes, superusers.
You were right, I did not supply the credentials of a superuser account. I mistakenly assumed that admin role is the same thing as superuser in pocketbase.
I created a new superuser as follows:
docker exec beszel /beszel superuser create [email protected] supersecurepasswordThen used the credentials from above in the widget config and everything is working now.
Thanks.