anonfunc/JellyPy
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated Frequently Asked Questions (FAQ) (markdown)

JonnyWong16
2017-01-15 17:28:10 -08:00
parent 54c0763b4b
commit 61b68dff01
1 changed files with 29 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
Frequently-Asked-Questions-(FAQ).md

@@ -19,6 +19,7 @@
* [PlexPy says "There was an error communicating with your Plex Server", and the logs say "Status code 401".](#general-q16)
* [I can't connect to my Plex server with "Use SSL" checked.](#general-q17)
* [My PlexPy database got corrupted: "DatabaseError: database disk image is malformed."](#general-q18)
* [PlexPy cannot read my Plex log file.](#general-q19)
## Activity and History Logging
@@ -30,6 +31,9 @@
* [Watch history isn't showing up under "Last Watched" on the homepage.](#history-q6)
* [After resuming a media item, it shows up as two plays in PlexPy.](#history-q7)
* [The logs keep telling me "Failed to write sessionKey XX ratingKey YY to the database. Will try again on the next pass."](#history-q8)
* [Can I see which items in my libraries are the *least watched*?](#history-q9)
* [My concurrent streams statistic is showing an insane number!](#history-q10)
* [I am seeing history entries with very long duration times.](#history-q11)
## Notifications
@@ -173,7 +177,7 @@ If you cannot load the Plex Web interface, then you may have a DNS rebinding iss
Otherwise, you may have to set secure connections to "Preferred" in your Plex server settings and uncheck the "Use SSL" box in the PlexPy settings. PlexPy will then connect to your Plex server directly without SSL using the address `http://LOCAL-IP-ADDRESS:32400`.
#### <a name="general-q18">Q:</a> My PlexPy database got corrupted: "DatabaseError: database disk image is malformed."
**A:** The easiest way to fix this would be restoring a older version of the database from the backup directory. Alternatively, you can try to fix is using the steps below, or using the [SQLite command line instructions here](http://froebe.net/blog/2015/05/27/error-sqlite-database-is-malformed-solved/).
**A:** The easiest way to fix this would be restoring an older version of the database from the backup directory. Alternatively, you can try to fix is using the steps below, or using the [SQLite command line instructions here](http://froebe.net/blog/2015/05/27/error-sqlite-database-is-malformed-solved/).
1. Backup your PlexPy database (`plexpy.db`) by making a copy and saving it somewhere safe.
2. Open your database with [DB Brwoser for SQLite](http://sqlitebrowser.org/).
@@ -188,6 +192,9 @@ Otherwise, you may have to set secure connections to "Preferred" in your Plex se
11. Go to "File > Write Changes" and "File > Close Database".
12. Replace your PlexPy database (`plexpy.db`) file with this new one.
#### <a name="general-q19">Q:</a> PlexPy cannot read my Plex log file.
**A:** PlexPy does not require your Plex logs to function. You can add your Plex logs folder to PlexPy in order to use it as a convenient log viewer. If you are installing PlexPy in a docker container or jail, then you will need to mount/share the Plex log folder into the PlexPy container. You must also specify the full path to the Plex logs folder (shortcuts will not work).
---
### Activity and History Logging
@@ -228,6 +235,27 @@ http://localhost:8181/info?rating_key=YY
If the item can't be found then you can flush the temporary sessions database in the Settings > Extra Settings.
#### <a name="history-q9">Q:</a> Can I see which items in my libraries are the *least watched*?
**A:** You can find out which items have not been watched by viewing the Media Info table for the library.
#### <a name="history-q10">Q:</a> My concurrent streams statistic is showing an insane number!
**A:** You can try fixing your database by following the steps below:
1. Create a backup of your PlexPy database (`plexpy.db`) by going to Settings > General > Backup Database
2. Shutdown PlexPy.
3. Open your database with [DB Brwoser for SQLite](http://sqlitebrowser.org/).
4. Go to the "Execute SQL" tab and run the following SQL:
DELETE FROM session_history WHERE id NOT IN (SELECT id FROM session_history_metadata);
DELETE FROM session_history_media_info WHERE id NOT IN (SELECT id FROM session_history_metadata);
5. Go to "File > Write Changes" and "File > Close Database".
6. Restart PlexPy.
#### <a name="history-q11">Q:</a> I am seeing history entries with very long duration times.
**A:** There's a websocket bug in the recent PMS versions where streams don't send a "stop" event. Once you restart PlexPy, a stop event is triggered, and the duration is calculated from when the stream started to when PlexPy was restarted.
The only solution at the moment is to disable Settings > Activity Monitoring > Use Websockets and manually delete those history entries from the History tab.
---