Truenas Scale Installed Plex and pi-Hole

Installed Plex first and that was running ok. Liked the idea of pi-Hole installed that and all went downhill , as Id enabled dhcp from pihole, and Plex had a dhcp still from the Router, the thing got sooo confused . Although now Plex runs, ( pi-hole not started ) these are the only 2 apps at the moment, it takes an Age to go from startup to actually running, like 10 minutes at least. Is this normal? Im sure it was much quicker when was the first and only App on board.
There are initially indications of network activity in the App of 40 to 67MB/s but then will show only 3 or 4 kilobytes, and refreshing the screen eventually shows running.
To get the App working after my dhcp hiccup, I had to several times delete the assigned Pool and re establish it.
Im tempted to delete Plex and Pi-hole and load Plex again after and reboot.

Its very strange too coming from Core that apps take on the persona of the main IP address plus a port number rather than a separate dhcp given address as in Core.

Id very much appreciate some insight if this is working correctly or I do need to reinstall it…?

Many thanks for reading…

Dave Sunny Stamford.

The Setup…
N5105 Lowpower motherboard
32GB Ram
4x 8TB Hard Drives
Truenas Scale Dragonfish 24.04

Silly question: Did you reenable DHCP on your router after stopping Pi-Hole? You didn’t mention DNS resolution, but you might have to undo that on your router as well.

Yes I did it was only one entry pointing back to pihole… now square router giving dhco and dns resolution but Plex is v unhapy.
Ramped up Pihole… seconds to become active… somethings not right in the State of Denmark, or Stamford !

Many thanks for your reply tho.

When you install Pi-hole or similar apps, be sure to not make TrueNAS itself dependant on anything that the app provides.

If, for example, TrueNAS uses Pi-hole for DHCP and/or DNS resolution, you’re going to be in for a bad time. The apps will not be available when the system boots and if anything prevents your app from starting you will not be able to access your server.

2 Likes

Further to my original post, took the view all was v unwell, deleted plex deleted pi hole.
rebooted…
Installed plex…
Installed emby…
Now it seems unless you STOP any working Apps on my system you will be waiting till the end of time for anything to happen, 30 mins in i stopped Plex. restarted the install of Emby and it worked.
Now fighting with emby to see any data im pointing to ? it doesnt traverse in the Web App to get to the Folder.
Now waiting for the whole thing to load from start 15 mins in … still deploying cant be right, can anyone confirm these sort of timescales?
Either ive got a broken Truenas Scale or this Kubernetes “stuff” isnt a patch on a VM ware spin up. On my sytem its v flakey takeing ages to load, network activity flashing between 600-1.1Mb/s then 0.00 , no Ram or CPU activity…

Broken isnt it?

On the Kubernetes window to the right this shows…:

2024-10-27 19:42:48 0/1 nodes are available: 1 node(s) didn’t have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod…

2024-10-27 19:42:48 Created pod: emby-5f7c74575d-9md2s

2024-10-27 19:42:48 Scaled up replica set emby-5f7c74575d to 1

2024-10-27 19:40:28 Scaled down replica set emby-7d7cd7df6c to 0 from 1

2024-10-27 19:40:28 skip schedule deleting pod: ix-emby/emby-7d7cd7df6c-qx8jf

2024-10-27 19:40:28 Deleted pod: emby-7d7cd7df6c-qx8jf

2024-10-27 19:35:42 Scaled up replica set emby-7d7cd7df6c to 1

2024-10-27 19:35:42 Created pod: emby-7d7cd7df6c-qx8jf

2024-10-27 19:35:42 0/1 nodes are available: 1 node(s) didn’t have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod…

If only i could understand what it means?

I can see Im gonna have to knock up a test box to compare notes…
Can anyone please shed some light on this, else how do you run apps?
The Saga continues, !

Goodnight all,