Hi,
Can you please point me to the file which holds the failed login IPs? I can’t find it in the logs folder, but it’s definitely there somewhere since I can see it from the web interface login logs.
Thanks!
Hi,
Can you please point me to the file which holds the failed login IPs? I can’t find it in the logs folder, but it’s definitely there somewhere since I can see it from the web interface login logs.
Thanks!
@thunder2k - I’m 90% sure the IPs are stored in the SQLite 3 main tautulli.db file.
There are a few mentions of login attempts in \logs\tautulli.log too, but I think that’s just a general warning - no direct tie to the db file storing the attempt.
Thanks for the info. I’m trying to setup my fail2ban server to avoid bots attempting to login. Any chances it could be added?
Directly, probably not. In theory, you might use a .htaccess file combined with nginx.
(info here for nginx proxy - https://github.com/Tautulli/Tautulli-Wiki/wiki/Frequently-Asked-Questions#q-why-does-tautulli-not-work-with-my-reverse-proxy-setup)
I see there is a ‘basic html authentication’ in settings of Tautulli too, but don’t know (nor believe it would) if it would make a log difference.
Please realize I’m a general IT geek - I understand 80% of what I’m referencing, but have no experience with the above to be able to help. I just now googled what fail2ban even is.
I’m sure some experienced person could come by here and totally sweep my theories out the door.
EDIT - See, i’m totally wrong about htaccess and nginx.
https://www.nginx.com/resources/wiki/start/topics/examples/likeapache-htaccess/
Sorry, I don’t have further idea.
Thanks a lot for your help. I posted the same question in the subreddit and a developer confirmed it’s in the db and they can’t add to the logs file.
I think I’ll write a script to query the db and export the IPs.
@Thunder2k - Tautulli API has a “get_user_logins” command - returns typical json data.
Might be able to poll with regular interval.
Have fun tinkering.
Tautulli Helpers :: Image 'Any movie' (poster) transformed on Cloudinary.
Why are posters for shows from live stats being posted to cloudinary???
When did this start, and, without removing the feature for newsletters/recently added posters to be hosted on Cloudinary, how do I turn this off?
I don’t mind having Tautulli use the local poster because so few actually log in other than myself - I really don’t want to upload every poster every time someone wants to watch something, but only when a newsletter is sent, or history of recently added posted to my site.
Tautulli has no knowledge of whether or not you are using a notification agent with posters enabled or whether or not you have {poster_url} in your notification text. Therefore it preemptively uploads first.
Ouch! That seems inefficient.
I’m going to have to reconsider my maintenance schedule or hosting options then. I never noticed key terms ‘for notification and newsletter’ in the Plex image area.
I’ve used 60% storage limit of my Cloudflare account in the past few months.
PlexEmail only did it for newsletters until it died, so didn’t take as much space.
EDIT
Seems it should by the way, there’s a checkbox ‘include poster’
![]()
That’s not how it works.
When was the last Tautulli update? Was it around April 19, 2019?
EDIT: Nevermind I look at the update log.
v2.1.29 (2019-05-11)
No additional changes from v2.1.29-beta.
v2.1.29-beta (2019-04-14)
Just wondering why I lost logging of history again. Real-time monitoring still worked it just wont log it. It seemed to stopped 04.19.2019. Very odd. I deleted the DB and now it’s logging into the history.
Has anyone got the docker version of Tautulli working on a Synology nas and connecting to a PMS running on the same nas? (I am using the official Tautulli container)
I am a bit stuck/confused.
From Tautulli in Docker, I can verify my other servers, one on an external network and another one on my iMac on my local network. But I can not for the life of me get it to verify the one on the nas.
I see messages about
Is your server maybe accepting SSL connections only
and
Connection timeouts
I can connect to the PMS on the nas via a web browser using the local ip address of the nas and port 33400, but putting these same values in Tautulli running in the Docker and trying to verify the server fails.
I have disabled the firewall on my nas in case that was causing the problem, but that did not seem to make any difference
If I run Plexpy Custom from the package center that can connect to the PMS on the nas. Which suggests that the PMS is accepting connections.
(and running Plexpy Custom seemed to be the only solution I could find on the interwebs)
I know I could keep using that, but I would just prefer to have them in all in separate dockers if at all possible.
So any suggestions gratefully received. Ta.
Depends if you have Docker using host mode or bridge mode. Try using the Plex container’s IP address (not the NAS IP address).
Thanks very much for the reply.
Ah, sorry I was not clear, it was only the Tautulli’s that I was planning to run in docker containers, at least for now (1 for each of my PMS)
The PMS on the nas is running on the nas, not in a container.
But… anyways, I got it to work. 
So for anyone else that might find it useful.
When you initially create the container, in the Network tab, there is a checkbox to use the same network as Docker host, so I checked that.
(fwiw, You can only do this when creating the container, there is no Network tab when you edit an existing container)
Once you select that you can no longer change anything in the Port Settings tab, so I just carried on and set the environment vars.
Launched the container and loaded Tautulli from the ip address of the nas and port 8181
and… success Tautulli loaded and now can verify the server using the ip address of the nas and port 33400.
(Once you have finished setting up the container and look in the docker network panel in the DSM you will see the container has been added to the host network section)
Hi guys,
I was away for few days and my raspberry pi was offline/rebooted several times because of a router issues. After I fixed that and restarted my RPi everything looks normal, except that when I try to login to my Tautulli web interface I’m being presented the setup wizard like the first time I installed it. It was running fine before this issue. Before I break/override something, is there anything I could do to fix this? I tried to restart the Tautulli service but this didn’t fix the issue.
Any advices?
Thanks!
You lost the config.ini file, or you lost the permissions to access the config.ini file.
@SwiftPanda16
I commonly get this error
Did you do what the message says to “check the logs and verify your server connection in the settings”?
Well… I’ve looked at the logs here and there and while the logs are more stupid simple to read I don’t always know what I’m looking at. A simple F5(refresh) fixes the issue. Till the next video encode…
I was hoping there was a setting I was overlooking to extend the TIMEOUT or whatnot.
Hi,
I’ve checked and the config.ini file seems intact and in its place in /opt/Tautulli.
Anyway I managed to fix this copying the latest config.ini and tautulli.db files from the backup folder.
Thanks
Bye