When the share or remote option at iPhone is enabled the message “An unclaimed media server has been found on your network. Claim it now” comes up every time I visit the server on my NAS.
When I click on “Claim it now” it always says the “server settings unavailable”.
What is wrong here?
It’s been happening to me immediately after I updated this morning to latest iOS Plex. I’ve just ignored it so far.
Thanks. But my server in this case is my iPhone. The iOS app is signed in to my online Plex Pass account.
My server on NAS is also signed in at online Plex Pass account.
This doesn’t help or do you mean something else?
@rays_server said:
Thanks. But my server in this case is my iPhone.
You said:
…every time I visit the server on my NAS.
the server is not your phone, then.
My server on NAS is also signed in at online Plex Pass account.
This doesn’t help or do you mean something else?
Either this mechanism is erroneously triggered by the micro-server in the iOS client (which would be a bug) or you have a second Plex server install in the same local network where your iOS device is.
Is there a name or an IP address shown for the ‘unclaimed’ server?
Of course my main server is my NAS (QNAP) v0.9.15.6. When I visit the web app (v2.5.6) of my NAS Server WHILE my iPhone App is running in the same network (with activated share and remote controller option in the iOS app), the web app shows this message.
In total I have only the main NAS server and 4 iOS Apps with a.m. activated options in my network. And the web app shows this message for all iOS devices. All iOS apps and my NAS Server are logged in my Plex Pass account.
I hope I could explain that a little better now.
Yes. Now it is crystal clear that it wants to claim the microserver in the iOS app. Which of course is nonsense. I will relay that.
May I later ask for logfiles, if needed?
Now the iPhone is available but settings are not accessible. Has this something to do with my problem?
of you can. Just tell me what I have to do!
I’m getting this on my Mac too. It apparently wants to claim my iPad’s server.
This error should’ve been fixed by now.
Which version of Plex Web and the iOS app are you using?
I have also been getting this message recently, since about (I’m guessing) release 9.15.3 or 9.15.6. I currently have the newest version, which is 9.16.2.1827. I thought the latest media version upgrade would fix this. I get the error on my Windows IE Plex Web App screen. I have (in case this matters), an Apple TV Plex app and 4 IOS devices, all with the latest plex versions. If I click on Claim it Now, it just hangs. The only way to remove the message is to close the Plex Web App screen and open it again. The IOS devices and the Apple TV device continue to operate correctly during this Unclaim Message however. I just can’t access the Server. Like I mentioned in my first sentence, I’ve only recently started seeing this Unclaimed message and I’ve been using this for well over a year already. So I think something has changed on the Plex side. It’s annoying to have to close and open the app almost daily. Can anyone help? I’ll give more details if anyone needs more info.
Coincidently, it may have been the same time frame that I noticed a change in my windows task bar box, i.e. the little window that appears when you click on the triangle on the bottom right hand corner of the windows lower bar. I used to see Open Plex Media Server when I right clicked on the Plex icon, but now I see Open Plex (which is the name that I called my server).
I noticed that OttoKerner just previously asked what version of Plex Web and IOS that rays_server was using, so I’ll answer those questions. I’m using Plex Web version 2.5.8 and all IOS versions are 4.0.15.
thanks
Any server that is not signed in to plex.tv from within the settings / server / general page would now appear as an unclaimed server to a plex web app session.
Claiming the server would sign the server to the same plex.tv account as that which the plex web app session is signed in into.
If there are issues with this then a plex media server.log should show the sign in attemp to claim the server and if any errors are being returned or if it is signing in with the wrong account.
In response to sa2000, when I checked the Settings / Server / General page, I noticed that it is logged in because it says, “Server signed in as” and then it gives my email account. This is how it normally looks. I actually don’t have to log into Plex.tv because the Plex Web App must log in automatically. Has anything changed in the last few updates to make this message appear? The Plex Web App is working at this moment, but likely within the next 24 hours, I’ll get that message. Just a thought but maybe the newest IOS might have fixed this since the previous version (i.e. 4.0.14) was logging itself out arbitrarily.
If I get the message again, then I’ll shut down the App, open it up again, and turn on logging. I don’t know how to do that but I’ll find out how. How long should logging be set for? Is a day going to produce too much info or should I just keep it on until I get the Unclaim message again?
thanks
@EntertainMe24 said:
In response to sa2000, when I checked the Settings / Server / General page, I noticed that it is logged in because it says, “Server signed in as” and then it gives my email account. This is how it normally looks. I actually don’t have to log into Plex.tv because the Plex Web App must log in automatically. Has anything changed in the last few updates to make this message appear? The Plex Web App is working at this moment, but likely within the next 24 hours, I’ll get that message. Just a thought but maybe the newest IOS might have fixed this since the previous version (i.e. 4.0.14) was logging itself out arbitrarily.If I get the message again, then I’ll shut down the App, open it up again, and turn on logging. I don’t know how to do that but I’ll find out how. How long should logging be set for? Is a day going to produce too much info or should I just keep it on until I get the Unclaim message again?
thanks
The Plex for iOS issue should not have a bearing on claimed / unclaimed servers. New server instances or logged out servers become candidate servers for claiming. So if a server is deleted from Devices tab in Plex Web - then when it is launched it could look like a new unclaimed server.
Logging is in two places:
On the server (settings / server / general) : enable debug logging. The log files get recycled when reaching 5Mb - also get recycled on restart. Last 6 log files are kept with Plex Media Server.5.log being oldest and Plex Media Server.log being latest
In Plex Web (it is Plex Web that is detecting unclaimed server), that would be set for a browser / url combination. So for example access via localhost:32400/web on Chrome would have its own logging setting separately from access via local-ip:32400/web or plex.tv/web
So set it for the url and browser you normally use and to set it, Settings / Web / Show Advanced / Debug : set to verbose
and save changes. The amount logged is limited and so leaving it on will not result in tons of logged information.
When the problem arises, take a full screenshot (with url and time of day) and then get the Plex Web App log:
Settings / Web / Show Advanced / View Logs / Select all. copy and paste to text file
and get the server logs (zip of the Plex Media Server.log and Plex Media Server.n.log files)
Thanks for your (needed) detailed response. Right now as I check the Plex tab, I noticed that it is all black and I can’t even go to that tab, so something is wrong.
I looked at the logging options and noticed that there is a verbose option on the server but you didn’t mention that, only to enable the debug logging. Should I set the verbose option? Also, I noticed that Enable Plex Media Server debug logging was already checked. Doesn’t that mean that I should already have a log file somewhere? I can’t find the Plex media Server.log files. Where would they be?
Back to your first paragraph, you said “…if a server is deleted from Device tab…”. How would that even happen? I wouldn’t have done that. Is it automatic somehow?
Do you know if anything changed recently (in the last few versions) that would make this happen?
thanks
@EntertainMe24 said:
Thanks for your (needed) detailed response. Right now as I check the Plex tab, I noticed that it is all black and I can’t even go to that tab, so something is wrong.
I looked at the logging options and noticed that there is a verbose option on the server but you didn’t mention that, only to enable the debug logging. Should I set the verbose option? Also, I noticed that Enable Plex Media Server debug logging was already checked. Doesn’t that mean that I should already have a log file somewhere? I can’t find the Plex media Server.log files. Where would they be?
Back to your first paragraph, you said “…if a server is deleted from Device tab…”. How would that even happen? I wouldn’t have done that. Is it automatic somehow?
Do you know if anything changed recently (in the last few versions) that would make this happen?
thanks
No need for verbose logging on the server end at this point. But do the restart step to make sure fresh log files generated
I do not think you mentioned what your Plex Media Server platform is. Have a look at this support page which gives details of where the Plex Media Server.log file is for the various platforms:
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
I’m also using Plex Web 2.5.8 and Plex iOS 4.0.15. I’m able to replicate the error by starting Plex Web, then starting Plex iOS on my iPad. When I click on the claim message, I get the error “setting servings are unavailable” but it doesn’t crash. I can just click on the little house icon and go back to the main Plex Web menu.
@tikilab said:
I’m also using Plex Web 2.5.8 and Plex iOS 4.0.15. I’m able to replicate the error by starting Plex Web, then starting Plex iOS on my iPad. When I click on the claim message, I get the error “setting servings are unavailable” but it doesn’t crash. I can just click on the little house icon and go back to the main Plex Web menu.
Try to replicate the problem without involving Plex for iOS and get the diagnostics mentioned. If it only happens when Plex for iOS is launched then that is very interesting
