Fresh Install - No soap for you - you have no access to this server

[nikkon]

Hi all,

this problem I had started when I decided to upgrade from FreeNAS to TrueNas. Plex jail crashed, and I decided to go for a fresh plugin install.
After I installed the plugin, I got this message. I deleted the plugin and manually installed a jail + plex server on it—same result.
I suspect the PSM software to have some issues running on Jails because I did install it on a VM, and the server got recognized, and I can add local libraries.
I have open tickets on the plex community forum, but nobody is replying over there.
Any clue why this is happening?

TrueNas version : TrueNAS-12.0-U1.1
Jail version: 12.1-RELEASE
PSM version: 1.21.1.3830

thanks in advance

 

[ThreeDee]

I just lost my jail drives and reinstalled the Plex plug in without issue plex-pass Version 1.21.1.3876
Plex was running via the plugin plex-pass (beta) version without issue as well.

Doesn't solve your issue I know .. but maybe it's a jail configuration issue on your end or similar .. ??

..or maybe it's an issue with the PMS regular plugin (of which I have never tried) .. try the PMS (Beta) plug in if you haven't already. Doesn't matter if you have a plex-pass subscription or not

 

[nikkon]

thanks for replying. I just installed the PSM beta plugin. Same issue.
I also have a plex-pass account.
I've enabled the verbose more on PSM logs & the only errors I see in Plex\ Media\ Server/Logs/Plex\ Media\ Server.log

Jan 17, 2021 09:35:42.779 [0x80b785c00] ERROR - Error issuing curl_easy_perform(handle): 7
Jan 17, 2021 09:35:42.779 [0x80afea100] ERROR - Error issuing curl_easy_perform(handle): 7

 

[G8One2]

I run into this all the time. Always ends up being that I was not on the same network or subnet, as the jail.

 

[stualden]

My suspicion would be the same as G8One2's. The address showing in your browser there looks strange - were you planning to use NAT on the jail? Easiest instead to set a static address for the jail that's on the same network as the rest of your setup, or (better) use DHCP and hand it a fixed lease.

 

[nikkon]

let me show you how is configured:
Lan network is 172.16.10.0/24

 

[stualden]

Hmm - network settings look right, so it's something else. Are all the various Plex processes running? Compare against what I see here (I tried ps -Ao user,command -U plex):

plex /usr/local/share/plexmediaserver/Plex_Media_Server (Plex Media Server)
plex Plex Plug-in [com.plexapp.system] /usr/local/share/plexmediaserver/Resourc
plex /usr/local/share/plexmediaserver/Plex DLNA Server
plex /usr/local/share/plexmediaserver/Plex Tuner Service /usr/local/share/plexm
plex /usr/local/share/plexmediaserver/Plex Media Scanner --match --type 8 --log

 

[G8One2]

Hmmm..... Well I don't know what your specific issue is, I just know that on my particular network here at home, the machine that I use to access the web management page, needs to be on the same subnet as the machine hosting plex. Because my wireless network is on a different subnet, I have to manually jack into my LAN with an ethernet cable to configure Plex through its jail IP. Otherwise, I get the "no soup for you" message. This is the only time I have ever encountered this.

 

[nikkon]

geonosis# ps -Ao user,command -U plex
USER COMMAND
plex daemon: /usr/local/share/plexmediaserver-plexpass/Plex_Media_Server[37539] (daemon)
plex /usr/local/share/plexmediaserver-plexpass/Plex_Media_Server (Plex Media Server)
plex Plex Plug-in [com.plexapp.system] /usr/local/share/plexmediaserver-plexpass/Resources/Plug-ins-6c22540d5/Framework.bundle/Contents/Resources/Versions/2/Python/bootstrap.py --server-version 1.21.1.38
plex /usr/local/share/plexmediaserver-plexpass/Plex Tuner Service /usr/local/share/plexmediaserver-plexpass/Resources/Tuner/Private /usr/local/share/plexmediaserver-plexpass/Resources/Tuner/Shared 1.21.1
geonosis#

 

[nikkon]

Hmmm..... Well I don't know what your specific issue is, I just know that on my particular network here at home, the machine that I use to access the web management page, needs to be on the same subnet as the machine hosting plex. Because my wireless network is on a different subnet, I have to manually jack into my LAN with an ethernet cable to configure Plex through its jail IP. Otherwise, I get the "no soup for you" message. This is the only time I have ever encountered this.

this is new. I will try this one as well and see how it goes. I was indeed accusing from a different network

Update:

problem solved. PSM is unable to claim the server if it's called from a different netwrok. as so I just tunneled the traffic:
ssh -L 32400:<plexip>:32400 <plexip> -v
then 127.0.0.1:32400/web/ made the rest.

thank for helping G8One2 your hint gave me the idea

 

[stualden]

I just installed a fresh Plex on a new server yesterday (with the danb35 script) and ran into this problem myself, because I wasn't local to my LAN, I happened to be on my road warrior VPN. I ended up fixing it by adding an entry to Plex's Preferences.xml:

allowedNetworks="10.165.5.0/255.255.255.0"

where that network (in my case) is the one for my OpenVPN connection. So that's another alternative to nikkon's tunneling approach.

Once you can get access to the Plex Media Server, you can further modify this allowed networks list under Settings...Network; you don't need to edit the Preferences.xml file directly again.

 

[Noviets]

this is new. I will try this one as well and see how it goes. I was indeed accusing from a different network

Update:

problem solved. PSM is unable to claim the server if it's called from a different netwrok. as so I just tunneled the traffic:
ssh -L 32400:<plexip>:32400 <plexip> -v
then 127.0.0.1:32400/web/ made the rest.

thank for helping G8One2 your hint gave me the idea

I tried doing this as I am having the same issue but I'm getting

Code:

debug1: channel 3: free: direct-tcpip: listening port 32400 for 192.168.2.234 port 32400, connect from 127.0.0.1 port 55282 to 127.0.0.1 port 32400, nchannels 4
debug1: Connection to port 32400 forwarding to 192.168.2.234 port 32400 requested.
debug1: channel 3: new [direct-tcpip]
channel 3: open failed: connect failed: Connection refused

I have TCP Forwarding for SSH enabled.

 

[smithj33]

this is new. I will try this one as well and see how it goes. I was indeed accusing from a different network

Update:

problem solved. PSM is unable to claim the server if it's called from a different netwrok. as so I just tunneled the traffic:
ssh -L 32400:<plexip>:32400 <plexip> -v
then 127.0.0.1:32400/web/ made the rest.

thank for helping G8One2 your hint gave me the idea

Thank you so much! I am setting up a 2nd server and kept getting Not Authorized when going to the IP of the server from a client on a different network. Also did not know about this tunneling voodoo, but it allowed me to setup my 2nd server.

 

[raynaud]

Hi, I have de same problem, and i don't know where to begin, i was deleted and reinstall and in my accout plex delete my server too hope to view the new server but never connect, and allway show "Not authorized", I was install as plugin from freenas.

What can i do for fix it?, please I'm a noob XD