Synology NAS - Plex Media Server error (cant connect & “No Soup For You” error)

Server Version#: DSM 6.2.224922 Update 6
Player Version#: ?
NAS: Synology DS218(play)

I recently bought my NAS and everything worked great. I installed Plex and was enjoying my videos comfortably.

Since a few days however my Plex can’t or won’t access my NAS server.
I scoured all the topics that related to my problem on this forum and tried everything. Restarting, updating, resorting back to the old version(s) for my PMS and NAS, deleting user and shared folder (multiple times), etc… etc.
I spent the whole day plus yesterday evening trying every possible thing to solve this.

I even erased my content on my NAS and resetted my device… Twice.
And now, after the whole thing is clean and whiped it gives me the “No Soup For You” error once I connect with my PMS via NAS (using the IP address as URL).

Herewith my Log file and a picture of the error.

PMS Log.log (514.1 KB)

  1. Turn off Ipv6
  2. Synology FAQ - Questions, Answers, and a few How-To's

Hi Chuck,

Thank you for your swift reply.

Followed your instructions but unfortunately didn’t work.

  1. I’m using a new account so my NAS isn’t linked on there. This made me skip the first couple steps after turning off my IPv6 and removing the NAS server from the Plex account.

  2. Because I resetted my NAS the Preference is almost empty and the criteria you named in the FAQ are not present. Not sure if this creates other issues. I uploaded it entirely in this message for your convenience.

I followed http://“ip.addr.of.syno”:32400/web and this gave me an instant obstacle.
The problem that I’m getting now is an unresponsive web page (see below picture).

PS: Firewall or VPN are all off or not present on my laptop NAS server.

It’s obviously saying that my Server is intentionally blocking the connection with my Plex account… again and again. :frowning:

Preferences.txt (310 Bytes)

Capture

If you’re performing a cold-restart of PMS, you can delete Preferences.xml entirely but do remember to give the server a uniquely identifiable name different from the default (which is the host name). It’ll save you trying to track it down later.

Are you using a WIndows client?
If the firewall is disabled on the Syno (control panel - security) then the only place you can get that is host accessing it – OR – if you’re trying to access it remotely from a different location / portal mechanism.

  1. Yes I’m on a Windows laptop.
  2. Firewall is turned off on both my devices and I’m home.
  3. Also deleted my Preference file.
  4. Finally, I changed my server name to MainOne.

Still no luck…

Hi Chuck,

Good news. I got the website to work but the “No Soup For You” issue is still showing, even after I get the Server to locate first and create one Library.

After some extensive troubleshooting on my personal laptop I found the following solution.

So I figured that it must be my Internet security settings that are blocking the webpage. This is a HTTP website and anything that has sensitive data on its website needs to be a HTTPS (Secured HTTP).
So my dear laptop was protecting me and refusing me to go on it.

I troubleshooted which firewall or antivirus program was causing this. I figured this out because i went to my Windows Settings (via Start) and opened Troubleshoot and ran it on my “Internet Connections” (see the picture below.
There it stated that there was some virus or firewall blocking it (duh).

Here comes the guilty party
I pressed Advanced and got to the Troubleshooting Report. There it said that NordVPN Firewall was blockking it. Now do note that the VPN was not turned on… So I turned it on because I figured it was telling me “Dude use me to hide your VPN so you won’t be exposed much…”

After that it worked.

Worth knowing tho… I turned my LAN settings in to Automatic instead of manual confirguration.

Hope that this may help any future victim like me and assist the Plex Team in collecting these types of feedback.

Good news again… I can see my NAS Server.

I gave the Plex user (in Control Panel > User) rights to the “user groups” named: http.

Afterwards, I gave in “permissions” (at least) “Reading” rights.

Now it seems to work like a charm :slight_smile:

Cheers

So this was a PEBKAC?

It’s nice to know I have company today :rofl:

1 Like

Lol, isn’t it always…
Luckily I found the error myself!

Funny how it seems to be solved when I create a ticket after kicking myself in the head the past few days (sigh)

I have a feeling we’ll be talking again soon, Chuck LOL

It usually works out that way.

As we take the time to walk through what we’ve done,

It becomes ABUNDANTLY clear :rofl: what we DIDN’T do :slight_smile:

Now, if I could only find those lost socks. I know I put them in the washer & dryer. :thinking:

1 Like

QUick question.

Did you change the permissions for the Plex share?

Hmm, not sure… but now it’s on Read and Write for Plex user.

Thanks, It should minimally be R/W, preferred “Custom” .

I set it every time the installation script runs.
(Folks keep wanting to put media in it. They don’t realize the Plex share is for metadata only. I’m about to change the name so it’s more clear).

Np, yeah that’s a good idea.

First I saw it, I too thought it was a regular folder I could edit.
Something told me to create another folder myself and name it Plex Media (just in case), lol.

The folder was originally hidden. It required everyone use the SSH command line to access it. — NOT happening —

I might make a “PlexMedia” and “PlexMetadataOnly” (names still being discussed) shares to guide people.

1 Like

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