Raspberry Pi 2 running 0.7.0 or 0.7.1 will not sign in

Dev Community Apps & Creations
1

I have two new pi2’s that I cannot get to sign-in using Rasplex 0.7.0 or 0.7.1. I’m running Windows PMS 0.9.12.12.1459-49fe448 and all I having is spinning.

The Pi2’s are ethernet connected to the same switch as the PMS.
Adding NTP settings have not helped.
Adding manual IP of server does not allow them to connect.
Log shows my PMS Server name without signing in.

I can get them to connect by loading 0.6.0, signing in, then upgrading from the Preferences menu.

However, interestingly I can can sign-in to a freshly imaged 0.7.1 on a Raspberry Pi 1 b.

See an excerpt from the PHT log from one of the Pi2’s below.

! 00:00:06 T:1970679808 NOTICE: -----------------------------------------------------------------------
! 00:00:06 T:1970679808 NOTICE: Starting Plex Home Theater (0.7.1), Platform: Linux (RasPlex (official) - Version: RP-0.7.1, 4.1.6 armv7l). Built on Aug 31 2015
! ------STUFF HAPPENS------
! 18:53:14 T:1794110544 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! 18:53:14 T:1970679808 NOTICE: Raspberry PI firmware version: Aug 20 2015 17:56:26
! Copyright (c) 2012 Broadcom
! version 3f87086448257aa66881de858a0b4b0e6daa8719 (clean) (release)
! 18:53:14 T:1970679808 NOTICE: ARM mem: 752MB GPU mem: 256MB MPG2:0 WVC1:018:53:19 T:1819276368 NOTICE: Thread Jobworker start, auto delete: true
! ------STUFF HAPPENS------
! 18:53:24 T:1810887760 WARNING: CPlexServerManager::UpdateReachability waited 10 seconds for the reachability stuff to finish, will just move on.
! 18:53:24 T:1700721744 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! ------STUFF HAPPENS------
! 19:03:12 T:1785721936 WARNING: CCurlFile::FillBuffer [plex.tv:443/pins.xml] failed: Timeout was reached
! 19:03:12 T:1785721936 ERROR: CMyPlexManager::GetXml failed to fetch plexserver://myplex/pins.xml : -1
! 19:03:14 T:1827664976 WARNING: CPlexManualServerManager::OnJobComplete failed to find a server on http://192.168.5.4:32400/
! 19:03:29 T:1582130256 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! 19:03:29 T:1529865296 NOTICE: Thread ConnectionTest: 192-168-5-4.421383e3ba1b4efdbb21e6a904625b45.plex.direct start, auto delete: true
! 19:03:30 T:1529865296 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! 19:03:30 T:1582130256 NOTICE: Thread ConnectionTest: 192-168-5-4.421383e3ba1b4efdbb21e6a904625b45.plex.direct start, auto delete: true
! 19:04:14 T:1598981200 WARNING: CPlexManualServerManager::OnJobComplete failed to find a server on http://192.168.5.4:32400/
! ------STUFF HAPPENS------
! 9:18:29 T:1819276368 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! 19:18:29 T:1582130256 NOTICE: Thread ConnectionTest: 192-168-5-4.421383e3ba1b4efdbb21e6a904625b45.plex.direct start, auto delete: true
! 19:18:30 T:1582130256 NOTICE: Thread ServerReachability: Benflix start, auto delete: true
! 19:18:30 T:1819276368 NOTICE: Thread ConnectionTest: 192-168-5-4.421383e3ba1b4efdbb21e6a904625b45.plex.direct start, auto delete: true
! ------STUFF HAPPENS------

2

Please enable debug logging and attach the log the this forum topic, the current log only show a Timeout was reached and suggest some sort of network problem.

3

Thanks for looking into this, Kwiboo. I’ve just done several new devices successfully without issue. I believe it was a connection issue between the Plex Media Server and the Plex.tv servers. I had a duel WAN I was using and believe Plex.tv would try to communicate back on the wrong external facing IP address.

Or it was on the Plex.tv servers themselves. Either way, I haven’t been able to replicate the issue a month later with a single WAN.