To get around this problem, each of your friends would have to set up their own local PlexConnect and have it hook up to the dedicated server I guess.
It will not pass through PlexConnect, however you would not want to use the PlexConnect DNS component with it facing the internet. Either use a locked down version or run individual PlexConnect instances locally.
The guy with the original problem is back :rolleyes:
I just downloaded the log from the NAS, but its 170MB. Its a huge log and the problem is I cannot create a smaller one with the interaction of two different ATVs only, because I am not at the house where the system is installed right now. Any suggestions what I should check in the log? The ATVs are running in the local LAN, so they all have different IP addresses. The problem must be different.
Btw after some unsuccessful tries to get the accounts running I also edited the DEFAULT section of the ATVSettings.cfg. Somebody mentioned it to be a problem?
>>Btw after some unsuccessful tries to get the accounts running I also edited the DEFAULT section of the ATVSettings.cfg. Somebody mentioned it to be a problem?
Depending on what you changed...
This is the current ATVSettings.cfg:
[DEFAULT]
showsynopsis = Hide
movies_navbar_decades = checked
showplayerclock = True
tv_navbar_unwatched = checked
movies_navbar_directors = checked
subtitlesize = 100
transcoderaction = Auto
tv_navbar_genres = checked
durationformat = Hours/Minutes
clockposition = Center
movies_navbar_more = checked
showview = List
movieview = Grid
movies_navbar_unwatched = checked
overscanadjust = 0
movies_navbar_actors = checked
showendtime = True
tv_navbar_more = checked
audioboost = 100
transcodequality = 1080p 40.0Mbps
seasonview = List
myplex_auth =
showunwatched = True
movies_navbar_collections = checked
myplex_user =
channelview = List
remotebitrate = 720p 3.0Mbps
timeformat = 24 Hour
actorview = Movies
movies_navbar_genres = checked
[C0HM122EFF54]
myplex_user = MarioSchwarzwald
myplex_auth = xx
[C0HM109MFF54]
myplex_user = GaesteSchwarzwald
myplex_auth = xx
transcoderaction = DirectPlay
[C0HM18NCFF54]
myplex_user = GaesteSchwarzwald
myplex_auth = xx
transcoderaction = DirectPlay
Can you detect any issues?
I posted a thread with the similar problem as mentioned by miniop a while ago (here)
As far as I can see, it’s not possible to have more than one ATV in the same LAN connected to a WAN-based PlexConnect Server. I run five ATV3’s (three at different location - they have no Problems because they all have different wan IP’s) the other two in my second home (they use the same WAN IP).
For me the workaround to this problem is buying a little Raspberry Pi put Mini Linux on it and run the PlexConnect Server on it locally at the location where you have more than one ATV. Should work flawlessly…
Sorry, I don’t want to hijack this thread but since here is a big discussion about multiple ATV's in a home I thought it is the right place to talk about this problem I experienced yesterday. So my PlexConnect is running on an AWS Server and 3 ATV3’s are using this. It was running since 3 - 4 weeks flawlessly. But Somehow it crashed (unfortunately I don’t run any logs at all). So I logged into the server and stopped the PlexConnect.py by pressing CTRL+C, but it could not really be stopped so I rebooted the complete server. After that two of the logins (all three ATV3’s have different myPlex Logins) where gone. Only the first ATV3 connected to the PlexConnect Server has been written down in the ATVSettings.cfg. So I thought this might be a onetime issue. So I entered the myPlex logins again on the two missing ATV3’s and stopped the server to see if it has been written down and again... only the first myPlex login has been written down into the ATVSettings.cfg. I guess I can do it manually? But how do I generate this token?
I am still trying to get multiple ATVs running in the same lan with one PlexConnect. If one ATV generates the token for an account, I can just copy this token to use it to authenticate another ATV, or it the token in some way ATV depended?
I have two aTVs running and they show different MyPlex tokens (with the same MyPlex user). So I guess you should let the login process/MyPlex server decide. :-)
Edit: looking in PlexAPI.py/MyPlexSignin() and further in getXArgsDeviceInfo() you will see a number of data points used during the token generation - device, model, udid, ...
Thanks Baa for the fast response!
That could be the problem. But I also tried to login to myplex individually and sometimes the ATV forgot the login right away... What is the best way get a clean ATVSettings.cfg?
Login with the first ATV, stop the PlexConnect service and start it again and so on... or try to login to every single ATV and then stop the service to create a ATVSettings.cfg?
It should not matter - once PlexConnect stops it *should* store the current ATVSettings. I am not totally sure what happens when rebooting (a Win machine), still missing a confirmation for the recent "shut down fix on Win".
Since I am running PlexConnect on a Synology NAS it should be working fine if I am just logging into all the accounts on the ATVs. I have to call the guy currently at home with all the ATVs, he will be happy to hear that he has to login on every device again :rolleyes:
Hello everybody,
I am back again...! I just freshly installed PlexConnect on the DSM 5.0 according to the steps listed here in the forum and just tried to log in to the myPlex accounts.
And now I am stuck with the SAME issue. This time I didm´t edit the ATVSettings.cfg in any way, but still when I log in to a different account on the second ATV it logs me out on the first one and everything gets messed up. I have no idea why, since I am using PlexConnect also at home on a freenas server without any issue!
Hopefully somebody has an idea! Thanks
Do you have all aTVs on the same (local) subnet?
Yeah they are all connected to the same network with the address 192.168.179.X.
The Plex and Plexconnect are running on a Synology DS 1512+ and the ATVs are connected through a switch to the server.
As far as I understand the issue must be related to the network infrastructure, because other users don´t have these issue? I am using a HP 1810 switch but without any special settings. The only thing is the link aggregation through witch the DiskStation is connected.
It is the same issue, even when I am already in the trailers app on ATV 1 and login to ATV2 with another plex account, I just have to change the view to settings on ATV1 to be in the account of ATV2
EDIT: It seems to be an issue with PlexConnect on the synology! I just installed it for a test on a windows machine in the network and there is no mixed up log ins from myplex.
Interesting... we know about a similar issue when connecting the aTVs through WAN and your public IP address. I wonder, if this is related to any port forwarding or such.
Could you create a short log were both aTVs access PlexConnect, each with maybe 2 or 3 requests? I would like to have a look at the IPs involved, UDIDs and stuff.
I created a log file with the two ATVs which should use two different myplex accounts, but they actually don't!
The think which looks weird in the log is that the aTVAddress says the ip address of the plexconnect installation and Synology NAS?
https://www.dropbox.com/s/4estd8nwms1ekfg/PlexConnect.log
Hopefully you will find something helpful! Thanks for the support
>>The think which looks weird in the log is that the aTVAddress says the ip address of the plexconnect installation and Synology NAS?
Yep... that is exactly the issue we have seen for aTV requests coming from WAN using the public PMS IP. The good thing on your environment is, you got an "X-Forwarded-For" tag in the http header, which should show the original source (in your case .47/.49). That way we can add some code to deduct the original source address...
Maybe I haven't looked there before - but using the public IP I haven't seen such an add-on.
Yeah it looks like somebody is doing something like a NAT similar to a wan environment. But this only happens if the plexconnect is running on the NAS. I disabled on both plexconnect installations the dns server and I am using the Synology DNS to be more flexible to switch between plexconnect installations. Oh actually I am not sure, maybe I also used the Synology DNS Server during the recording of the log file, maybe therefore it says the ip of the NAS. But in the same setup the windows installation works fine!
Synology uses port 80 for web access, right? My understanding is, that the installed Apache (or whatever) is set up to forward the requests to PlexConnect.
On Windows you don't have that forwarding... the requests go straight into PlexConnect, and it can figure out the actual sender.
When you say the NAS has link aggregation are you speaking about it teaming 2 or more NIC connections?
If so that is probably going to confuse things if you do not hard code in the correct IP and disable auto detection as the "real" IP of the NAS will probably be a virtual interface.
