OpenMeteo API Error in latest version

[Leighm0]

Description

After upgrading from v0.10.9 to v1.0.2 the OpenMeteo widget no longer works - top right just shows "API Error"

homepage version

v1.0.2

Installation method

Unraid

Configuration

From widgets.yaml (redacted info)

- openmeteo:
    label: [REDACTED]
    latitude: [REDACTED]
    longitude: [REDACTED]
    timezone: [REDACTED]
    units: metric
    cache: 5

Container Logs

▲ Next.js 15.1.7

• Local: http://[::1]:3000
• Network: http://[::]:3000

✓ Starting...
✓ Ready in 385ms
[2025-03-15T04:09:52.604Z] error: undefined
[2025-03-15T04:09:52.616Z] error: TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at process.processTimers (node:internal/timers:526:9)
at async o (/app/.next/server/pages/api/releases.js:1:4348)
at async s (/app/.next/server/pages/api/widgets/openmeteo.js:1:872)
at async z (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17092)
at async U.render (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17800)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:628:9)
at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:278:37)
[2025-03-15T04:11:10.805Z] error: undefined
[2025-03-15T04:11:10.811Z] error: TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async o (/app/.next/server/pages/api/releases.js:1:4348)
at async s (/app/.next/server/pages/api/widgets/openmeteo.js:1:872)
at async z (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17092)
at async U.render (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17800)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:628:9)
at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:278:37)
at async NextNodeServer.handleRequestImpl (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:853:17)
at async invokeRender (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/lib/router-server.js:230:21)
[2025-03-15T04:11:16.179Z] error: undefined
[2025-03-15T04:11:16.182Z] error: TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async o (/app/.next/server/pages/api/releases.js:1:4348)
at async s (/app/.next/server/pages/api/widgets/openmeteo.js:1:872)
at async z (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17092)
at async U.render (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17800)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:628:9)
at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/next-server.js:278:37)
at async NextNodeServer.handleRequestImpl (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:853:17)
at async invokeRender (/app/node_modules/.pnpm/next@15.1.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/lib/router-server.js:230:21)

Browser Logs

Failed to load resource: the server responded with a status of 500 ()
Failed to load resource: the server responded with a status of 500 ()
GET https://[REDACTED]/api/widgets/openmeteo?latitude=[REDACTED]&longitude=[REDACTED]&index=1&label=[REDACTED]&timezone=[REDACTED]&units=metric&cache=5&style=%5Bobject+Object%5D 500 (Internal Server Error)

Troubleshooting

Rolled back to v0.10.9 and the widget works. Then tried upgrading to v1.0.0 - same errors. Only seems to be working in v0.10.9 and below.

[shamoon]

Cant reproduce. What if you disable ipv6 with

        sysctls:
            - net.ipv6.conf.all.disable_ipv6=1

[Leighm0]

EDIT: sorry no it doesnt, I forgot to remove the sysctl line on first attempt.

[shamoon]

Gotcha. what about if you use the image feature-use-ipv4?

[winsphinx]

I run in docker, but I cannot remove sysctl setting.
I tried HOMEPAGE_PROXY_DISABLE_IPV6=true and HOMEPAGE_PROXY_USE_IPV4=true, still failed.

[Licidil]

I run in docker, but I cannot remove sysctl setting. I tried HOMEPAGE_PROXY_DISABLE_IPV6=true and HOMEPAGE_PROXY_USE_IPV4=true, still failed.

I managed to get it working for myself disabling IPV6 by adding this to the compose file;

sysctls:
  - net.ipv6.conf.all.disable_ipv6=1

Add it in like you would a restart policy, with "sysctls:" being it's own segment under "homepage"

Hopefully this helps!

[Leighm0]

Gotcha. what about if you use the image feature-use-ipv4?

no, same error

The only way to fix it so far for me is to use the sysctls config.

[winsphinx]

I met same issue.
I tried Open-Meteo and OpenWeatherMap, both are errors. Neither ipv4 nor ipv6.

[Licidil]

Just wanna make sure you see this, I don't know how GitHub handles notifications on answered / closed discussions, sorry about any potential double notifications!

I managed to get it working for myself disabling IPV6 by adding this to the compose file;

sysctls:
  - net.ipv6.conf.all.disable_ipv6=1

Add it in like you would a restart policy, with "sysctls:" being it's own segment under "homepage"

This is in place of HOMEPAGE_PROXY_DISABLE_IPV6=true and HOMEPAGE_PROXY_USE_IPV4=true. These didn't work for me, but sysctls: absolutely did.

Hopefully this helps!

[owennewo-dev]

I had this same issue. v0.10.9, installed on TrueNAS Scale via the Homepage app.
Disabling IPv6 worked!
For any other TrueNAS users that need some help:

[shamoon]

I'd be curious if anyone here is willing to try this (again, it changed):

• Try the docker image tagged feature-disable-ipv6 with env HOMEPAGE_PROXY_DISABLE_IPV6=true

If testing this out you should remove the sysctls option described above, the idea is to see if we can make it no-longer needed

[Leighm0]

You needed to use the image label "feature-disable-ipv6" as mentioned in the post.

image: ghcr.io/gethomepage/homepage:feature-disable-ipv6

[Leighm0]

I'd be curious if anyone here is willing to try this (again, it changed):

• Try the docker image tagged feature-disable-ipv6 with env HOMEPAGE_PROXY_DISABLE_IPV6=true

If testing this out you should remove the sysctls option described above, the idea is to see if we can make it no-longer needed

This works for me using the image tag and the env var and removing the sysctl config.

[shamoon]

Oh amazing, thanks for testing that. I hoped it would!

That change will be in our next release if anyone else wants to use that method (the sysctls thing isnt going to go away or anything like that).

[winsphinx]

Tag "feature-disable-ipv6" works. Thanks!

[jamesawebb]

I've just come across this issue. I'm also on an IPv6 stack (with CGNAT IPv4). I'm curious to understand why this is an issue as a raw API fetch itself works without issue. Anyone have insights on this?

[jamesawebb]

Incidentally, sysctls: [net.ipv6.conf.all.disable_ipv6=1] works as a fix for me. Neither env vars helped.

[shamoon]

Neither env vars helped.

The version containing this is not released yet.

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