Open spuniun opened 8 years ago
Are you on the master or dev branch? I've had a PIN set since Plex Home first came out with no issues.
I'm on master - I will switch to dev and give a try
I haven't been using this project as much myself lately, there are a few other issues that need investigation as well so please let me know how that goes.
With dev branch I cannot load history page, getting an error on parsing the FriendlyName JSON param from plexWatch:
Uncaught SyntaxError: Unexpected string FriendlyName @ history.php:182 $.dataTable.aoColumnDefs.fnCreatedCell @ history.php:250 _fnCreateTr @ jquery.dataTables.js:1149 _fnDraw @ jquery.dataTables.js:1451 _fnAjaxUpdateDraw @ jquery.dataTables.js:2059 (anonymous function) @ jquery.dataTables.js:1899 (anonymous function) @ history.php:198 fire @ jquery-2.0.3.js:2913 self.fireWith @ jquery-2.0.3.js:3025 done @ jquery-2.0.3.js:7400 (anonymous function) @ jquery-2.0.3.js:7822
It's the same value that was working with master branch. I looked at the actual string and cannot find any issues that would fail a JSON parsing.
I see https://github.com/ecleese/plexWatchWeb/issues/135 addressed this issue but I'm latest dev branch and still experiencing it.
With plexWatch and plexWatchWeb running on localhost with PMS, when Plex Home user has PIN set the plexWatchWeb UI fails to connect to PMS with the error "Failed to access Plex Media Server. Please check your settings."
Disabling the PIN restores normal functionality to plexWatchWeb. plexWatch continues to scrape PMS logs successfully and is not affected by the Plex Home PIN being enabled.
The myPlex user/password is set correctly in both plexWatch and plexWatchWeb