Can't Log Into or Claim Server

Server Version#: 1.41.5.9522 (although it says there’s an update, there is not)
Synology NAS Ver#: DSM 7.2.2-72806 update 3

Hello,

I had a power outage a few days ago, for 25 hours. This started as an inability to see server content on Fire TV.

On the Server, I uninstalled and reinstalled several ways (Uninstall Only; Sign out and Uninstall this server; and Erase all of Plex Media from this Server) and eventually after the last step, removed the media directory. Each time I received a message that ‘there was a problem logging in,’ and ‘there was a problem claiming the server.’

I’ve also tried signing out of Plex, then trying to claim the server, forcing a sign in. No joy.

I’ve confirmed that the time is correct on the Server and that article went on to suggest a ‘soft-reset’ however, can’t find any info on this.

Can you provide assistance?

Thanks,
Seaghan

The ’ problem logging in ’ means you Syno can’t get out to the internet correctly.

The Syno has built-in clock so it’ll sustain current date/time for a long time.
It will only drift a few seconds after several months.

I looked at your account on plex.tv

I see you have two network adapters connected
( 10.0.0.8 and 10.0.0.9 )

Please open the Syno desktop (http://10.0.0.8:5000)

Now to figure out what’s happened to your network config during the power failure.

Control Panel - Network - Network Interface

Did you set ethernet addresses manually or let the modem/router assign them.

If you set by hand, except for your LAN and my LAN being different, do you have similar for eth0 ? (10.0.0.8)
– points to your modem/router for DNS and Gateway
– eth0 is the Default Gateway

Thank you for helping.

I have not set the IP addresses manually, and allow them to set via DHCP.

Oddly, they are not 10.0.0.8 and .9 respectively, nor were they ever. They are and have always been 10.0.0.108 and 10.0.0.109

Is this something that can be corrected at my end (in Plex Server) or at your end?

Thanks,
Seaghan

@seaghanhancocks

Please accept my apology. I read 108 & 109 but wrote 8 and 9. Total Brainfart.

In your network configuration for the “108” adapter,

  • Is this the eth0 adapter ?
  • Is the “Set as default gateway” box checked ?

I’m asking because DSM has the nasty habit of dropping that.

Additionally, regarding Plex, when you have a power outage, the Preferences.xml file (which is what identifies the server as yours) can be somewhat damaged.

Have you used the “Plex Claim Token” method to reclaim the server
-and/or-
Used an incognito window to open http://10.0.0.108:32400/web ?

The Plex Claim Token method will always work as long as the internet connection is good (Syno → internet)

I recommend:

  1. Try opening the server using the incognito method first (easiest)
  2. That failing, use the Plex Claim Token method I show below.

No worries, re Brainfart. I’ve had those myself :wink:

The 108 is the eth0 adapter (assuming that’s the same as LAN1).

I’ve confirmed that the “Set as default gateway” box IS checked. You were correct. It was unchecked.

I tried to claim the token (after correcting the “set as default gateway”) but no change.

I tried using incognito method, however received the same message, “Problem logging in.”

I worked through the “claim token” method, however received the message…

(If you can’t see the image, it says, "Failed to install the package. Error: Could not complete dialog with Plex.tv. Unable to claim token.

Either installation time was too long or difficulties communicating with Plex.tv exist.

Please try again or seek assistance in our Support Forum."

I hit back, and installed without the token.

Tried to claim the token again with no change.

Thanks for hanging in there.

Hmm. This is sounding like DSM is being dumb.

  1. Please confirm that the NAS can open Package Center and search for apps
    (this confirms basic internet connectivity)

  2. Would you be adverse to merging the two (108 & 109) LAN 1 & LAN 2 into a single adapter ?

Hi ChuckPa -

I can open and peruse the packages in the package centre. I can also click on apps that haven’t been loaded, and in a few seconds, it populates the window with it’s icon and a description of what the app is.

I don’t have any other package sources I can add, unless you have a recommendation.

I don’t have any issues with the two adaptors being merges to a single one. The only reason there’s two, is because there are two physical lines running to the NAS. If it makes it easier, I can physically unplug one of them.

Thanks,
Seaghan

If you don’t mind, would you consider the following.

  1. Unplug one of the adapters (whichever isn’t your primary)
    – I assume .109 is the “secondary” ?

  2. Restart DSM & Plex

  3. Now, using an incognito window (by IP) with you also on the same 10.0.0.x subnet (important) - open and try to claim it.

If that doesn’t work,

  • Stop PMS
  • Using FileStation, navigate to PlexMediaServer/AppData/Plex Media Server
  • Right-click LogsCompress to Logs.zip
  • Download the zip file
  • Upload it here.

That zip will let me see what’s happening / going wrong.

Hi Chuck -

That seemed to have fixed the problem.

I disconnected the secondary adaptor, rebooted the system, and logged in using incognito and all seems well, both local computer and on my FireTV.

If this happens again, I suspect the problem was that the server needed a hard reboot after fixing the “Set as Default Gateway,” glitch at the Server, although it seems odd after a power outage, that it would need another hard boot.

Although Plex is still reporting there’s an update (and there doesn’t appear to be one), that’s a minor point. Current running version is 1.41.5.9522.

Thanks for your help and patience.

Regards,
Seaghan

The problem is rooted in how DSM uses the adapters interchangeably with disregard.

Plex is sensitive to which adapter it sent from and which adapter the response is received (should be the same)

Given you’ve confirmed this is ethernet adapter related, I have an option for you.

  1. stop plex
  2. plug both cables in
  3. create a bond adapter by merging the two ethernets into one.
  1. Keep the DHCP setting you have
  2. Select Adaptive Load Balancing (No special switch config required)
  3. Select eth0 and eth1
  4. Make the new bond adapter ( Bond0 ) the default gateway
  5. Apply
  6. Confirm it’s still at the 108 address
  7. Start Plex

What you’ll get is both adapters merged into one, aggregated and balanced 2 Gbps of total throughput (assuming multiple 1 Gbps devices talking)

Now start PMS.

It won’t get confused anymore about the adapter.
It will use ‘bond0’ from this point forward

Hi Chuck -

That’s very interesting. I’ll try it over the weekend and let you know.

Thanks for the information. I’m usually pretty good at these kinds of things, but this was a real head-scratcher.

Regards,
Seaghan

Hi Chuck -

Just made the changes at the Server and everything is working great.

Thanks so much for your help.

Sincerely,
Seaghan

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