For the record you can have multiple libraries in one condition, you shouldn’t need a unique condition per library.
thanks will look into that
so below setup is enough to send notifications of recently added items?
conditions {1}
Library Name IS [exact library name OR exact library name or etc.]
========
i can now confirm that above works like a charm 
thanks
PS also IMDB urls preview and work on facebook as they should!
@tarnecki
glad it working for you
I have setup Tautulli on my computer and have it set so I can access it remotely however when I have put all that info into the app on my phone it keeps telling me it couldn’t authenticate with either Tautulli or Plex. I am using a noip address to get access to Tautulli and can remote access from a browser off network.
Phone:
Samsung Galaxy S7 Edge
OS Android 7.0
Computer:
Windows 10
Taultulli is current
Successfully installed Tautulli on a QNAP TVS-471. Can’t run Tautulli setup wizard. It won’t authenticate with plex.tv. It says fetching token then authentication failed. Tried plex username/pw and plex email/pw. Neither work. Both work for logging into plex.
Any ideas how to troubleshoot?
My PlexPy updated the other night to the main release of Tautulli and I absolutely love it. Thank you Johnny for your hard work. I’ll get over to the web page and send a donation for your efforts. The notifications features are great, I’m using pushbullet for myself and have posts going to a private Facebook group for my friends/family so they can see what’s new on the server and if it’s up or down. The added feature of being able to see all the stream information has already helped me troubleshoot on family members buffering issue! That was an awesome addition!!!
First of all, thank you for this amazing project, and A LOT of great improvements on the new version, that whole v2 changelog was damn impressive!
If I may ask - why didn’t you move most of the old issues to the new issues repo? Before opening an issue, I’m usually searching for existing ones on the subject - and often find it was discussed, and those discussions usually have very useful info to troubleshoot or to understand one’s position why something won’t be fixed. Your project is pretty damn huge and has all those awesome features, that I feel sad that all those hundreds of discussions are gone now, at least from the public view. I can understand it from the point of a post-release spring cleaning, but still feels like a pretty big loss, especially for the closed issues, that didn’t need to be removed even for the cleaning sake.
I’m sorry to bother you with all that, it’s just that I’m used to research everything very thoroughly, and am very sensitive about information loss, and my OCD doesn’t help either. Also, as far as I understand, the most recent issues that were opened there right around release day, are gone too(including mine), and users will have to remember what exactly they wrote, and recreate it all again word-for-word (or just give up).
@enchained said:
First of all, thank you for this amazing project, and A LOT of great improvements on the new version, that whole v2 changelog was damn impressive!If I may ask - why didn’t you move most of the old issues to the new issues repo? Before opening an issue, I’m usually searching for existing ones on the subject - and often find it was discussed, and those discussions usually have very useful info to troubleshoot or to understand one’s position why something won’t be fixed. Your project is pretty damn huge and has all those awesome features, that I feel sad that all those hundreds of discussions are gone now, at least from the public view. I can understand it from the point of a post-release spring cleaning, but still feels like a pretty big loss, especially for the closed issues, that didn’t need to be removed even for the cleaning sake.
I’m sorry to bother you with all that, it’s just that I’m used to research everything very thoroughly, and am very sensitive about information loss, and my OCD doesn’t help either. Also, as far as I understand, the most recent issues that were opened there right around release day, are gone too(including mine), and users will have to remember what exactly they wrote, and recreate it all again word-for-word (or just give up).
I started migrating some issues but it was causing too many problems so I just decided to start fresh. If you have a specific issue in question then I can clone individual ones manually.
issue
missing one library (section id 8, Music) of three , if accessible through Home/Recently Added all the same, with Tautulli running on macOS 10.13.3
action
http://localhost:8181/undelete_library?section_id=8, as per the GitHub faq, through Safari 11.0.3 (having searched this discussion in vain)
outcome
web page says {“message”: “Re-added library with id 8.”}, though no such library card
on Settings/Homepage if still accessible through Home/Recently Added
action next
restart Tautulli, reload Home (in Safari)
outcome next
still no such library card (while remaining accessible through Home/Recently Added)
! 2018-03-13 17:13:10 - INFO :: MainThread : Received signal: restart
! 2018-03-13 17:13:10 - ERROR :: CP Server Thread-7 : WebUI :: /restart : Script error.. (:0)
! 2018-03-13 17:13:15 - INFO :: Thread-2 : Tautulli NotificationHandler :: Notification thread exiting…
! 2018-03-13 17:13:15 - INFO :: Thread-1 : Tautulli NotificationHandler :: Notification thread exiting…
! 2018-03-13 17:13:15 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:13:15 - INFO :: MainThread : Tautulli is restarting…
! 2018-03-13 17:13:15 - INFO :: MainThread : Restarting Tautulli with [‘/usr/bin/python’, ‘/Applications/PlexPy/Tautulli.py’, ‘–nolaunch’]
! 2018-03-13 17:13:28 - INFO :: MainThread : Checking if the database upgrades are required…
! 2018-03-13 17:13:29 - INFO :: MainThread : Checking if configuration upgrades are required…
! 2018-03-13 17:13:29 - INFO :: MainThread : Retrieving latest version information from GitHub
! 2018-03-13 17:13:29 - DEBUG :: MainThread : Requesting URL via GET method: https://api.github.com/repos/Tautulli/Tautulli/commits/master
! 2018-03-13 17:13:30 - DEBUG :: MainThread : Latest version is a08bce2073b1847762a22a843b13acc5f996d9cb
! 2018-03-13 17:13:30 - INFO :: MainThread : Tautulli is up to date
! 2018-03-13 17:13:30 - INFO :: MainThread : Tautulli PlexTV :: Requesting resources for server…
! 2018-03-13 17:13:30 - INFO :: MainThread : Tautulli PlexTV :: Using user-defined URL.
! 2018-03-13 17:13:30 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:13:30 - INFO :: MainThread : Tautulli Users :: Requesting users list refresh…
! 2018-03-13 17:13:31 - INFO :: MainThread : Tautulli Users :: Users list refreshed.
! 2018-03-13 17:13:31 - INFO :: MainThread : Tautulli Libraries :: Requesting libraries list refresh…
! 2018-03-13 17:13:48 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:13:48 - INFO :: MainThread : Tautulli Libraries :: Libraries list refreshed.
! 2018-03-13 17:13:48 - INFO :: MainThread : Tautulli NotificationHandler :: Starting background notification handler (2 threads).
! 2018-03-13 17:13:48 - DEBUG :: MainThread : Tautulli Monitor :: Checking for active streams.
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Tautulli WebSocket :: Opening websocket.
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Tautulli WebSocket :: Connection attempt 1.
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Tautulli WebSocket :: Ready
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Check GitHub for updates
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Backup Tautulli database
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Backup Tautulli config
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Refresh Plex server URLs
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Check for Plex remote access
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Refresh users list
! 2018-03-13 17:13:48 - INFO :: Thread-3 : Scheduled background task: Refresh libraries list
! 2018-03-13 17:13:48 - INFO :: MainThread : Tautulli WebStart :: Web server authentication is enabled: Tautulli admin (username is ‘marC31’).
! 2018-03-13 17:13:48 - INFO :: MainThread : Tautulli WebStart :: Starting Tautulli web server on http://0.0.0.0:8181/
! 2018-03-13 17:29:49 - INFO :: CP Server Thread-11 : Tautulli Libraries :: Re-adding library with id 8 to database.
! 2018-03-13 17:30:11 - ERROR :: CP Server Thread-8 : WebUI :: /home : Script error.. (:0)
! 2018-03-13 17:30:21 - ERROR :: CP Server Thread-10 : WebUI :: /home : Script error.. (:0)
! 2018-03-13 17:30:42 - ERROR :: CP Server Thread-5 : WebUI :: /settings : Script error.. (:0)
! 2018-03-13 17:31:44 - ERROR :: CP Server Thread-6 : WebUI :: /settings?support=true : Script error.. (:0)
! 2018-03-13 17:33:08 - ERROR :: CP Server Thread-8 : WebUI :: /restart : Script error.. (:0)
! 2018-03-13 17:33:08 - INFO :: MainThread : Received signal: restart
! 2018-03-13 17:33:13 - INFO :: Thread-1 : Tautulli NotificationHandler :: Notification thread exiting…
! 2018-03-13 17:33:13 - INFO :: Thread-2 : Tautulli NotificationHandler :: Notification thread exiting…
! 2018-03-13 17:33:13 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:33:13 - INFO :: MainThread : Tautulli is restarting…
! 2018-03-13 17:33:13 - INFO :: MainThread : Restarting Tautulli with [‘/usr/bin/python’, ‘/Applications/PlexPy/Tautulli.py’, ‘–nolaunch’]
! 2018-03-13 17:33:17 - INFO :: MainThread : Checking if the database upgrades are required…
! 2018-03-13 17:33:17 - INFO :: MainThread : Checking if configuration upgrades are required…
! 2018-03-13 17:33:17 - INFO :: MainThread : Retrieving latest version information from GitHub
! 2018-03-13 17:33:17 - DEBUG :: MainThread : Requesting URL via GET method: https://api.github.com/repos/Tautulli/Tautulli/commits/master
! 2018-03-13 17:33:17 - DEBUG :: MainThread : Latest version is a08bce2073b1847762a22a843b13acc5f996d9cb
! 2018-03-13 17:33:17 - INFO :: MainThread : Tautulli is up to date
! 2018-03-13 17:33:17 - INFO :: MainThread : Tautulli PlexTV :: Requesting resources for server…
! 2018-03-13 17:33:18 - INFO :: MainThread : Tautulli PlexTV :: Using user-defined URL.
! 2018-03-13 17:33:18 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:33:18 - INFO :: MainThread : Tautulli Users :: Requesting users list refresh…
! 2018-03-13 17:33:18 - INFO :: MainThread : Tautulli Users :: Users list refreshed.
! 2018-03-13 17:33:18 - INFO :: MainThread : Tautulli Libraries :: Requesting libraries list refresh…
! 2018-03-13 17:33:28 - INFO :: MainThread : Tautulli Config :: Writing configuration to file
! 2018-03-13 17:33:28 - INFO :: MainThread : Tautulli Libraries :: Libraries list refreshed.
! 2018-03-13 17:33:28 - INFO :: MainThread : Tautulli NotificationHandler :: Starting background notification handler (2 threads).
! 2018-03-13 17:33:28 - DEBUG :: MainThread : Tautulli Monitor :: Checking for active streams.
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Tautulli WebSocket :: Opening websocket.
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Tautulli WebSocket :: Connection attempt 1.
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Tautulli WebSocket :: Ready
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Check GitHub for updates
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Backup Tautulli database
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Backup Tautulli config
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Refresh Plex server URLs
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Check for Plex remote access
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Refresh users list
! 2018-03-13 17:33:28 - INFO :: Thread-3 : Scheduled background task: Refresh libraries list
! 2018-03-13 17:33:28 - INFO :: MainThread : Tautulli WebStart :: Web server authentication is enabled: Tautulli admin (username is ‘marC31’).
! 2018-03-13 17:33:28 - INFO :: MainThread : Tautulli WebStart :: Starting Tautulli web server on http://0.0.0.0:8181/
! 2018-03-13 17:33:30 - ERROR :: CP Server Thread-10 : WebUI :: /home : Script error.. (:0)
!
At an utter loss so please assist.
cheers,
PS issue occurred only after the PlexPy in-line update
issue
not receiving OSX Notify notifications
with Tautulli running on macOS 10.13.3 (System Preferences/Notifications/Python enabled), for all reassurances logged below
! 2018-03-13 19:14:40 - INFO :: CP Server Thread-8 : Tautulli Notifiers :: Updated notification agent: OSX Notify (notifier_id 1).
! 2018-03-13 19:14:40 - DEBUG :: CP Server Thread-8 : Sending test osx notification.
! 2018-03-13 19:14:40 - INFO :: CP Server Thread-8 : Tautulli NotificationHandler :: Preparing notifications for notifier_id 1.
! 2018-03-13 19:14:40 - INFO :: CP Server Thread-8 : Tautulli Notifiers :: OSX Notify notification sent.
action
consulted the GitHub faq, searched this discussion
outcome
being stumped for a remedy all the same
Please assist.
cheers,
PS issue occurred only after the PlexPy in-line update
@TheMeanCanEHdian said:
For the record you can have multiple libraries in one condition, you shouldn’t need a unique condition per library.
Additionally, for anyone learning/reviewing, the conditions didn’t, in this case, need to be anded together either. As stated at the bottom of the page, conditions are implicit as ‘and’ if left blank.
@plex-linux - I don’t say this to indicate your method was wrong, as it’s perfectly capable/working - I only state for education of those not use to the new conditional statements
@marC31 said:
Though detailed, as I’m sure Jonnywong will appreciate, forums are not the intended bug report area,
Please use Issue tracker - GitHub - Tautulli/Tautulli-Issues: Bug reports for Tautulli
@Yamipirogoeth said:
the app on my phone it keeps telling me it couldn’t authenticate with either Tautulli or Plex.
I’m not sure the tautulli release thread is proper support place for Tatuilli Remote.
@JonnyWong16 - can you confirm? Does William have a support arena, or are you swallowing it here?
Either way @Yamipirogoeth , have you registered the device in Tautulli settings? If not, go to Tautulli, Settings, Tautulli remote, click the + plus on register device, scan QR code with Tautulli remote and input settings as it shows into mobile app.
@JonnyWong16 - The support links on Tautulli.com for git/wiki and for forum support thread need to be changed now that everything points to Tautulli branding/names.
@JamminR said:
@marC31 said:
Though detailed, as I’m sure Jonnywong will appreciate, forums are not the intended bug report area,
Please use Issue tracker - GitHub - Tautulli/Tautulli-Issues: Bug reports for Tautulli
I’d rather you don’t post on GitHub unless it is an actual bug report. Asking for help to configure something is not a bug report. Not to sound offensive, but most of the time it is user error. Ask for support, then we will confirm if it’s actually a bug that should be submitted on GitHub.
@Yamipirogoeth said:
the app on my phone it keeps telling me it couldn’t authenticate with either Tautulli or Plex.
I’m not sure the tautulli release thread is proper support place for Tatuilli Remote, @JonnyWong16 - can you confirm?
It’s fine. We both share the same support locations (Discord, Forums, Reddit) so it’s easier to keep track of.
Either way, have you registered the device in Tautulli settings? If not, go to Tautulli, Settings, Tautulli remote, click the + plus on register device, scan QR code with Tautulli remote and input settings as it shows.
@JonnyWong16 - The support links on Tautulli.com for git/wiki and for forum support thread need to be changed now that everything points to Tautulli branding/names.
Thanks for letting us know.
@JonnyWong16 said:
I’d rather you don’t post on GitHub unless it is an actual bug report. Asking for help to configure something is not a bugThanks for letting us know.
Roger that, and welcome
@JonnyWong16 said:
I started migrating some issues but it was causing too many problems so I just decided to start fresh. If you have a specific issue in question then I can clone individual ones manually.
Thanks for the offer! Does that mean you still have the data left? I’ve heard it’s impossible to make issues readonly on github, but there are ways to store something like an “old issues readonly archive” if you’d like to still keep it online for future references: GitHub - matomo-org/github-issues-mirror: Provides a read-only mirror for your GitHub issues Though not sure if it’s simple to setup or if it could cause some problems too.
I don’t really remember specific issues, but I think I subscribed to some. Oh, one of them was particularly helpful - where you explained in details how to merge records in case you move your libraries and want consistent history. I often move movies between libraries and even wanted to do a feature request on Feathub - never would have guessed that “Fix metadata” does exactly what I need for consistent stats (maybe it’s due to rename and/or a tooltip? I thought of it like Plex’s Fix Match or something, thinking of metadata as of something that user sees, and not merging internal ids).
As for mine - I can recreate them manually, since they were simple and only a couple of them. Quick question: does the search filter on the history page use the Plex search directly? If so - one of my issues is irrelevant since I just found out that case-sensitive search bug for Russian language is a very old Plex bug and I don’t think you can do anything about it on your side then…
@enchained said:
@JonnyWong16 said:
I started migrating some issues but it was causing too many problems so I just decided to start fresh. If you have a specific issue in question then I can clone individual ones manually.
Thanks for the offer! Does that mean you still have the data left? I’ve heard it’s impossible to make issues readonly on github, but there are ways to store something like an “old issues readonly archive” if you’d like to still keep it online for future references: GitHub - matomo-org/github-issues-mirror: Provides a read-only mirror for your GitHub issues Though not sure if it’s simple to setup or if it could cause some problems too.
I don’t really remember specific issues, but I think I subscribed to some. Oh, one of them was particularly helpful - where you explained in details how to merge records in case you move your libraries and want consistent history. I often move movies between libraries and even wanted to do a feature request on Feathub - never would have guessed that “Fix metadata” does exactly what I need for consistent stats (maybe it’s due to rename and/or a tooltip? I thought of it like Plex’s Fix Match or something, thinking of metadata as of something that user sees, and not merging internal ids).
As for mine - I can recreate them manually, since they were simple and only a couple of them. Quick question: does the search filter on the history page use the Plex search directly? If so - one of my issues is irrelevant since I just found out that case-sensitive search bug for Russian language is a very old Plex bug and I don’t think you can do anything about it on your side then…
Yes, I still have access to all the old issues. They’re all hidden because I don’t want people posting on the Tautulli/Tautulli repository. You cannot make GitHub issues readonly. You can see that I already tried moving over some of the issues here. It was just causing too many problems.
Migrating media could probably be added as an FAQ answer instead of searching through old GitHub Issues.
Only the search bar at the very top of the page use Plex search. Any of the search bars for the tables specifically search in our own database. I will have to add some Russian characters to my database to see what the issue is.
@JonnyWong16 said:
Yes, I still have access to all the old issues. They’re all hidden because I don’t want people posting on the Tautulli/Tautulli repository. You cannot make GitHub issues readonly.
I understand, it’s only logical to disable issues on the old repo. But there is actually still a way to make them “read-only”, just not on the github anymore. The repo I linked to about mirroring issues says that it does just that. Not sure how exactly, since I have no experience with PHP, but it probably parses all the data to json and provides it via some custom web ui.
I found a link to example of such read-only issues archive: https://issues.matomo.org (my browser was blocking css styles, until I opened in incognito).
Sadly, I don’t see the most important feature - the search. It’s fixable by google’s custom search or things like Defiant.js, but that’s already requires more effort than I was trying to suggest. Still I thought it was worth mentioning.
Migrating media could probably be added as an FAQ answer instead of searching through old GitHub Issues.
Good idea, this will be really useful.
Only the search bar at the very top of the page use Plex search. Any of the search bars for the tables specifically search in our own database. I will have to add some Russian characters to my database to see what the issue is.
Thanks for looking into it! Should I still create a ticket on the subject?
@JamminR
yea i know you don’t need to and them together now but this was carry over from before, when you did need to. I have been running beta, v2 tautulli for a long time, basically as soon as i found out about it
that change was made clear back on Jan7
than you for this great app…so far i installed this and tried to configure the notification settings in notification agents. I would prefer to use my hotmail, but I couldn’t get it to work as they use STRATTLS and couldn’t find guidance. So I went to GMAIL because I saw a post in the Tautulli wiki that had all the server info…below is what I have and cannot get it to work. I keep getting an error “Tautulli Notifiers :: Email notification failed: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions”
here are my settings
from: myemail@gmail.com
TO: tofriends@gmail.com
SMTP Server: smtp.gmail.com
Port: 587
SMTP user: myemail@gmail.com
SMTP Password: mypassword
TLS: Checked
Triggers I have notify plex remote down: Checked
I can’t seem to get this email to work for hotmail/gmai.
