Server Version#: 1.18.5.2309-f5213a238
Player Version#: Plex Web
Oh hi. I must have screwed up and just can’t get it to work.
Having installed a Plex server on my new Synology 420+, which is replacing my old Mac mini since Apple has more or less discontinued macOS server. There wasn’t an easy way to move data (whyy) between Plex server platforms, so I installed a clean server, but
I just can’t claim the server!
I’ve tried this at least twice:
uninstall the package
trashed everything in /plex
reinstalled package
clean cookies, restart web browser
go to package link, http://[localip]:32400/web
log in to my Plex account with email. (normal warning about trusting IP)
Settings → Claim server. It just spins forever and seems to give up with no error message, reloading page and it’s not spinning any more.
So I guess the problem isn’t on my server, it should be on my network or Plex account. I’ve forwarded port 32400 to this internal IP. My old server has moved to port 32500 and is working great so there is no stress. Restarted router. What more can I do?
Thank you so much Trumpy for trying to help me with this weird problem.
Problem persist. I’ve done your list, with some changes:
I’ve used a clean browser never used for Plex before. (couldn’t log out)
I trashed all content of the Plex data folder instead of renaming preferences.
Used local IP, no domain name, quick connect, no vpn just a router. This is the log. This time I stopped the server before copying the logs and no settings made except going straight to claim server.
When I look at the log all I see is page up and down with errors.
Thank you for spotting that Trumpy!
However, only one of them is used (eth1), the other one is a manual configuration not used anymore. Only one cable attached. I’ve removed it now in case Plex has some issues with that. The problem do persist unfortunately.
(1Gbit is enough for me, I don’t have faster network. They did offer me to raise from 1Gbit/s to 10Gbit/s for another €10/month, but I don’t know what to do with that - maybe later)
Ok I FINALLY found what I made wrong. This could have been so much easier if Plex had shown some error messages. So I borrowed a friends Synology to install Plex, and it did work after some soup-changes. I knew it was something on my unit, but since I’ve resetted everything it couldn’t have anything to do with Plex.
Main issue
Ok I’m a bit ashamed for this. DNS was for some reason set manually to an old router. This is not done under network settings in Synology settings but under General. Interesting is that I didn’t found this problem until another app showed me an error message which Plex never did. All other services I’ve setup did work, guess they didn’t need working DNS.
smaller problem 1, no soup for you:
When Plex is installed on Synology and you select Open app, it will open a webpage which is domainname:32400/web which just result in a page that say “No soup for you” that in translated version make no sense at all. It also say that I must login with an account that have rights to this server.
First time claim must be made from [local ip]:32400/web which must be written manually by user and it doesn’t say anywhere during installation. For Synology users this is very strange, all other apps are using Synology’s own account system, and here is something weird about soup and no account. This onboarding can be done better, at least write this link in description of the package in package center.
smaller problem 2, no error message for network problems.
So now I know that the problem was Plex couldn’t connect to its cloud service. It doesn’t say this anywhere, the process just go around in a circle without any report of a problem. So better problem reporting please.
I hope someone with a problem like this might find this helpful. And I hope Plex tries to do the onboarding experience a bit better for synology users.
- maybe later)
