fetch request failed - open-meteo

[TeaJhay]

Description

I've been trying to to get the open-meteo widget working consistently since I installed Homepage and through numerous vms I've managed to get it working sometimes. I really wanted to have it work on Alpine linux so that's where the following error message comes from, but I do believe it's the same that was occuring on debian CT's. the logs in "container logs" are the errors displayed in dev mode.

homepage version

8.12

Installation method

Source

Configuration

Widget is the basic open-meteo example.

intallation was exactly as follows on an Alpine Linux CT template

apk add git
apk add npm
apk add nano
npm install node
cd /opt/
mkdir homepage
cd homepage/
git clone https://github.com/gethomepage/homepage.git
cd homepage
npm install
npm run build
npm start &
<nano widget.yaml and paste open-meteo example>
reboot

cd and npm start again

Container Logs

[2024-04-25T03:14:37.699Z] error: TypeError: fetch failed
    at node:internal/deps/undici/undici:12500:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async cachedFetch (webpack-internal:///(api)/./src/utils/proxy/cached-fetch.js:23:18)
    at async handler (webpack-internal:///(api)/./src/pages/api/widgets/openmeteo.js:12:21)
    at async Object.apiResolver (/opt/homepage/node_modules/next/dist/server/api-utils/node.js:366:9)
    at async DevServer.runApi (/opt/homepage/node_modules/next/dist/server/next-server.js:481:9)
    at async Object.fn (/opt/homepage/node_modules/next/dist/server/next-server.js:741:37)
    at async Router.execute (/opt/homepage/node_modules/next/dist/server/router.js:252:36)
    at async DevServer.run (/opt/homepage/node_modules/next/dist/server/base-server.js:365:29)
    at async DevServer.run (/opt/homepage/node_modules/next/dist/server/dev/next-dev-server.js:709:20)

Browser Logs

:3000/api/widgets/openmeteo?latitude=50.449684&longitude=30.525026&index=2&label=Kyiv&timezone=Europe%2FKiev&units=metric&cache=5&format=%5Bobject+Object%5D&style=%5Bobject+Object%5D:1

   Failed to load resource: the server responded with a status of 500 (Internal Server Error)

:3000/api/widgets/openmeteo?latitude=50.449684&longitude=30.525026&index=2&label=Kyiv&timezone=Europe%2FKiev&units=metric&cache=5&format=%5Bobject+Object%5D&style=%5Bobject+Object%5D:1

   Failed to load resource: the server responded with a status of 500 (Internal Server Error)

:3000/api/widgets/openmeteo?latitude=50.449684&longitude=30.525026&index=2&label=Kyiv&timezone=Europe%2FKiev&units=metric&cache=5&format=%5Bobject+Object%5D&style=%5Bobject+Object%5D:1

   Failed to load resource: the server responded with a status of 500 (Internal Server Error)

index-ea2c0d705703a383.js:1

   GET http://10.0.0.140:3000/api/widgets/openmeteo?latitude=50.449684&longitude=30.525026&index=2&label=Kyiv&timezone=Europe%2FKiev&units=metric&cache=5&format=%5Bobject+Object%5D&style=%5Bobject+Object%5D 500 (Internal Server Error)

fetcher @ index-ea2c0d705703a383.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1
o @ _app-31e5bc7bec1014c9.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1ec1014c9.js:1
(anonymous) @ _app-31e5bc7bec1014c9.js:1
o @ _app-31e5bc7bec1

Troubleshooting

n/a for info widgets however I have made sure curl and ping works for api.open-meteo.com on several vms.

[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 the open-meteo widget is not functioning correctly and is resulting in a TypeError: fetch failed error in the container logs, as well as a 500 Internal Server Error in the browser logs when trying to access the widget's API endpoint.

The error suggests that there is an issue with the server-side code that handles the fetching of data from the open-meteo API. This could be due to a number of reasons, such as a misconfiguration in the widget settings, network issues, or a problem with the server environment (e.g., missing dependencies or incorrect permissions).

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

1. Check the widget configuration: Ensure that the widget.yaml file is correctly configured according to the open-meteo widget documentation. Make sure that the latitude and longitude are set correctly and that there are no syntax errors in the file.

2. Verify network connectivity: Since you mentioned that curl and ping work for api.open-meteo.com, it's likely not a network connectivity issue. However, it's still worth double-checking that the server where Homepage is running can reach the open-meteo API without any issues.

3. Check for missing dependencies: Ensure that all required dependencies are installed on the server. Since you're running on Alpine Linux, make sure that all necessary Node.js packages are installed and up-to-date.

4. Review server logs: Look at the server logs for more detailed error messages that might indicate what's causing the fetch failed error. This could provide clues as to whether the issue is with the fetch request itself or with the handling of the response.

5. Update Homepage: If you're not running the latest version of Homepage, consider updating to the latest version to see if the issue has been resolved in a more recent release.

6. Seek support: If you're unable to resolve the issue on your own, consider reaching out for support. You can use the Homepage AI Bot, open a GitHub discussion, or check out the #ai-support channel on Discord for assistance.

If you provide more specific details about the error or the steps you've already taken, I may be able to offer more targeted advice. Otherwise, the general troubleshooting steps above should help you start investigating the issue.

This comment was generated by Glime.

[shamoon]

Wish I had more to offer but since this works both in docker and from source for me I have to assume this is a config or perhaps but less likely a network issue. You didnt actually post your config but you said the example one, which is what the screenshots below are.

[TeaJhay]

my bad, completely misinterpreted what to write. I can get it working on ubuntu an ubuntu lxc and a debian lxc (although that's had on and off issues between tests).

config is all default, literally unchanged as I spun up an alpine vm, installed git, nano and npm, then cloned and, installed, built and started homepage. It could be network but I have zero idea where the issue could be happening for that. It runs on some proxmox containers and on a docker install for windows. I'm able to ping the api and curl (although curl gives some an int error, presumably because i had no actual request info) works. the fact that it worked on two ct's makes me doubt it's network as well. I'm thinking it's something with node.js and missing files but I presumed that'd come up as an error during "npm install".

for the sake of it I just tried again with pnpm instead of npm. on the alpine linux CT template in proxmox, network set to dhcp and everything default. All I did was install npm, then pnpm, git clone the repo, then run the install and build and edit the widget.yaml.

is there any dependencies that might not get installed and are installed by default on ubuntu and the like? Honestly I think I've fried my brain the last few days trying to get it functioning in an ideal environment. worst case I move on from trying minimise the resources used by getting it working on an ubuntu or debain ct. It's not a big deal, just not completely ideal.

any idea's for how I could extract some more logs or info to further troubleshoot?

[shamoon]

Honestly, that whole paragraph feels like an advertisement for docker 😜

If youre running from source it'd be easy enough to play with it a bit, but open-meter is unbelievably simple as you can see:

homepage/src/pages/api/widgets/openmeteo.js

Lines 3 to 9 in 312e97d

	export default async function handler(req, res) {
	const { latitude, longitude, units, cache, timezone } = req.query;
	const degrees = units === "imperial" ? "fahrenheit" : "celsius";
	const timezeone = timezone ?? "auto";
	const apiUrl = `https://api.open-meteo.com/v1/forecast?latitude=${latitude}&longitude=${longitude}&daily=sunrise,sunset&current_weather=true&temperature_unit=${degrees}&timezone=${timezeone}`;
	return res.send(await cachedFetch(apiUrl, cache));
	}

and cachedFetch is a tiny little wrapper around fetch which comes from straight nodejs...

[TeaJhay]

hah. You're probably right. At this point I suppose I should just start learning docker. Would have been nice to get source to work, however it will be interesting to see if the docker method does work. If it doesn't then I know it's my fault. My network or hypervisor is messed up somewhere and if it does then I guess there must be differences between Ubuntu, Debian and Alpine as well as their nodejs packages (I assume npm uses the distros repos? not entirely sure). Not sure what else would cause the problem, especially with something so simple, that will probably eat at my curiosity for a while.

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