Suddenly can't login to web app

[SamM]

I've rebooted several times. I tried Chrome, nothing seems to work. I take it the log files don't reveal anything? Maybe I need to install v.4?
sm

[mvallevand]

In Chrome if you open developer mode with F12 and type http://localhost:8866/ do you seen any error messages?

F12 again will turn it off

Martin

[SamM]

I don't see anything that looks like errors to me. See attached - it's what I see after attempting login. If I reinstall it, do I need to use the default login?
sm

PS I tried the default login, and IT WORKED. Somehow it reverted back to default login. What can cause this (I didn't reinstall).
sm

PPS Ok, so I updated to 5.0.7. And had to redo some of my settings. Is this to be expected every time it's updated to the new version?
sm

[sub]

PS I tried the default login, and IT WORKED. Somehow it reverted back to default login. What can cause this (I didn't reinstall).
sm

If somehow your config.xml is corrupted (like you machine powered off while writing to it, or bad disk), it can restore to a default copy of the config file.

PPS Ok, so I updated to 5.0.7. And had to redo some of my settings. Is this to be expected every time it's updated to the new version?
sm

No, settings are retained between updates, and you normally wouldn't have to redo any settings. If you config.xml has been recreated though, this could explain some settings returning to their defaults, and needing to be reset.

[Graham]

PS I tried the default login, and IT WORKED. Somehow it reverted back to default login. What can cause this (I didn't reinstall).
sm

If somehow your config.xml is corrupted (like you machine powered off while writing to it, or bad disk), it can restore to a default copy of the config file.

Sub

Has there been at least one previous similar thread?

Should the password and username be stored somewhere a bit more robust that config.xml?

Could the username and password have their own file such as, for example ... userpass.xml ... Could there be a ... userpass-master.xml ... that a user could copy over userpass.xml to do a password reset?

Could the login screen display a messsage that says ... Username and password have default values ... when that is true?

[sub]

Hmm, I'm not sure if we've really seen anything to indicate there is a problem. This same config.xml stuff has been in use and pretty damn reliable since like 2008-ish?

We're not really sure that was what his problem was. Occasionally issues like this are users forgetting what they changed a password to, or manually editing config files and messing up.

[BrettB]

PS I tried the default login, and IT WORKED. Somehow it reverted back to default login. What can cause this (I didn't reinstall).
sm

If somehow your config.xml is corrupted (like you machine powered off while writing to it, or bad disk), it can restore to a default copy of the config file.

Sub

Has there been at least one previous similar thread?

Should the password and username be stored somewhere a bit more robust that config.xml?

Could the username and password have their own file such as, for example ... userpass.xml ... Could there be a ... userpass-master.xml ... that a user could copy over userpass.xml to do a password reset?

Could the login screen display a messsage that says ... Username and password have default values ... when that is true?

Hmm, I'm not sure if we've really seen anything to indicate there is a problem. This same config.xml stuff has been in use and pretty damn reliable since like 2008-ish?

We're not really sure that was what his problem was. Occasionally issues like this are users forgetting what they changed a password to, or manually editing config files and messing up.

There have definitely been cases in the past (with v4) where the config.xml got corrupted and the NextPVR service wouldn't start up properly.

I don't specifically recall seeing that problem with v5, but would guess it could still be a "problem". It may be that with v5 you changed it so that if the config.xml was corrupted, rather than hanging or dying, it would automatically copy over the default config.xml and then start up. The problem with that scenario is that if the user doesn't know about, they may be unable to log in, recordings may go to the wrong directories, etc. Also, not ideal.

[sub]

It may be that with v5 you changed it so that if the config.xml was corrupted, rather than hanging or dying, it would automatically copy over the default config.xml and then start up. The problem with that scenario is that if the user doesn't know about, they may be unable to log in, recordings may go to the wrong directories, etc. Also, not ideal.

It's just the same as v4.

If there is no existing config.xml, or the existing one is zero bytes long, it'll create a new config.xml file form the master.

If there is an existing file, with data in it, but it is invalid, the file will be renamed config-broken.xml, and a new one file created, so the application can be started.

It's not entirely fail proof, but config.xml has been pretty reliable for us over the years. A full c:\ drive can increase your odds of issues.

[jobby99]

Stop the NextPVR Service.

Edit the c:\users\public\NPVR-data\config.xml file, to set the following in the <WebServer> section:

    <Username>admin</Username>
    <Password>5f4dcc3b5aa765d61d8327deb882cf99</Password>

then restart the NextPVR Service

Thank you!!  Fixed the problem.  Don't know what the alphanumericals mean but reset it back to defaults in all browsers.  It was driving me crazy.

[jamessbuzzz]

I can only guess you were trying the wrong password.