All my status pings show up as red
All apps show up as red even though the app is up and responds with 200 when doing a manual curl
56 Replies
Any errors in the homarr log?
What version are you running?
What status code does it return?
Please give us clues... We can't just magically figure out everything š
Log
2023-03-04T13:47:54.716482036Z Listening on port 7575 url: http://7723f0d303a6:7575
2023-03-04T13:48:27.101252977Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T13:48:27.693468095Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T13:50:21.847947362Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T13:50:22.307879412Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T13:51:18.645465501Z ā¹ Saving updated configuration of 'default' config.
2023-03-04T13:54:34.716233152Z
2023-03-04T13:54:34.716308833Z ERROR Error communicating with your download client 'qBittorrent' (749f6a06-fdbf-4717-b41c-8d500864c505): HTTPError: Response code 502 (Bad Gateway)
2023-03-04T13:54:34.716318628Z
2023-03-04T13:54:34.716530602Z
2023-03-04T13:54:34.716556890Z WARN 1 download clients failed. Please check your configuration and the above log
2023-03-04T13:54:34.716565145Z
2023-03-04T13:58:24.096328595Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T13:58:24.520787799Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T14:03:11.947687030Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T14:03:12.402439082Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T14:03:33.501524779Z ā¹ Saving updated configuration of 'default' config.
2023-03-04T14:15:47.024976113Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T14:15:47.967798406Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T14:48:24.919722058Z ā¹ Saving updated configuration of 'default' config.
2023-03-04T15:17:25.321024209Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T15:17:25.919362082Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T15:17:58.199882807Z ā¹ Saving updated configuration of 'default' config.
2023-03-04T16:13:27.143215899Z ā¹ Requested frontend content of configuration 'default'
2023-03-04T16:13:28.805953496Z ā¹ Requested frontend content of configuration 'default'
Version 0.11.5
It returns status 200 OK as shown in the picture
200?
That's weird
Are you on dev?
yes
@ajnart this is most likely related to your change
Can you fix it?
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
Still same, has worked before with that enabled so would be weird if it stopped working now
Now it's actually able to ping one app, but everything else is still red
Same settings as all the other hosts in nginx
It might get stuck one one app
What change ? I don't think i made any in .15
Oh i didn't see that
Can you show me your config ?
I didn't I forgot to add a condition that assumes [200] code is always accepted
If I remove 200 from the list of status codes then add it again on an app it seems to work again so I guess I'll do that for now
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
We're working on this...
A fix should be out very soon.
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
Happens to me š
Make sure that you run 0.12.1 or newer
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
You can open the console of container and use the built in network tools.
Some examples, but not an exhaustive list:
- ping
- hostname
- wget
- curl
- nslookup
@joejoe13
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
That seems very weird. Did you allow networking capablities ?
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
It should work. Can you try to ping another container with its name? (One that's on the same adapter)
like
http://sonarr/ or similarUnknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
I am sorry I can't really help with that. I am not sure what could be going on
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
Is Plex, Sonarr and such on the same network? If yes, you can use that as the internal IP (external one as well if there is no exposed domain).
Unknown Userā¢2y ago
Message Not Public
Sign In & Join Server To View
Hello everyone
I am facing the exact same issues
What version are you running? Have you tried the above suggestions?
I am running version 0.12.2
When in my docker console I do:
wget 192.168.0.7:1234
And it doesn't respond
When doing the same wget command in my terminal (outside the docker) it works
Ok, then your docker setup is to blame. Try different network modes and allow communication between containers if possible
Alright, I'll look into my network configuration but I've followed the steps for portainer deployment that were given on github
Home | Homarr Docs
Simplify the management of your server with Homarr - a sleek, modern dashboard that puts all of your apps and services at your fingertips. With Homarr, you can access and control everything in one convenient location. Homarr seamlessly integrates with the apps you've added, providing you with valuable information and giving you complete control....
Yes my bad
Okay š
When I ping my router (192.168.0.1) it works
But when I ping the IP of the machine running the docker container (192.168.0.7) it doesn't work
(I ping from the console of the homarr container)
Can you try to set network mode to bridge?
Sure
Do you mean joining the network named bridge ?
Yes, there should be one named bridge
Done, restarting the container
Still cannot ping the IP of the host machine (192.168.0.7)
I can ping other machines on my network
But not the host machine
Let me check if I can use 127.0.0.1 instead
I can ping 127.0.0.1 but the wget doesn't work
I assume the 127.0.0.1 is not going to my host machine
Can you try
host as a network mode? Please make sure that you understand the risks of the different network drivers: https://docs.docker.com/network/#network-driversI'll try
Yes, that probably won't work from the container
I must be doing something wrong
I have the following error when starting the container with host mode:
Invariant: failed to start render worker Error: getaddrinfo ENOTFOUND ghcr-io-ajnart-homarr-1
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
errno: -3008,
code: 'ENOTFOUND',
syscall: 'getaddrinfo',
hostname: 'ghcr-io-ajnart-homarr-1'
}
Okay. That's a known bug (reported on GitHub)
I think you'll have to fix your bridge setup
Let me check with another container that is on the same bridge network
I have a bunch of containers, I was previously using Dashy but I wanted to migrate to Homarr
Yes, sounds good š
You might need to experiment a bit with the different modes....
(I am on a synology DS920 by the way)
(I don't know if it is relevant)
Maybe it is... You just had the same errror like in this issue:
https://github.com/ajnart/homarr/issues/973
GitHub
ENOTFOUND error after updating to 0.12.2 Ā· Issue #973 Ā· ajnart/homa...
Environment Docker Version 0.12.2 Describe the problem Hi, I just pulled the latest image but when I try to start the container I get the error: Invariant: failed to start render worker Error: geta...
I wonder if the latest docker changes in Synology caused issues on the network side because my dashy is acting really weird too
I have the exact same issue, I cannot ping or wget anything that is on the 192.168.0.7 (my NAS running docker) from my dashy container anymore
It could be, but users with other systems reported this issue too
I doubt that Synology is causing it
Maybe there are two separate issues ?
One issue that is preventing me from running Homarr in host mode
And one issue that might prevent my docker containers from reaching the IP of the machine that is hosting them
Yes, that is most likely the case. The network issue is probably not related to Homarr though
I have found the root cause, it is indeed a synology issue
Hello again, I have resolved my network issues, but I have a hard time getting Plex ping to work
Oh never mind, it turned green eventually