Fresh freenas install, can't access server setup

Server Version#: v1.15.2.793-782228f99
Player Version#: Version 3.83.1

Hello all. Yesterday morning, I decided to install the plex FreeNAS-11.2-U3 plugin for the first time in my entire life. I have never administrated the service before and didn’t know what to expect. For whatever reason, after fresh installation, I cannot enter the server setup mode.

I’ve read a few topics about this, most notably this one: So I recently updated my freenas box to 1.15.2.793_1 and i now cant get to the server setup page but nothing seems to really be the issue, and I can’t figure out what’s going wrong. There are only 2 errors in my logs about trying to clean some cached transcoding data (there shouldn’t be any yet?). The rc.d script looks fine, the rc.conf looks fine, everything is where it’s supposed to be as far as I can tell, settings have been toggled, VNET is on, I’m allowing raw sockets.

If anyone is experiencing a similar issue, has a fix, or some resources on what I need to do to fix this, please let me know.

Thanks!

EDIT: I was able to figure out a solution to this. Everything was working fine, however my installation was running in a jail, in freenas, that are both hosts on my network that are different from my work station, ie, not my localhost. It seems that you can only configure the server from localhost. Once got ssh up in the jail, I created an ssh tunnel from my localhost port 32400 to the jail’s localhost 32400, then navigate to /web/index.html?#/setup directly, it allowed me to configure my server.

Are you sure the rc.d file is correct on the LD_LIBRARY_PATH line? cause that was broken last I tried.

100% sure because I was going to hot patch it myself after I saw someone recommend to move everything from the lib folder… but it turns out that I didn’t need to because that var in the LD_LIBRARY_PATH was good. I read the whole rc.d script as well as the rc.conf and it all seemed ok to me?

But PMS does start right!?

Can you post sockstat -l46 and the PMS logs?

sure. here ya go!

USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
plex     Plex Scrip 38858 4  tcp4   127.0.0.1:11932       *:*
plex     Plex Tuner 38857 13 tcp4   127.0.0.1:32600       *:*
plex     Plex DLNA  38856 12 udp4   *:1900                *:*
plex     Plex DLNA  38856 15 tcp4   *:1343                *:*
plex     Plex DLNA  38856 18 udp4   *:13902               *:*
plex     Plex DLNA  38856 21 udp4   *:1284                *:*
plex     Plex DLNA  38856 24 tcp4   *:32469               *:*
plex     Plex DLNA  38856 27 udp4   *:60815               *:*
plex     Plex DLNA  38856 30 udp4   *:48817               *:*
plex     Plex Scrip 38848 9  tcp4   127.0.0.1:50443       *:*
plex     Plex Media 38815 60 tcp4   *:32400               *:*
plex     Plex Media 38815 61 tcp4   127.0.0.1:32401       *:*
plex     Plex Media 38815 69 udp4   *:32414               *:*
plex     Plex Media 38815 70 udp4   *:32410               *:*
plex     Plex Media 38815 71 udp4   *:32412               *:*
plex     Plex Media 38815 72 udp4   *:32413               *:*
plex     Plex Media 38815 73 udp4   192.168.1.170:12927   *:*
plex     Plex Media 38815 74 udp4   192.168.1.170:24334   *:*
plex     Plex Media 38815 75 udp4   *:1901                *:*
plex     Plex Media 38815 76 udp4   192.168.1.170:32932   *:*

log.tar (37.5 KB)

also, slight correction. Some of the rc.conf stuff is, in fact, incorrect, but it’s minor stuff, simple fix with reading the rc.d script and copy/pasting the relevant lines.

I was able to arrive at a solution to this. see the EDIT in the original post.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.