# Cannot claim server

**URL:** <https://forums.plex.tv/t/cannot-claim-server/554828>\
**Category:** Metadata & Adding Files\
**Tags:** server-linux\
**Created:** [March 14, 2020, 8:28pm UTC](https://forums.plex.tv/t/cannot-claim-server/554828 "2020-03-14T20:28:57Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [March 14, 2020, 9:11pm UTC](https://forums.plex.tv/t/cannot-claim-server/554828/2 "2020-03-14T21:11:00Z")

</div>

Before embarking on this:

1. make a tar.gz of the “Logs” directory in PMS.
2. you can post them here for me to check if you wish.
3. You’re looking for the obvious DNS lookup errors (Error code 6) and Permission denied (error code 13) errors.

Plex can’t claim for two reasons: 1. No communication with [Plex.tv](http://Plex.tv) and 2. Can’t write the new credentials to Preferences.xml.

> [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/21):
>
> When server and device credentials are out of sync. Use this procedure when: You receive the nasty “No Soup For You” message You’ve changed your Plex password and now have trouble accessing something. You’ve cloned the server or performed a ‘backup & restore’ using the procedures above but now cannot access the server. First choice - Preferences.xml missing or deleted. If something happened to “Preferences.xml” and you need to claim the server again, with everything being normal, Start here…

In conjunction with this, since the host is remote, you need a proper SSH tunnel. Be certain that is properly established.

We recommend port 8888 for the local port and `8888:127.0.0.1:32400` as the report port specification.

---

_[View the full topic](https://forums.plex.tv/t/cannot-claim-server/554828)._
