@moussa.uk said:
lonelyfairie I should correct myself. You should just need your server signed into plex.tv so that the Xbox One can look up the IP address of the server. It does not need remote access enabled.
3rd party apps cannot use network discovery, but Microsoft’s own built in apps can.
Understood, then as I stated above I think it would be wiser to just implement a login sequence whenever the server starts up, or at least add an option to just do this instead of full remote access?
If you are not willing to implement this globally, is there a way I can modify the server startup to include this?
Thanks for your help and for explaining the real cause of the issue.
@moussa.uk yes it is, and the values seem correct:
( sorry for the late reply, I had given up on this )
Anything else I should look for? I’ve managed to set up a working server on a laptop, the server hardware in question that isn’t working is running an older version of OS X ( 10.6 ) - would that matter? When I quit and then re-start the server on the machine with problems, I see this:
15-08-22 4:22:51 PM [0x0-0x2c02c].com.plexapp.plexmediaserver[3174] 2015-08-22 16:22 Plex Media Server[3174] (CarbonCore.framework) FSEventStreamCreate: _FSEventStreamCreate: ERROR: could not allocate 0 bytes for array of path strings
15-08-22 4:22:51 PM [0x0-0x2c02c].com.plexapp.plexmediaserver[3174] 2015-08-22 16:22 Plex Media Server[3174] (CarbonCore.framework) FSEventStreamScheduleWithRunLoop(): failed assertion 'streamRef != NULL'
15-08-22 4:22:51 PM [0x0-0x2c02c].com.plexapp.plexmediaserver[3174] 2015-08-22 16:22 Plex Media Server[3174] (CarbonCore.framework) FSEventStreamStart(): failed assertion 'streamRef != NULL'
There seems to be an issue with Windows 10 and Plex. I keep getting knocked offline (and maybe xbox one is contributing to the issue). It seems to be worse when network is set to “preffered”. I’ve got it set to “disabled” right now, so we’ll see how that goes, but obviously “disabled” isn’t an ideal solution.
@moussa.uk so the key question I thinks is this. In the following screenshot form my api results, why does ‘convolver’ work fine with the xbox but ‘ekoplex’ does not?
At this point my suspicion is mainly the OS / hardware on ekoplex - it’s an older ‘hackintosh’ desktop running snow leopard. The server works fine with iOS / Android clients, just not xbox. ‘convolver’ is a brand-new MBPro running 10.10, and that seems to work fine. I assume if I get a NAS / freenas setup as the server this won’t be an issue.
Once setup and signed in to plex.tv, you should be able to shutdown and restart PMS and stay signed in (I think, anyway). If you have time/energy to do so, could you please make sure your PMS is signed in and then restart it, and then send us the logs for when this happens?
Dom C
I saved the logs from when my server goes offline and it appears to be going offline when there’s a refresh of the media library. I also have a dump file from when the server went offline if you’d like to see that too.
Anyway, there’s a warning that might be related to the issue (WARN - [FFMPEG] - stream 0, timescale not set). As well as references to an error issuing curl_easy_perform and "unable to allocate a changestamp from the server. What exactly does this all mean?
Aug 24, 2015 17:11:15:002 [8108] DEBUG - Downloading document http://127.0.0.1:32400/library/changestamp
Aug 24, 2015 17:11:15:003 [8108] DEBUG - HTTP requesting GET http://127.0.0.1:32400/library/changestamp
Aug 24, 2015 17:11:20:006 [8108] ERROR - Error issuing curl_easy_perform(handle): 28
Aug 24, 2015 17:11:20:006 [8108] WARN - HTTP error requesting GET http://127.0.0.1:32400/library/changestamp (28, Timeout was reached) (Operation timed out after 5016 milliseconds with 0 out of -1 bytes received)
Aug 24, 2015 17:11:20:006 [8108] DEBUG - Simulating 408 after curl timeout
Aug 24, 2015 17:11:20:006 [8108] ERROR - HTTP 408 downloading url http://127.0.0.1:32400/library/changestamp
Aug 24, 2015 17:11:20:006 [8108] ERROR - Exception inside transaction (inside=1) (Library\MediaItem.cpp:1261): Unable to allocate a changestamp from the server
Aug 24, 2015 17:11:20:006 [8108] ERROR - Exception in worker thread: Unable to allocate a changestamp from the server
