Search the Community

My log is full of this error and i dont know why... every few minutes i get this message and also 401 error for emby/Sync/data folder

I was wondering if anyone could help me with this error which keeps appearing in my logs. 016-12-04 13:18:23.5284 Error ServiceStackHost: Error occured while Processing Request: Access token is invalid or expired. *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Kenn\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Kenn\AppData\Roaming\Emby-Server Application Path: C:\Users\Kenn\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Access token is invalid or expired. MediaBrowser.Controller.Net.SecurityException at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken(IServiceRequest request, String token) at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateUser(IServiceRequest request, IAuthenticationAttributes authAttribtues) at ServiceStack.ServiceStackHost.ApplyRequestFiltersSingle(IRequest req, IResponse res, Object requestDto) at ServiceStack.ServiceStackHost.ApplyRequestFilters(IRequest req, IResponse res, Object requestDto) at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__13.MoveNext() 2016-12-04 13:18:23.6532 Error ServiceStackHost: Error occured while Processing Request: Access token is invalid or expired. *** Error Report *** Version: 3.0.8500.0 Command line: C:\Users\Kenn\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1 Processor count: 8 64-Bit OS: True 64-Bit Process: True Program data path: C:\Users\Kenn\AppData\Roaming\Emby-Server Application Path: C:\Users\Kenn\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Access token is invalid or expired. MediaBrowser.Controller.Net.SecurityException at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateSecurityToken(IServiceRequest request, String token) at MediaBrowser.Server.Implementations.HttpServer.Security.AuthService.ValidateUser(IServiceRequest request, IAuthenticationAttributes authAttribtues) at ServiceStack.ServiceStackHost.ApplyRequestFiltersSingle(IRequest req, IResponse res, Object requestDto) at ServiceStack.ServiceStackHost.ApplyRequestFilters(IRequest req, IResponse res, Object requestDto) at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__13.MoveNext() What is causing it? Suggestions to fix? This is a fresh 3.0.8500 install. But I believe this error has been there since I first installed Emby a few months ago. Emby is functioning normally as far as I can tell. Thanks for reading and any help you can offer! server-63616467062.txt

Salve mi piacerebbe sapere se è possibile con emby essere visti sulle smart v. Ho provato ma oltre a vedersi il server quando voglio vedere le tv in diretta vedo solo uno schermo nero. Grazie

Hello, I didn't see a post about this, so I thought I would ask. I'm pretty sure this has something to do with fedora, because the webplayer works fine at home on chrome/firefix/qutebrowser on arch (client side), however I'm currently on a fresh install of fedora (client side) and when I try to play a move in chrome or firefox, it hangs and in the js console I get a message about websocket problems. I added a few things to my apache config to try and fix this, but I went from a 404, to a 500 and then to a "Invalid Socket response" message. I'm wondering if I just forgot to install some library on the client side that is causing the browsers not to run the web player correctly. I checked the emby server logs and everything on the server end seems to be in order, emby even thinks the transaction was successful and shows the movie currently being played even though the web player stalled out in the browser. Nothing is showing up in the apache logs ether, so the proxypass I have set up is working fine. So my question is, could I be missing some libraries that chrome/firefox needs in order to properly talk over a webshell? I will be happy to provide the logs I mentions if you would like, but I don't know that it will be necessary as both (emby server and apache error logs) are clean.

I am having a major issue with the Fire TV Stick (It's also happening on the Nexus Player app). I recently added my sister as a guest account to my server, but on her Fire TV Stick, whenever she chooses "Login with Connect" after entering the pin on her computer using HER USERNAME AND PASSWORD, she is given the "choose a user" screen on the app. The major issue here is even though she used the pin with HER account, she is unable to launch the app using her account. It always gives the "Invalid Username or Password" error. She CAN however, click on MY username (the admin account) and the app works perfectly. This is a major issue, as I'd like to add more guests, but absolutely can't if they all have immediate access to my admin account, and not their own when using a Set top box. The app works perfectly under her account for Android, as well as the web client, but there definitely are some wires crossed when it comes to the pin sign on for the box apps. Any help would be greatly appreciated! Thank you!

As per the subject line, this has recently started to happen when using MB Classic. Whenever I select an actor to see their information, the application exits. Under the new 3.0.27 beta, at least I get an "invalid application" error in Windows Media Centre. The problem does not manifest in MB Theatre, so I think something is up with my MB Classic. Has anyone else experienced this?

Every time I start media browser theater it shows following screen. And when clicked on OK, MBT crashes. I tried removing (deleting all files in "%appdata%") and reinstalling MBT, but it didn't work. And one more thing, every time I install MBT it installs beta version automatically. MBS Version :- 3.0.5238.39498 MBT Version :- 3.0.5265.16010 crash_1eae0897-d675-4059-b1ec-6ba864d5777d.txttheater-install.log

MB3 Key Missing or Invalid - in order for any premium content to be registered, you must also be an MB3 Supporter. Please donate and support the continued development of the core product. Thank you. I have 2 I bought Square and it reads expired so I decided to link them again now the newest one reads invalid as does the older one email is dave@white-elephant.co.uk