Homarr failing to update applications and widget
Since 10 April a previously functioning Homarr board now fails on trying to load on widget information either internet or locally.
I'm using:
Raspbian Bookworm version 12
Docker version 26.1.2, build 211e74b
traefik as my reverse proxy
docker-compose.yml attached
I can ping 1.1.1.1 from all the docker containers, and can ping the homarr container but there when I attach the the homarr container I can't run ping to confirm if it has full network access.
I'm really stumped as it was working, and I've deleted the previous working board, deleted the old sqlite database and recreated homarr using a default board but still can't get the default widgets to load.
e.g. weather widget set for Paris won't display any information (just loading pulse icon) and when I try and edit won't load any other locations either. Board just times out and when I check the logs see error message of fetch failed.:homarr:


26 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?
Hi @Buckwheat_UK , please provide the data as requested by @Cakey Bot
Apologies, I'm not sure what else I need to post. I did create an account for paste bin for the logs, but couldn't work out how to attach it to the request. I did attach screen shots of the homarr logs and docker-compose.yml
Please post your Homarr version 🙂
Is there a way to get that from docker itself as its just the latest and when I try and get it from the homarr dashboard it just times out and the page won't load.
No but you can post your image hash

ghcr.io/ajnart/homarr latest 8c2fa24be049 3 days ago 656MB
I'm unable to find this hash. But since you updated on 10 Apr, it's likely that you are running 0.15.3.
First off, I'd like to make you a backup of all Homarr directories (in case you haven't done so).
Then, Iwould suggest you to delete the image & container, repull the image and try again.
Just done, that still have this with the default board

Still same error in the log?


@Meierschlumpf can you look into this? Almost seems to me that the hostname for nextauth is invalid...
@Buckwheat_UK please wait for Meier to reply. Thank you 👍
👍 Really appreciate your time on this @Manicraft1001
Can you try to add the BASE_URL env variable like the following:
🔀 Proxies and Certificates | Homarr documentation
Allowing self-signed certificates
I added
environment:
- BASE_URL=homarr.local.metropol-ad.com
but still the same issue.
tried NEXTAUTH_URL=http://homarr.local.metropol-ad.com/api/auth and NEXTAUTH_URL=https://homarr.local.metropol-ad.com/api/auth both the same error.
Wait it's failing to get the icons as well, maybe is something wrong with the internet connection?
That's what I initially though, I tested other containers could successfully ping 1.1.1.1
docker container exec -it uptime-kuma /bin/bash
root@ede7a875937e:/app# ls
config db docker index.html package-lock.json public src
data dist extra node_modules package.json server
root@ede7a875937e:/app# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=54 time=19.1 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=54 time=14.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=54 time=14.3 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=54 time=13.9 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=54 time=14.5 ms
Maybe try to resolve a hostname instead of pinging?
root@ede7a875937e:/app# getent ahostsv4 www.bbc.co.uk
212.58.237.129 STREAM gtm-uk.www.bbc.co.uk.pri.bbc.co.uk
212.58.237.129 DGRAM
212.58.237.129 RAW
212.58.235.129 STREAM
212.58.235.129 DGRAM
212.58.235.129 RAW
212.58.236.1 STREAM
212.58.236.1 DGRAM
212.58.236.1 RAW
212.58.237.1 STREAM
212.58.237.1 DGRAM
212.58.237.1 RAW
212.58.236.129 STREAM
212.58.236.129 DGRAM
212.58.236.129 RAW
212.58.235.1 STREAM
212.58.235.1 DGRAM
212.58.235.1 RAW