HomarrH
Homarr16mo ago
7 replies
Krispy

Pings and integrations through reverse proxy failing

I recently (today) migrated from using a jail running docker on truenas scale to native docker with dockge. Same compose file, same paths, same everything except for which docker engine is running and which IP it's bound to.

All of my other apps seem to be fine, but homarr absolutely refuses to successfully ping anything that's going through my reverse proxy. Apps like notifiarr that are monitoring some of the same services work fine also. I've managed to reconfigure those that I can to use the internal docker network hostname and port, but that's not an option for everything.

Additionally, I can shell into the homarr container, install curl, and run curl https://sonarr.xx.cx and get the proper response.

Also interestingly, OIDC won't work either (it times out) -- but it does work in my v1 testing container (but pings don't work there either).

Get the below for example
homarr  |  ERROR  Ping timed out for app with id '88fa977f-886e-4458-a038-f6aeaa56b687' in config 'default' -> url: https://sonarr.xxx.cx)
Solution
OK, I think I figured it out
1) OIDC -- Had to remove trailing slash, not sure why that was a new problem
2) Pings-- IT WAS DNS... I have two pihole DNS servers, and previously the first one was in a seperate docker instance, moving everything into the second docker instance caused DNS resolution delays when it uses the one on the same docker instance. Swapping to the other external DNS server fixed the resolution issues. (as configured on Truenas scale network configuration).
Was this page helpful?