wud widget returns nothing

[kajvans]

Description

i am trying to setup my dashboard and was adding the wud widget. it just runs on port 3000 so i did setup the widget but when looking in my dashboard it gives an error:
API Error: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
is there something i need to do extra? are the docs outdated?
anyone some advice?

homepage version

v0.8.9 (c89c488, Mar 10, 2024)

Installation method

Docker

Configuration

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    restart: always
    ports:
      - 3008:3000
    volumes:
      - ./:/app/config # Make sure your local config directory exists
      - ./logo:/app/public/icons
      - /var/run/docker.sock:/var/run/docker.sock # (optional) For docker integrations

Container Logs

03/19/2024
04:39:27 PM
[2024-03-19T15:39:27.188Z] error: <httpProxy> Error calling http://192.168.1.225:3000/api/containers...
03/19/2024
04:39:27 PM
[2024-03-19T15:39:27.189Z] error: <httpProxy> [
03/19/2024
04:39:27 PM
  500,
03/19/2024
04:39:27 PM
  Error: connect ETIMEDOUT 192.168.1.225:3000
03/19/2024
04:39:27 PM
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
03/19/2024
04:39:27 PM
    errno: -110,
03/19/2024
04:39:27 PM
    code: 'ETIMEDOUT',
03/19/2024
04:39:27 PM
    syscall: 'connect',
03/19/2024
04:39:27 PM
    address: '192.168.1.225',
03/19/2024
04:39:27 PM
    port: 3000
03/19/2024
04:39:27 PM
  }
03/19/2024
04:39:27 PM
]

Browser Logs

API Error: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Troubleshooting

tried different ports

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the error message you're seeing (API Error: Unexpected token '<', "<!DOCTYPE "... is not valid JSON), it seems that the request made by the widget is expecting JSON data but is instead receiving HTML. This often happens when the request hits a web server that returns a default error page, usually a 404 or 500 error page, which is HTML and not the JSON data the widget expects.

The container logs you provided indicate a timeout error when trying to connect to 192.168.1.225:3000. This suggests that the homepage instance is unable to reach the Whats Up Docker (WUD) service at the specified IP and port.

Here are some steps you can take to troubleshoot this issue:

1. Ensure that the WUD service is running and accessible at http://192.168.1.225:3000/api/containers. You can test this by accessing the URL directly in your web browser or using a tool like curl.

2. Verify that there are no network issues preventing the homepage container from reaching the WUD service. This could be due to firewall rules, network segmentation, or the WUD service not being up and running.

3. Check the configuration of your WUD widget in the services.yaml file. Make sure that the URL is correct and does not end with a trailing slash, as per the documentation. The URL should be something like http://192.168.1.225:3000.

4. If you're running the homepage and WUD services in separate Docker containers, ensure that they are on the same Docker network or otherwise configured to communicate with each other.

5. If the issue persists, you may want to check the WUD logs for any errors or messages that could indicate why it's not responding with the expected JSON data.

6. As a last resort, you can try recreating the homepage container to ensure that all settings are applied correctly.

If you continue to experience issues, you may want to reach out for support on the homepage GitHub discussions or Discord channel, as mentioned in the troubleshooting documentation.

This comment was generated by Glime.

[kajvans]

when curling the url it returns json data and it all works fine.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.