Authentication problem on Sony TV

[johnvick 1]

V 4.3.1.0 on Ubuntu server - Emby working fine on computers, tablets, phones, Android Sony TV (via Kodi/Embycon) and via browser on same TV.

 

On my older Sony TV using the inbuilt browser I get the login page but cannot authenticate:

 

Portion of log below: any ideas what's going on? Users don't need passwords on LAN.

 

Thanks for any help.

 

*** Error Report ***

Version: 4.3.1.0

Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3

Operating system: Unix 4.15.0.58

64-Bit OS: True

64-Bit Process: True

User Interactive: True

Runtime: file:///system/System.Private.CoreLib.dll

Processor count: 4

Program data path: /config

Application directory: /system

System.Exception: System.Exception: Invalid username or password

   at Emby.Server.Implementations.Library.DefaultAuthenticationProvider.Authenticate(String username, String password, User resolvedUser)

   at Emby.Server.Implementations.Library.UserManager.AuthenticateWithProvider(IAuthenticationProvider provider, String username, String password, User resolvedUser, CancellationToken cancellationToken)

Source: Emby.Server.Implementations

TargetSite: System.Threading.Tasks.Task`1[MediaBrowser.Controller.Authentication.ProviderAuthenticationResult] Authenticate(System.String, System.String, MediaBrowser.Controller.Entities.User)

 

2020-01-06 09:35:30.755 Info UserManager: Authentication request for ruth has succeeded.

2020-01-06 09:35:30.755 Info SessionManager: Reissuing access token: 66e91aba3b6544029a5ba25f78c44c7f

2020-01-06 09:35:30.757 Info HttpServer: HTTP Response 200 to 192.168.1.58. Time: 13ms. http://192.168.1.2:8096/emby/Users/authenticatebyname

2020-01-06 09:35:30.760 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-12-29T20%3A35%3A30.839Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:35:30.760 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2020-01-04T20%3A35%3A30.838Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:35:30.765 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 5ms. http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2020-01-04T20%3A35%3A30.838Z&hasUserId=true

2020-01-06 09:35:30.766 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 6ms. http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-12-29T20%3A35%3A30.839Z&hasUserId=false

2020-01-06 09:35:30.801 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-12-29T20%3A35%3A30.879Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:35:30.801 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2020-01-04T20%3A35%3A30.879Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:35:30.803 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 3ms. http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-12-29T20%3A35%3A30.879Z&hasUserId=false

2020-01-06 09:35:30.804 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 3ms. http://192.168.1.2:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2020-01-04T20%3A35%3A30.879Z&hasUserId=true

2020-01-06 09:36:03.109 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/Users/c5ad8a1925714958ae4958a08c89f110. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.113 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 5ms. http://192.168.1.2:8096/emby/Users/c5ad8a1925714958ae4958a08c89f110

2020-01-06 09:36:03.115 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/web/configurationpages?Name=webhooks. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.121 Info HttpServer: HTTP GET http://192.168.1.2:8096/web/configurationpage?name=webhooks&v=4.3.1.0&r=0. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.149 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 33ms. http://192.168.1.2:8096/emby/web/configurationpages?Name=webhooks

2020-01-06 09:36:03.153 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 32ms. http://192.168.1.2:8096/web/configurationpage?name=webhooks&v=4.3.1.0&r=0

2020-01-06 09:36:03.155 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/web/strings?PluginId=85a7b1d4-fbda-4e85-a0a2-ac303c9946a4&Locale=en-US&v=1578256091445. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.167 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 13ms. http://192.168.1.2:8096/emby/web/strings?PluginId=85a7b1d4-fbda-4e85-a0a2-ac303c9946a4&Locale=en-US&v=1578256091445

2020-01-06 09:36:03.195 Info HttpServer: HTTP GET http://192.168.1.2:8096/web/configurationpage?name=webhooksjs&v=4.3.1.0. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.197 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 2ms. http://192.168.1.2:8096/web/configurationpage?name=webhooksjs&v=4.3.1.0

2020-01-06 09:36:03.215 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/Configuration/webhooks. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:03.245 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 30ms. http://192.168.1.2:8096/emby/System/Configuration/webhooks

2020-01-06 09:36:04.149 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:04.150 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

2020-01-06 09:36:04.152 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 2ms. http://192.168.1.2:8096/emby/System/Configuration

2020-01-06 09:36:04.152 Info HttpServer: HTTP Response 200 to 192.168.1.80. Time: 4ms. http://192.168.1.2:8096/emby/System/Logs

2020-01-06 09:36:05.304 Info HttpServer: HTTP GET http://192.168.1.2:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36

 

 

[Luke 37065]

HI, by older, how old? What browser does it use? Please attach the complete emby server log. The above log snippet makes it appear as though you're simply entering the wrong password.

[johnvick 1]

Sony KDL-40W600B Opera browser.

[Luke 37065]

Ok, please attach the complete emby server log. There's nothing in that log snippet mentioning opera. Thanks.

[johnvick 1]

Sorry having trouble attaching the logs - should be there now and thanks for the prompt repsonse..

 

And the TV is from Feb 2014.

emby-log.txt

Edited January 5, 2020 by johnvick

[Luke 37065]

UserAgent: Opera/9.80 (Linux armv7l; InettvBrowser/2.2 (00014A;SonyDTV140;0001;0001) KDL40W600B; CC/NZL) Presto/2.12.407 Version/12.50

So this is like 2014 era? Old but not completely ancient. Unfortunately I don't have an answer for you right now as I don't have this type of model on hand for testing.

 

The error messages in the log suggest that you're simply entering the wrong password. Are you sure you're entering the right one? Perhaps you can make things easier for yourself by enabling the options to sign in on the local network without a password. Then you won't have to enter your password on the TV.

 

Please note, either way you'll get a better experience using the Emby Theater web app as this is made for TV devices:

 

http://tv.emby.media

 

My same guidance about logging in still applies, but once you get logged in, I think you'll enjoy the Emby Theater web app more.

[johnvick 1]

I'm 100% sure re passwords, I don't use then on the local machines and I created a new test user without password - same result. Also the browser dows not display the person icon but a Chinese looking character. 

 

I tried http://tv.emby.media but no luck on the 2014 Sony - couldn't navigate between the fields to input the details - and on the 2019 Android Sony I couldn't connect to the server.

 

Worked fine on the PC. I'll give up on the old Sony set and assume it's a browser incomaptibility - thanks again for the help.

[Luke 37065]

On the tv web app you could use our Emby Connect pin code sign in feature so that you could enter the password using another device...but then again, these issues are a good indication that there will be more problems after logging in, so it might not be worth it.