Ping timeout
Hi there.
Getting a bunch of "Ping timeout" across all apps for some reason. Refreshing eventually gets one here and one there becoming "Online" until eventually they're almost all online. CPU usage is low and RAM is under 40% as well as bandwidth.
Also getting no more icon search when adding a new app.
I have just updated homarr though. Has there been (in the last 6 months or so) any breaking changes maybe?
Operating system - Ubuntu
Homarr Version 0.15.3
Logs: https://pastebin.com/spM0HVAc
Compose (using portainer stacks):
Network nginx_default being the network where all containers are. homarr is both in that network and bridge network, but also tried it only on nginx_default
8 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, there's a tendency for 1 app to fail the others automatically because of the way the system is currently done. You need to find the 1 app that is unresponsive and correct/remove it
you might have a hint in homarr's container's console/logs
odd. I did have one (Monica) that i had stopped the container for a while. But even removing that didn't solve it. All other ones seem to be working just fine
also getting this now: 2024-08-08T20:35:58.464007747Z ERROR Failed to fetch icons from repository 'JsDelivr': TypeError: fetch failed
That's one odd failed fetch, Are you using a dns-hole? JsDelivr can sometimes end up by mistake on blocklists
basically, anything that is failing or has a long timeout has a potential to slow everything else down drastically. Kind of a pain. Limitation of the current system, which should not be an issue anymore in v1.0, but that'll take a bit of time to come.
i'm a complete newbie when it comes to self-hosting so i'm gonna guess no? haha
but no biggie if i can't get it to work. also using uptime-kuma to monitor anything going offline, so nothing too bad about it
A dns-hole would be PiHole, AdGuard Home, Technitium, Blocky
Oh no none of that. I'm using a VPS. That's how newbie I am. Might change things as well but I forgot to mention I'm using nginx proxy manager and all apps are behind that
There are numerous reasons for slow downs, pings can be one of them. basically anything that has to be fetch from the internet can too, so if your icons are not saved locally but instead using a url, that could factor in. Having way too many apps that use the ping too (That is way the ping function will be set on apps independently and not all of them)
as for the jsdelivr, quite frankly I'm not sure. maybe your vps uses a dns-hole and it might fix itself soon, maybe a restart of the container could help