Can't access first-time setup of a new server on my network

Server Version# NAS: 1.18.5.2309-f5213a238
Server Version# NAS: 1.18.3.2129
Player Version#: ----

Hi,

for a couple of years now, I’m running a Plex Media Server on a Mac Mini. I also was using the Mac as a media PC.

Reality is that software providers drop support for media PCs more and more (like Plex did). I decided to change my setup and are now using an Android TV as client and a Synology DiskStation as server.

I now installed the server on my NAS. The problem I have is when I open the web interface (http://localnasip:32400/web), it redirects me to the login screen. When I’m logging in there, it tells me, that the server isn’t reachable. It seems to search for my old server that was running on my mac and doesn’t offer me to set up my new server on the NAS.
My NAS is using the same IP, my Mac was using before.

Any ideas?

Hi Trumpy,

thanks for the quick reply. I tried that. After logging in with my credentials, it tells me: Access denied. See attached screenshot (unfortunately, it’s in german).
Looks like, my user isn’t allowed to log into the freshly installed instance of the server.

Hm… Do you mean, the DiskStation user? I’m logged in with a user that belongs to the administrators group. Isn’t that sufficient?

Is my DSM user even relevant? To Plex, I’m logging in with my Plex account.

What is the LAN IP of the NAS?
What is the LAN IP of the computer you are using?

It might also help to manually download the Log files and attach them.

Hi Trumpy and ChuckPa,

I was able to track down the issue in the logs. I was accessing the server using a domain name instead of the IP address of the NAS.
Then, I got the error:
Request came in with unrecognized domain / IP ‘nas.mylocaldomain.lan’ in header Host; treating as non-local
Using the IP instead, server setup screen appeared. Now, after the server was set up, it’s not a problem to access it with the domain name again.

I find this behaviour quite odd. But I have to admit, that I’m only using the DNS of my TomatoUSB router. Probably, with a proper DNS this would work.
Still, treating a .lan address as non-local is kind of funny.

Anyhow, thanks for your support. In case, this also happens with a proper DNS, I’d suggest to fix it.

Hi Trumpy,
how did you get a moderator status with doing such comments?

Why did you not bother to read my solution?
The issue wasn’t in any way related to the user. I was using my own plex account to log in which is an admin user.
The issue was some strange assumption that the domain name of my nas wasn’t a local host. I didn’t investigate further why the heck Plex is displaying the message that I’m not allowed to access this server in such a case.

So, it’s not very supportive, when you ask the question: “Why are you not logging in as admin?” even though you don’t even know, if I’m logging in with an admin.

I’d assume, it’s more the tone that doesn’t let you sound like a moderator.
From a moderator, I’d expext the first part of the third question you asked now. Something like “It seems to me, you didn’t follow my instructions properly. Was there something unclear?”

And here, what you are doing “or was there some other reason you ignored them”. Why do you assume that I ignored your instructions? I didn’t ignore them at all. I just didn’t expect that I can’t replace YOUR_NAS_IP_ADDRESS with my local domain name for this server. After all, DSM is also using the domain name when I press the Plex button in Disk Station and this is what I did to open the Plex Web.
If you knew that it is important to put in the IP and not the domain name when writing your instructions, it would have helped to point that out.

The message was displayed because you were attempting to login using a domain name. If that was allowed then any Tom, Dick or Harry could log into your Plex server, they would only need to guess the password.

The error message doesn’t state that at all. It gives the impression that I’m trying to access my server, but don’t have the rights to do so.
And how should one of these three guys be able to log into my server, just because I’m using a local domain? This domain isn’t public at all. In case, you want to check, try to ping it. It’s a domain for my local network.

Had I been aware that you were using a domain name instead of following my instructions my question to you would have been very different, don’t you think?

I don’t know. Probably. But how should I know that this is relevant. Usually services can work with domain names. You also didn’t know that it is relevant to ask me that.

do not answer simple questions

I didn’t answer the question, because it wasn’t clear to me. That was the reason why I asked a couple of questions back.

Also note that your instructions didn’t were the solution to the problem. If I wouldn’t have followed your instructions and just used the IP in the first place, everything would have worked.

Look, I think, this doesn’t go anywhere. I was really thankful for your support even though your question “Why are you not logging in as admin?” was a bit irritating. I didn’t expect such quick support and this was very positive. But your comment after the problem was solved already was just inappropriate.

The questions from ChuckPa on the other hand were the right ones to hint me to the problem and helped me to solve it.

I’ve interpreted this comment more as “Don’t just copy/paste YOUR_NAS_IP_ADDRESS”. I wasn’t expecting that I can’t use a domain name instead. This isn’t such a stupid assumption.

You can do it and I followed them. I don’t complain about your instructions. Just about your reactions.

Because you asked why I didn’t log in as an admin even though you didn’t know if I was logging in with an admin.

Sorry for that. Feel free to point me to the errors. I’m always eager to improve.

I don’t know, if he already had a supicion. But the question about the IP addresses and directing me to the logs made me look for addresses in the logs which solved the issue for me.

Again. I don’t want to argue. You for sure wanted to help. You were complaining that I’m wasting your time. With offending me after the problem was solved, you now wasted even more time arguing with me. So, let’s just stop this conversation before we waste even more time.

May I ask a question?

What are

  1. the LAN IP addresses of the Synology and
  2. the computer which is accessing it

The issue is solved already. The problem was that Plex “thought” that I’m using a public address just because I was using a domain name instead of an IP when opening Plex Web. The error message that I got because of that led to wrong assumptions.

Thank you for clarifying where the error occurred.

We try to make it clear that the LAN IP is needed because of how PMS security is configured (protects your server installation should it ever forget who owns it).

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