Try radarr.ix-radarr-4k.svc.cluster.local. The format is {container}.ix-{app-name}.svc.cluster.local. The container name for Radarr instances is always radarr, so all you need to change is the app name to that of the second instance.
1 Like
This worked thank you!
I will note just for reference that on Dragonfish and earlier the format that worked was actually the radarr-4k.ix-radarr-4k.svc.cluster.local format.
I donât know enough about any of this to say why, just putting it out there. That was the format I pulled using HeavyScript.
You just saved my weekend!
I just resently wanted to ditch truenas as a whole because i went through the hell of the core apps years ago and ended up with custom jails and a VM eating all resources of my nas, because there was no native homeassistant deployment. So i gave the migration a try from truenas core to scale and with that came the update of homeassistant which now uses postgres instead of sqlite. So i thought i could also get rid of my influxdb and connect grafana directly to the postgres until i couldnât.
The networking problem brought up some bad memories with truenas apps. And this google search would have been my last action before killing truenas out of my life.
So thank you very much! I can now successfully add postgres.ix-home-assistant.svc.cluster.local as a datasource in my grafana.
You should put a buymeacoffee link on your github 
This is excellent work, thank you! Within seconds I was able to install this and have my apps (from catalog and custom ones) all talk together as needed.
Thank you very much, sir! Youâre a gentleman and a scholar!
1 Like
Absolute legend, thank you!
1 Like
Can you confirm everything is working in Fangtooth or do you need per App IP addressing?
I can try it out in a VM when I get some time, hopefully this week. What changes should I look out for to achieve this?
Since you created the request and also a very useful workaround (many thanks!), you are more expert than me.
My guess is that for new/custom apps you can connect them to special network. for standard Apps, you might need to wait for per IP addressing change on June 1.
If it doesnât work, it would be useful to know what doesnât and whether your workaround still works.
I was just trying to see if the problem was solved as expected.
Got it, Iâll try it out and let you know
Did you already find the time to try this?
Thank you.
1 Like
Sorry, not yet! Not much free time recently 
I can confirm that as of Fangtooth 25.04.02 this workaround is still functional.
2 Likes
Hi! I have a question about Fangtooth and Dragonify. Do I still need to install Dragonify on Fangtooth for inter-container communication? I have one appâs network configuration set to âExpose port for inter-container communicationâ but still donât know how to make another app access that port.
Is there a ticket for implementing/fixing this? As far as I can see in 25.10 beta each app is still on a separate network. âPort Bind Modeâ âExpose for inter-container communicationâ seems to be the same as âNoneâ and the only option for communication between containers seems to be to âPublish port on the host for external accessâ + using the serverâs ip.
1 Like
Hi! Iâm trying to figure out how our apps should talk to each other. It seems like some of them need an IP address to connect and they fail when I try using the containerâs hostname. Could you point me in the right direction on how we should be setting this up? Iâm particularly curious about how to handle this for Arti, e.g. because if I check Is TrueNAS App, should Arti reach the container who is binding this port?
This item has been addressed, closing at this time to free up votes. If there are further feature requests in this area please submit. Those looking for support from the community with configuration please submit topics in the Apps and Virtualization category on the forum.
3 Likes