TRPC Client Error - Weather widget cannot fetch data
Hello,
I'm currently getting the following and I'm using docker compose through portainer for my instance:
2025-01-17T22:21:50.563Z error: tRPC Error with query on 'widget.weather.atLocation': (INTERNAL_SERVER_ERROR) - fetch failedDocker compose is as follows (env file just contains encryption key):
version: '3' services: homarr: container_name: homarr image: ghcr.io/homarr-labs/homarr:v1.0.1 restart: unless-stopped volumes: - /portainer/Files/AppData/Config/homarr:/appdata - /var/run/docker.sock:/var/run/docker.sock ports: - 7575:7575 env_file: - stack.envSee pictures attached. Thank you
29 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Is the container able to connect to the internet and do you have a dns hole service?
When I terminal into the docker container I can ping outbound websites. I do have pihole setup as my dns and have also used the "dns:" property in my compose config to no avail
Can you check if it can fetch https://api.open-meteo.com/v1/forecast or if that is blocked by your pihole? If so add it to the allowlist
Seems to be able to get to the api end point:
I've also tried disabling pihole to the same effect
DNS Hole not found. Is't possible to add the Adguard IP to the docker yaml or how could Homarr find the IP
Hey @Xenio can you try again in 1.1.0? The log should tell more than just
fetch failed nowSame error I believe?
2025-01-23T22:37:25.974Z error: tRPC Error with query on 'location.searchCity': (INTERNAL_SERVER_ERROR) - fetch failed
TypeError: fetch failed
at node:internal/deps/undici/undici:13484:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/6573.js:5:53552
at async l.middlewares (/app/apps/nextjs/.next/server/chunks/442.js:43:101549)
at async u (/app/apps/nextjs/.next/server/chunks/442.js:46:68)
at async t (/app/apps/nextjs/.next/server/chunks/442.js:43:100010)
at async t (/app/apps/nextjs/.next/server/chunks/442.js:46:403)
at async /app/apps/nextjs/.next/server/chunks/442.js:43:94885
Okay, I have to check again. Thought it would show more
I too am getting the same error
2025-01-26T01:29:14.406Z error tRPC Error with query on 'widget.weather.atLocation': (INTERNAL_SERVER_ERROR) - fetch failed
TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/6573.js:5:80943
at async l.middlewares (/app/apps/nextjs/.next/server/chunks/442.js:43:101517)
at async u (/app/apps/nextjs/.next/server/chunks/442.js:46:68)
at async u (/app/apps/nextjs/.next/server/chunks/442.js:46:68)
at async t (/app/apps/nextjs/.next/server/chunks/442.js:46:403)
at async /app/apps/nextjs/.next/server/chunks/442.js:43:94855
at async /app/apps/nextjs/.next/server/chunks/442.js:43:96986
at async /app/apps/nextjs/.next/server/chunks/442.js:46:8860
I can ping outside of my container.
My pihole is seeing replies:
Jan 26 01:49:43: query[A] api.open-meteo.com from 172.19.0.1
Jan 26 01:49:43: forwarded api.open-meteo.com to 1.1.1.1
Jan 26 01:49:43: query[AAAA] api.open-meteo.com from 172.19.0.1
Jan 26 01:49:43: forwarded api.open-meteo.com to 1.1.1.1
Jan 26 01:49:43: reply api.open-meteo.com is 94.130.142.35
Jan 26 01:49:43: reply api.open-meteo.com is 2a01:4f8:13b:2e04::2
Jan 26 01:49:45: query[A] api.open-meteo.com from 172.19.0.1
Jan 26 01:49:45: cached api.open-meteo.com is 94.130.142.35
Jan 26 01:49:45: query[AAAA] api.open-meteo.com from 172.19.0.1
Jan 26 01:49:45: cached api.open-meteo.com is 2a01:4f8:13b:2e04::2
and I even turned off blocking just to be sure anyway.
I am getting this error. My docker is installed on Windows (Docker Desktop) though and no dns hole service
2025-01-30 16:32:17 2025-01-30T05:32:17.618Z error: tRPC Error with query on 'widget.weather.atLocation': (INTERNAL_SERVER_ERROR) - fetch failed
2025-01-30 16:32:17 TypeError: fetch failed
2025-01-30 16:32:17 at node:internal/deps/undici/undici:13502:13
2025-01-30 16:32:17 at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-01-30 16:32:17 at async /app/apps/nextjs/.next/server/chunks/5366.js:6:38416
2025-01-30 16:32:17 at async l.middlewares (/app/apps/nextjs/.next/server/chunks/5088.js:102:329495)
2025-01-30 16:32:17 at async p (/app/apps/nextjs/.next/server/chunks/5088.js:105:68)
2025-01-30 16:32:17 at async p (/app/apps/nextjs/.next/server/chunks/5088.js:105:68)
2025-01-30 16:32:17 at async t (/app/apps/nextjs/.next/server/chunks/5088.js:105:403)
2025-01-30 16:32:17 at async /app/apps/nextjs/.next/server/chunks/5088.js:102:322624
2025-01-30 16:32:17 at async /app/apps/nextjs/.next/server/chunks/5088.js:102:324755
2025-01-30 16:32:17 at async /app/apps/nextjs/.next/server/chunks/5088.js:105:8860
2025-01-30 16:32:17 TypeError: fetch failed
I'm hoping one of the developers sees this because it feels like there is a bug here
Yes we know about this bug, but we first need to get it working to print more details.
Glad to know that. I thought it was a me problem 😂
Thanks for confirming mate. Much appreciated.
I also have the same problem, I'm using Homarr over Portainer. In my case I'm not only having problems fetching the weather api but also receive the error "Application error: a server-side exception has occurred (see the server logs for more information).
Digest: 687904191"
I just installed the recently released version 1.4.0 but didn't fix anything.
I'm also getting that 'Application Error' when trying to access 'Settings' on the newest v1.4.0.
I only get this error when I'm logged in. If I access the Homarr site in incognito mode without logging in, I can see the dashboard (except for the weather widget). However, as soon as I log in with my credentials, I get the "server-side" error.
Can you create a seperate #💬・get-help post and post your logs there?
I disabled Pi-hole, midified my router to use standard dns IP (8.8.8.8) and not only Homarr is working but also my Portainer custom templates from Github are working now.
I finally fixed setting up its own DNS directly on the Homarr container. Everything is working fine now.
Do we have an update on this? Im on a new server and just deployed the container and still seeing the same bug.
I'm also having the weather issue on the last couple of releases at least, works perfectly on 0.15.10 but gives the same error as above with the later versions. (TRPCClientError: fetch failed)
Please post the logs
It's weird because I noticed it working randomly as I was changing things / adding things and I was able to change the weather to my location and configure how I wanted, but its now showing an error again, heres what comes up in the logs:
2025-03-15T10:25:39.510Z error: tRPC Error with query on 'widget.weather.atLocation': (INTERNAL_SERVER_ERROR) - fetch failed
TypeError: fetch failed
at node:internal/deps/undici/undici:13502:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/apps/nextjs/.next/server/chunks/2359.js:9:20883
at async l.middlewares (/app/apps/nextjs/.next/server/chunks/5697.js:116:1576669)
at async u (/app/apps/nextjs/.next/server/chunks/5697.js:119:68)
at async u (/app/apps/nextjs/.next/server/chunks/5697.js:119:68)
at async t (/app/apps/nextjs/.next/server/chunks/5697.js:119:403)
at async /app/apps/nextjs/.next/server/chunks/5697.js:116:1569787
at async /app/apps/nextjs/.next/server/chunks/5697.js:116:1571929
at async /app/apps/nextjs/.next/server/chunks/5697.js:119:9784
TypeError: fetch failed
@Meierschlumpf why do we not see more of the stacktrace? The error is too generic
No the tRPC error is not fully logged yet
We just improved the logs in #2574. The improvements will land in v1.13.0
Thanks for your work, it used to work off and on, now it never seems to load.