```
That doesn’t look related to this issue, but I don’t know.
Do you have any suggestions? Considering [the amount of similar questions](https://www.google.com/search?hl=en&q=plex%20unauthorized%20you%20do%20not%20have%20access%20to%20this%20server) I hope there is a solution to this.
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [September 18, 2022, 5:35pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/8 "2022-09-18T17:35:08Z")
Grab the logs for me please.
Something else going on in there.
---
### Author:  [@milias](https://forums.plex.tv/u/milias)
#### Post date: [September 18, 2022, 6:10pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/9 "2022-09-18T18:10:36Z")
Here you go!
[logs.tar.gz](https://forums.plex.tv/uploads/short-url/4HUNBqcYFJ2AfcHnCfvKqLZ0v9p.gz) (2.1 MB)
In the meantime, I tried a couple more things:
- I spin up a container using image `plexinc/pms-docker` and the exact same behavior occurs. After providing the claim token using `PLEX_CLAIM`, the server is unauthorized.
- I created a new account and trying to claim the “bare metal” installation gives the same result as before. With a freshly spin up container, giving the claim token from the newly created account, I get this when accessing `http://127.0.0.1:32400/web/index.html#!/get-plex-media-server`.
It tells me to install plex media server… from the server, this is because the account is “unauthorized” to access it.
- If instead I don’t provide the environment variable `PLEX_CLAIM`, I can access the server but of course it says it’s unclaimed.
I am now even more confused, to be honest. What is happening that a brand new account cannot claim a server? Just in case it matters: the container is running on a separate machine (different network), and I’m accessing using “private browsing” to make sure there are no cookies from my normal account influencing anything.
Thank you very much for your help 🙂
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [September 18, 2022, 6:45pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/10 "2022-09-18T18:45:12Z")
@milias
Do you want me to be polite as I report my findings? 😈
1. Why am I seeing Redhat in a Synology forum? 🤔
```auto
Sep 18, 2022 18:42:42.490 [0x7f15813fcb00] INFO - Plex Media Server v1.28.2.6151-914ddd2b3 - unknown PC unknown - build: linux-x86_64 redhat - GMT 02:00
```
1. Borked ‘AllowedHosts’ setting in preferences. You enter discrete IP addresses without netmask of /32 🙂
```auto
Sep 18, 2022 18:42:43.317 [0x7f1580df3b00] ERROR - Illegal whitelist has all-zeroes netmask
```
1. And the $50 question 😈
– What’s the DNS / network set for? 🤦♂️
```auto
Sep 18, 2022 18:42:48.922 [0x7f157eefeb00] WARN - [HttpClient/HCl#3] HTTP error requesting GET http://plex.tv/pms/:/ip (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Sep 18, 2022 18:42:48.922 [0x7f157f7eeb00] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):
```
#### Conclusion:
1. Not Internal server or API error
2. PEBKAC
🤣
---
### Author:  [@milias](https://forums.plex.tv/u/milias)
#### Post date: [September 18, 2022, 7:03pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/11 "2022-09-18T19:03:10Z")
… damn!
Thank you for pointing out the DNS issues, [why is it always DNS!?](https://www.dnsfilter.com/blog/why-is-it-always-dns)
At least now I can say what the issue was: for something unrelated I commented out the nameservers from my `/etc/resolv.conf`, because they are configured in a different way… and that seems to break Plex 😛 ! Regardless, putting them back indeed fixes the issue.
To answer for your curiosity:
1. Next time I’ll try to find a more appropriate subforum, it seemed like a similar situation at the start. This is arch linux (btw).
2. I completely forgot I had added `allowNetworks="0.0.0.0/0"` to `Preferences.xml` (now removed), which I guess Plex doesn’t like too much.
3. Good idea to check more log files next time, not only one!
Thank you very much for guiding me in the right direction 🙂
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [September 18, 2022, 7:29pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/12 "2022-09-18T19:29:01Z")
I have my own name servers and Plex doesn’t break.
I’m curious how you did that.
Are you putting them in the search clause ?
Yes, 0.0.0.0/0 will break Plex and about any other program which is subnet aware. 🙂
I hope I, at minimum, made this 🍕 and 🍺 laugh worthy?
Don’t worry about the sub-forum. I was _purely_ busting your chops 🕶
---
### Author:  [@milias](https://forums.plex.tv/u/milias)
#### Post date: [September 18, 2022, 7:37pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/13 "2022-09-18T19:37:54Z")
You definitely made it fun! 🙂
Have you tried using an empty `/etc/resolv.conf`? I’m using `systemd-networkd` and setting the nameservers as
```auto
[Network]
DNS=1.1.1.1
DNS=1.0.0.1
```
So they appear in `/run/systemd/resolve/resolv.conf` and are picked up by other programs without issues. However the “more traditional” `/etc/resolv.conf` is empty.
… I just realized I need to link one to the other. This should properly fix the issue _and_ I can still specify them as I wanted.
I have to say, ackchyually, that `0.0.0.0/0` is a perfectly valid network!
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [September 18, 2022, 8:13pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/14 "2022-09-18T20:13:21Z")
> [@milias](#):
>
> … I just realized I need to link one to the other. This should properly fix the issue _and_ I can still specify them as I wanted.
🌞
That’s the trick; tell systemd to stop interfering
---
### Author:  [@system](https://forums.plex.tv/u/system)
#### Post date: [December 17, 2022, 8:13pm UTC](https://forums.plex.tv/t/plex-on-synology-cannot-add-media-server/811230/15 "2022-12-17T20:13:32Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.