@“roku.caleb” said:
Since I updated to Tautulli the “Plex Update available” notification is no longer working from my Telegram notification Agent.All other triggers work fine except for this one. Is anyone else having this problem?
Have you enabled Settings > Plex Media Server > Monitor Plex Updates?
@SVKTV said:
@JamminR said:
@Davidson-NAS @SVKTV
It’s likely NOT called “stable”, and, you can’t edit the config while Tautulli is running. It’s stored in memory, gets overwritten when tautulli shuts down.That being said, I’d recommend using the settings in Tautulli
Settings - General - Show advanced, scroll to bottom - change from beta to master, check out.
- Suddenly on beta branch without changing from master
- Settings - General - Show advanced - Scroll to bottom
- Setting is not there. Tried both firefox and chrome.
Ditto here. Don’t recall ever making any change, i installed plexpy via the QNAP packaged appstore and here I am
@Davidson-NAS said:
@SVKTV said:
@JamminR said:
@Davidson-NAS @SVKTV
It’s likely NOT called “stable”, and, you can’t edit the config while Tautulli is running. It’s stored in memory, gets overwritten when tautulli shuts down.That being said, I’d recommend using the settings in Tautulli
Settings - General - Show advanced, scroll to bottom - change from beta to master, check out.
- Suddenly on beta branch without changing from master
- Settings - General - Show advanced - Scroll to bottom
- Setting is not there. Tried both firefox and chrome.
Ditto here. Don’t recall ever making any change, i installed plexpy via the QNAP packaged appstore and here I am
+1 here also, I installed via the QNAP package AppStore and I also don’t have the extra optional update settings. Just a guess, but I think the QNAP package might be the problem…
@Davidson-NAS said:
@DuffHQ said:
@JamminR said:
@Davidson-NAS @DuffHQ
It’s likely NOT called “stable”, and, you can’t edit the config while Tautulli is running. It’s stored in memory, gets overwritten when tautulli shuts down.That being said, I’d recommend using the settings in Tautulli
Settings - General - Show advanced, scroll to bottom - change from beta to master, check out.
- Suddenly on beta branch without changing from master
- Settings - General - Show advanced - Scroll to bottom
- Setting is not there. Tried both firefox and chrome.
Ditto here. Don’t recall ever making any change, i installed plexpy via the QNAP packaged appstore and here I am
I found the error. I accidentally added the beta tag to the master branch. It should correct itself on the next release.
I am not a coder, but I’ve always attempted to push my limited computer knowledge on my own. I’ve been trying to get a custom newsletter template built exactly to my liking and am running into an issue giving me quite a bit of grief. I’m trying to get it to list the first 3 actors but I keep getting indexing errors when a movie has been added with less than 3 actors (documentaries usually). When movies all have 3+ actors it looks perfect. Can anyone steer me in a good direction on how to solve this?
Thanks in advance for any advice!
@GoSpursGo said:
I am not a coder, but I’ve always attempted to push my limited computer knowledge on my own. I’ve been trying to get a custom newsletter template built exactly to my liking and am running into an issue giving me quite a bit of grief. I’m trying to get it to list the first 3 actors but I keep getting indexing errors when a movie has been added with less than 3 actors (documentaries usually). When movies all have 3+ actors it looks perfect. Can anyone steer me in a good direction on how to solve this?Thanks in advance for any advice!
Similar to the genre tags.
% for actor in movie['actors'][:3]:
${actor}
% endfor
@JonnyWong16 said:
Similar to the
genretags.Tautulli Newsletter - ${subject}
% for actor in movie['actors'][:3]: ${actor} % endfor
That did it! Thank you once again!
Again regarding newsletters:
Would it be possible to have the badges (including the new actor ones you just helped me with) link to their respective Plex pages (i.e. content rating ‘PG’ would take you to my Plex library showing all PG movies, year ‘2016’ would show all 2016 movies, actor ‘Brad Pitt’ would show all Brat Pitt movies, etc.)?
I attempted to do this with just the actors (as this would be the best use case IMO) but got caught up trying to determine what the actor codes are linked to (didn’t seem to be IMDB or TMDB) and how they’re populated.
Not a huge deal so if it’s anything too complicated please don’t sweat it, but it would be a nice touch. Thanks!
Jonny, don’t know how you keep up with this constant thread. LOL
Is there anyway to have an email agent email an account other than the one used to create a friends’ plex acct. Some account are a household with 2-5 people watching but one master account. Each To/CC/BCC field is a drop down only.
I just told some people, sure I can send it there… oops.
@royalef said:
Jonny, don’t know how you keep up with this constant thread. LOL
Is there anyway to have an email agent email an account other than the one used to create a friends’ plex acct. Some account are a household with 2-5 people watching but one master account. Each To/CC/BCC field is a drop down only.I just told some people, sure I can send it there… oops.
You can type in those dropdown boxes.
Sorry to waste the time. I tried that first but I must have not hit enter. It didn’t convert to the item with the X at the end.
Thanks.
@JonnyWong16 said:
@royalef said:
Jonny, don’t know how you keep up with this constant thread. LOL
Is there anyway to have an email agent email an account other than the one used to create a friends’ plex acct. Some account are a household with 2-5 people watching but one master account. Each To/CC/BCC field is a drop down only.I just told some people, sure I can send it there… oops.
You can type in those dropdown boxes.
Nevermind.
-Shark2k
I’m getting the following Header message when the footer hasn’t been changed at all: “The Tautulli newsletter footer was removed from the newsletter template. Please leave the footer in place as it is unobtrusive and supports Tautulli. Thank you.”
At first I thought it was happening because I removed some of the padding between the bar and footer text, but then I replaced the footer section with that of the original and I’m still seeing the message. Any suggestions?
Thanks in advance!
@GoSpursGo said:
I’m getting the following Header message when the footer hasn’t been changed at all: “The Tautulli newsletter footer was removed from the newsletter template. Please leave the footer in place as it is unobtrusive and supports Tautulli. Thank you.”At first I thought it was happening because I removed some of the padding between the bar and footer text, but then I replaced the footer section with that of the original and I’m still seeing the message. Any suggestions?
Thanks in advance!
You need the <!-- FOOTER MESSAGE - DO NOT REMOVE --> line in your template.
From the beta template file: Tautulli Newsletter - ${subject}
@tycho1974 said:
@tycho1974 said:
@Migs said:
@tycho1974 said:
This is why I’m left scratching my head as to why one works but not the other. I literally copied and pasted my SMTP and login info from my PlexEmail config into the Tautulli interface, so I’m hesitant to assume that one of my settings is “wrong”. I can confirm that my PlexEmail scripts works properly, as it went out on schedule last night. My username is standard, and my password has the requisite special characters, as deemed necessary by my email server (the usual alphanumeric characters, and a single “special” character).
tycho1974, just a thought… do you happen to have 2-step verification enabled for your Google account ? If so, that would mean you would need an “app specific” password to be used for Tautulli with your Gmail account.
support.google.com/accounts/answer/185833?hl=en
I kinda ran into this problem when I was setting up my newsletters in Tautulli the other day using my Apple Mail account. I had forgotten I had enabled 2-step verification on my iCloud account and was getting verification errors. I finally remembered needing an app specific password, like Google does as well.
This may not be the issue in your case, just figured I’d throw it out there as a suggestion for you. Hope you get it figured out…
Thanks, but as I mentioned originally, I’m not using a google account; regardless, I’m not using any kind of TFA.
@JonnyWong16 — Any thoughts on this newsletter issue I’m having? I’ve tried using a gmail account, two separate private account that use an Office365 server, and nothing is working. I keep getting the same error:
ERROR Tautulli Notifiers :: Email notification failed: SMTP AUTH extension not supported by server.
I don’t know why this seems to work fine for other users but not for me. I’ve checked and re-checked the usernames, passwords, and SMTP server info and verified that they’re all current and correct.
Just updated to Tautulli 2.19, hoping my issues with the newsletter not working would get worked out. Sadly, my test still fails:
2018-05-21 18:11:35 - INFO :: Thread-2 : Tautulli Newsletters :: Recently Added newsletter saved to ‘newsletter_e03198ee.html’
2018-05-21 18:11:35 - ERROR :: Thread-2 : Tautulli Notifiers :: Email notification failed: SMTP AUTH extension not supported by server.
2018-05-21 18:11:35 - INFO :: Thread-2 : Tautulli Notifiers :: Email notification sent.
I don’t know why, after the update, I get an additional line saying the email has been sent, because I can verify that it did not send.
To recap: I’m using Tautulli 2.19, using a non-Gmail SMTP server with no TFA, with login credentials that work perfectly fine when I run PlexEmail. Am I literally the only experiencing this issue? This is getting very frustrating, and I haven’t read anything here that could help me out.
Hi all, any idea what could be causing this? Since the 17th, Tautulli suddenly started throwing this error constantly. The disk is not at fault (ran a check). I’ve tried restoring a database in case the database is corrupt; no change. I’m running tautulli on unraid in a docker container. This has been operational for years (previously plexpy). Any thoughts?
2018-05-21 17:10:03 - INFO :: MainThread : Checking if the database upgrades are required…
2018-05-21 17:10:03 - ERROR :: MainThread : Can’t connect to the database: disk I/O error
2018-05-21 17:10:03 - INFO :: MainThread : Checking if configuration upgrades are required…
2018-05-21 17:10:03 - ERROR :: MainThread : Uncaught exception: Traceback (most recent call last):
File “/app/tautulli/PlexPy.py”, line 28, in
main()
File “/app/tautulli/Tautulli.py”, line 200, in main
plexpy.initialize(config_file)
File “/app/tautulli/plexpy/init.py”, line 194, in initialize
notifiers.blacklist_logger()
File “/app/tautulli/plexpy/notifiers.py”, line 612, in blacklist_logger
db = database.MonitorDatabase()
File “/app/tautulli/plexpy/database.py”, line 123, in init
self.connection.execute(“PRAGMA synchronous = OFF”)
@JonnyWong16 Why is the Twitter limit set to 120 characters when Twitter increased the amount that users can say?
@SteveG144 said:
@JonnyWong16 Why is the Twitter limit set to 120 characters when Twitter increased the amount that users can say?
Because it hasn’t been updated.
@JonnyWong16 said:
@“roku.caleb” said:
Since I updated to Tautulli the “Plex Update available” notification is no longer working from my Telegram notification Agent.All other triggers work fine except for this one. Is anyone else having this problem?
Have you enabled Settings > Plex Media Server > Monitor Plex Updates?
LOL. I forgot to check that setting. It was enabled before I upgraded to Tautulli
All good now!
Thanks
@tycho1974 said:
using a non-Gmail SMTP server with no TFA, with login credentials that work perfectly fine when I run PlexEmail. Am I literally the only experiencing this issue?
So far, yes, likely.
You even stated you tried Gmail somewhere in a previous post. If you can’t get THAT working, following the Wiki setup instructions for a Gmail account, something is wrong somewhere on your end that none of us have encountered before, and unfortunately, the logs don’t really help. It’s almost as though you, your ISP, malware, or overprotective web proxy, is preventing the connection.
