So I was standing up a temporary plex server to test some things before I commit my main plex server to some upgrades, and I ran into the most annoying problem... For whatever reason. the system insists on using 192.168.1.1 for the plex jail. That IP is a reserved IP on my network, so it was free, but NOT available for use. It is not in the DHCP range, so where did this come from and why? When I change it, the server just errors out when I try to start it from the plugin services gui page.
I do a lot of router development, and I have that IP reserved for when I must attach a build test to the network. my default gateway is .2, and the DHCP range starts at 150, so there is no good reason for this IP to be forced.
The environment is a freshly built 9.10 machine running from an 8g thumb drive, with updates applied, a single raidZ2 filesystem, and a freshly installed plex plugin. It is about as clean out of the box as you can get. The server is a Dell T1700, 16g ECC memory, the filesystem is the LSI 9211-i8 flashed in IT mode with a stack of new drives. Other than the system itself not being one of the the recommended Supermicro system, I'm pretty sure I haven't made any grievous errors, this is my 10th or 12th FreeNAS build, and this has me perplexed... Granted, I only have one other Plex server, and I have reinstalled the plex jail a few times on that system, and it never acted like this under 9.3... Is this some new behavior under 9.10?
Plex seems to run fine when I leave it at the IP address it wants... I copied my content folder to the new server, and linked it to the plex jail through the gui, the only thing I've done from the command line was copy the content from the other server with scp...
When I went in to assign the IP, I was surprised that is had the one it had pre-populated, and I kept getting plugin startup errors after trying to change it... The error was something like "an error has occurred". I reinstalled the plugin several times, and finally I decided to leave the IP alone to see if it worked then, and it works fine...
I assume the errors are caused by the IP being set in more than one place, so changing it in the plugin config gui is not changing it everywhere it needs to be set. So I see two issues, inappropriate IP selection, and the gui not successfully making the change everywhere it needs to. It's not a huge problem, and this will work for the purposes of my temporary test fixture, but...
I do a lot of router development, and I have that IP reserved for when I must attach a build test to the network. my default gateway is .2, and the DHCP range starts at 150, so there is no good reason for this IP to be forced.
The environment is a freshly built 9.10 machine running from an 8g thumb drive, with updates applied, a single raidZ2 filesystem, and a freshly installed plex plugin. It is about as clean out of the box as you can get. The server is a Dell T1700, 16g ECC memory, the filesystem is the LSI 9211-i8 flashed in IT mode with a stack of new drives. Other than the system itself not being one of the the recommended Supermicro system, I'm pretty sure I haven't made any grievous errors, this is my 10th or 12th FreeNAS build, and this has me perplexed... Granted, I only have one other Plex server, and I have reinstalled the plex jail a few times on that system, and it never acted like this under 9.3... Is this some new behavior under 9.10?
Plex seems to run fine when I leave it at the IP address it wants... I copied my content folder to the new server, and linked it to the plex jail through the gui, the only thing I've done from the command line was copy the content from the other server with scp...
When I went in to assign the IP, I was surprised that is had the one it had pre-populated, and I kept getting plugin startup errors after trying to change it... The error was something like "an error has occurred". I reinstalled the plugin several times, and finally I decided to leave the IP alone to see if it worked then, and it works fine...
I assume the errors are caused by the IP being set in more than one place, so changing it in the plugin config gui is not changing it everywhere it needs to be set. So I see two issues, inappropriate IP selection, and the gui not successfully making the change everywhere it needs to. It's not a huge problem, and this will work for the purposes of my temporary test fixture, but...
Last edited: