Web Admin Login Fails v3.9.2 (161119)
|
2016-11-20, 05:22 AM
Upgraded to 3.9.2 this evening, now my NEWA login fails.
Is there any way to reset it? (I suspect the encryption/salt changed.) (Going to try renaming web config file and see if it'll make a new one.)
2016-11-20, 05:40 AM
There seems to be some bug with the web admin login.
1. config-web.xml no longer appears to be used 2. If I make a login called 'admin' with any password, NEWA always says it's invalid. If the login name is not admin it seems to work.
2016-11-20, 06:06 AM
The default admin/password login is no longer accepted for remote logins, to force users to use something more secure.
Not sure I am having the same problem, but what is the new procedure for signing in using the modern web. Attached are my log files. No issue connecting with Kodi 17.
Also some good news for me, the memory leak issue has gone away with the latest version 3.9.2. Ran numerous movies and TV shows, no increase in DWM size. Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". Message from Client machine. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>
2016-11-20, 03:23 PM
Barry10 Wrote:Not sure I am having the same problem, Probably not. What are you using as a hostname? Your source here is ipv6 because of the selection you made. Martin
http://backup:8866 and also tried http://127.0.0.1:8866 Kodi is using the 127.0.0.1:8866 on the same machine. Also using Microsoft Edge.
Also on the host machine 127.0.0.1:8866 works, but Backup:8866 does not.
2016-11-20, 04:08 PM
Barry10 Wrote:http://backup:8866 and also tried http://127.0.0.1:8866 Kodi is using the 127.0.0.1:8866 on the same machine. Also using Microsoft Edge. Kodi doesn't use NEWA. backup I can understand and I can speculate on localhost but I am surprised 127.0.0.1 doesn't work. Does [::1] work? (you need squre brackets) Martin
2016-11-20, 04:12 PM
http://backup:8866 and also tried http://127.0.0.1:8866 Kodi is using the 127.0.0.1:8866 on the same machine. Also using Microsoft Edge.
2016-11-20, 04:22 PM
On my local host I have Nextpvr running and Kodi. The 127.0.0.1 works, but on any other machine I get the above error. Also backup:8866 does not work on the local machine either. Backup is the name of the machine.
2016-11-20, 04:36 PM
Ok so if you use the IP of your server from remote machines it probably works too.
Since you are using ipv6 from Edge you would need to ensure backup can be resolved as an ipv6 name on the server. From the command prompt type ping -6 backup If that fails on the server that is the problem. Martin |
|
|
