API - OpenWeather and Open-meteo

[TeaJhay]

Description

Unable to get the Open-meteo widget (or the OpenWeather one) to function. API error, 500 internal server error.

I've scoured the discussions, docs and forums to try and find a solution and haven't had any luck. The problem is most likely on my end but I can't figure out what. Built the homepage as a proxmox LXC with a helper script, made it super easy. Script was made by tteck and is here. I can ssh in and ping and curl both google and open-meteo.com to what seems to be fine, so the container can get out and I'm frankly not sure if it's an install issue or if something is happening with my reverse proxy and I need the help in finding out what is going on.

homepage version

0.8.12

Installation method

Other (please describe above)

Configuration

Widget.yaml:

- openmeteo:
    latitude: -25.29
    longitude: 152.89
    units: imperial
    cache: 5
    format:
      maximumFractionDigits: 1

Container Logs

[2024-04-21T13:55:48.523Z] error: undefined
[2024-04-21T14:00:29.986Z] error: undefined
[2024-04-21T14:00:33.089Z] error: undefined
[2024-04-21T14:00:36.761Z] error: undefined
[2024-04-21T14:00:38.692Z] error: undefined
[2024-04-21T14:00:47.691Z] error: undefined
[2024-04-21T14:04:11.945Z] error: undefined
[2024-04-21T14:04:12.075Z] error: undefined
[2024-04-21T14:04:15.368Z] error: undefined
[2024-04-21T14:04:15.443Z] error: undefined
[2024-04-21T14:04:15.788Z] error: undefined
[2024-04-21T14:04:22.677Z] error: undefined
[2024-04-21T14:04:26.676Z] error: undefined

Browser Logs

Troubleshooting

tested on both Brave and Firefox, https and direct IP. Reinstalled (using same script, will do a standard docker install late when I have the time)

[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 information provided, it seems that you are encountering a 500 internal server error when trying to use the Open-meteo widget on your Homepage installation. This error indicates that there is a problem on the server side, which could be related to the configuration of the widget, the Homepage installation, or network issues such as a reverse proxy configuration problem.

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

1. Check the Widget Configuration: Ensure that the configuration for the Open-meteo widget in your widget.yaml file is correct. According to the documentation, you do not need to specify a URL for the Open-meteo API, as it is handled by the widget itself. Make sure there are no typos or incorrect values in the configuration.

2. Verify Network Connectivity: Since you mentioned that you can ping and curl both Google and open-meteo.com, it seems like your container has internet access. However, you should also ensure that the Homepage container can reach the Open-meteo API endpoint. You can do this by executing a curl command from within the container to the Open-meteo API.

3. Check Reverse Proxy Configuration: If you are using a reverse proxy, make sure that it is configured correctly to allow traffic to and from the Homepage container. Incorrect reverse proxy settings can lead to API errors.

4. Review Container Logs: The container logs you provided only show error: undefined, which is not very informative. You can try setting the ENV variable LOG_LEVEL to debug to get more detailed logs that might help identify the issue.

5. Check for Open Issues: Look for any open issues on the Homepage GitHub repository that might be related to your problem. Other users may have encountered similar issues, and there might be a discussion or solution available.

6. Use Homepage AI Bot: Utilize the Homepage AI Bot for assistance. The bot has full knowledge of the docs, GitHub issues, and discussions. You can access the bot by hitting the 'Ask AI' button on any page in the docs, opening a GitHub discussion, or checking out the #ai-support channel on Discord.

7. Standard Docker Installation: If the issue persists, you may want to try a standard Docker installation of Homepage as opposed to using the script provided by tteck. This could help determine if the issue is related to the script or the installation method.

If none of these steps resolve the issue, you may want to reach out for support on the Homepage GitHub discussions or the Discord channel for more personalized assistance.

This comment was generated by Glime.

[TeaJhay]

ran like 4 different install tests. My hypervisor and vms are fine, it's the install script. Something isn't right. will let the script maintainer know. thanks

[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.