QuidNYC
Cadet
- Joined
- Jan 10, 2015
- Messages
- 3
FIXED -- I will provide my solution here and preserve my original message below in case it helps someone else:
Solution: I logged into the jail from a shell session, and edited the file /usr/pbi/plexmediaserver-amd64/plexdata/Plex Media Server/Preferences.xml and disabled the IPv6 attribute within the Preferences element. Then I restarted the server with
----------------------------------
Sorry if this is basic, but I've searched here and online and haven't had any luck with my situation.
I've got a relatively new install of FreeNAS 9.3, and I installed the Plex plugin to manage media files. I got through that whole process fine and had it working 100% (I tested access to the Plex media database and had it streaming to another PC on my home network).
Then when I was reviewing the configuration in FreeNAS, I got concerned that the default settings were basically giving Plex an arbitrary static IP mapping within the DHCP pool / assignment range that was being used by my router. So I tried changing the settings to use DHCP.
In the process of changing these settings it seems I somehow broke the web interface for managing the Plex Media Server plugin. Now, when I use the "click here to access" function for the plugin, the page fails to load, whereas it worked perfectly before. I get an "ERR_CONNECTION_REFUSED" in Chrome.
The Plex jail and Plex Media Server plugin are running. The URL used for the web UI corresponds to the IP assigned to the jail. I can ping that IP and get a response. But the web interface refuses to load. And access via the Plex Home Theater app on the other PC is also down.
I have tried everything I can think of -- I switched from DHCP back to static IP assignment, with the same results. I have rebooted the system several times. I also installed two additional plugins (Transmission and SickBeard), and they seem to have the same problem. They are installed and running in FreeNAS, but when I click to access their web UIs, the pages fail to load.
Any ideas on what to do?
Solution: I logged into the jail from a shell session, and edited the file /usr/pbi/plexmediaserver-amd64/plexdata/Plex Media Server/Preferences.xml and disabled the IPv6 attribute within the Preferences element. Then I restarted the server with
/usr/local/etc/rc.d/plexmediaserver restart. Subsequently the web UI came up.----------------------------------
Sorry if this is basic, but I've searched here and online and haven't had any luck with my situation.
I've got a relatively new install of FreeNAS 9.3, and I installed the Plex plugin to manage media files. I got through that whole process fine and had it working 100% (I tested access to the Plex media database and had it streaming to another PC on my home network).
Then when I was reviewing the configuration in FreeNAS, I got concerned that the default settings were basically giving Plex an arbitrary static IP mapping within the DHCP pool / assignment range that was being used by my router. So I tried changing the settings to use DHCP.
In the process of changing these settings it seems I somehow broke the web interface for managing the Plex Media Server plugin. Now, when I use the "click here to access" function for the plugin, the page fails to load, whereas it worked perfectly before. I get an "ERR_CONNECTION_REFUSED" in Chrome.
The Plex jail and Plex Media Server plugin are running. The URL used for the web UI corresponds to the IP assigned to the jail. I can ping that IP and get a response. But the web interface refuses to load. And access via the Plex Home Theater app on the other PC is also down.
I have tried everything I can think of -- I switched from DHCP back to static IP assignment, with the same results. I have rebooted the system several times. I also installed two additional plugins (Transmission and SickBeard), and they seem to have the same problem. They are installed and running in FreeNAS, but when I click to access their web UIs, the pages fail to load.
Any ideas on what to do?
Last edited by a moderator:
