DancingTable 11 Posted December 11, 2024 Posted December 11, 2024 Hello! I am brand new to emby. Based on everything I've done so far, minus some minor things I'm trying to fix (and, at the end of the day, will not likely stop me from proceeding with emby to replace plex), I plan on buying it. But, repeated in my logs, every single second is this: 2024-12-11 13:10:20.231 Warn Server: AUTH-ERROR: 172.17.0.34 - Access token is invalid or expired. 2024-12-11 13:10:20.231 Error Server: Access token is invalid or expired. 2024-12-11 13:10:20.231 Info Server: http/1.1 Response 401 to host1. Time: 0ms. GET http://10.52.3.36:8096/sessions I've attached the full log file as well. I literally deleted my server, and all appdata for it, and reinstalled it as a blank slate, thinking I could re-add plugins/folders and check the logs continuously until I saw the error re-appear, but it's there on the fresh server. I didn't even add any media folders, no config changes nothing. Running on unRAID. Attached is a photo of my config. To be clear, these aren't specifically causing an issue in usability, but I don't want to spend $120 and find out later that they are an issue, I just didn't notice exactly what it was until after I paid for it, so I am trying to see what they are and what I can do to fix them.
DancingTable 11 Posted December 11, 2024 Author Posted December 11, 2024 Apparently, I lied when I said I attached the full log file. Here it is. logs.txt
Solution Luke 42077 Posted December 11, 2024 Solution Posted December 11, 2024 HI, before you reinstalled, did you configure any external applications to be able to connect to your emby server? Something is constantly pinging the server, coming from 172.17.0.34, and I can tell it's not an Emby app. Basically it looks like you configured something, and that something is still trying to connect based on credentials from the old server installation. 1
DancingTable 11 Posted December 11, 2024 Author Posted December 11, 2024 Jellystat. I set it up for Jellyfin when I was testing different things, and because it's on the same port, jellystat just kept trying it. I feel like an idiot now. As soon as I stopped jellystat, the errors went away. Thank you for your help! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now