Locked out

I have installed the demo version and have been testing for a few days. Suddenly I am locked out and unable to login from a remote workstation. Username and password are still demo/demo, the result on login is:



401 Unauthorized

A password is required to access this web server. Please try again.



Username / Password is still demo/demo. Please update.





I am able to login in localhost, but even if I change the admin login I am not able to login remote.



Todays events says:



You are currently using the 21-day trial version. It ends in 20 days. Monitoring Software license pricing & purchase. Technical support



What am I missing?



Thanks!



Marcel van Beuzekom

Apada

What are the first 5 lines of your serverscheck.conf file?

These are the first 5 lines:





LOGFILE:true

GRAPHS:true

HTML:true

SETTINGS:demo<X>53616c7465645f5f5ba2bdd437f8c82b1dcb6f773c526a63<X><X><X><X><X><X><X><X><X><X><X><X><X>

SETTINGS:demo<X>53616c7465645f5fe86704a1acb81aba44b27dcd3025de994e115ec29286d3e842e15aaa953fa923e0e88b6dc516ce8ad07bfc12e26d66e82a102e07cd22fdfd621083fdf6d7e4c3<X><X><X><X><X><X><X><X><X><X><X><X><X>



Thanks for your help!



Regards,



Marcel van Beuzekom

Apada

Something has corrupted your conf file.



Remove the 4th line and try again.

I'm sorry, this does not solve the problem. To check I stopped the service and remove the 4th line resulting in the lines:



LOGFILE:true

GRAPHS:true

HTML:true

SETTINGS:demo<X>53616c7465645f5fe86704a1acb81aba44b27dcd3025de994e115ec29286d3e842e15aaa953fa923e0e88b6dc516ce8ad07bfc12e26d66e82a102e07cd22fdfd621083fdf6d7e4c3<X><X><X><X><X><X><X><X><X><X><X><X><X>



After starting the service (before opening any webpage to the service, the .conf is changed to:



LOGFILE:true

GRAPHS:true

HTML:true

SETTINGS:demo<X>53616c7465645f5fe86704a1acb81aba44b27dcd3025de994e115ec29286d3e842e15aaa953fa923e0e88b6dc516ce8ad07bfc12e26d66e82a102e07cd22fdfd621083fdf6d7e4c3<X><X><X><X><X><X><X><X><X><X><X><X><X>

SETTINGS:<X>53616c7465645f5fe965e2fb6272da2d0fe801ffd1361550<X><X><X><X><X><X><X><X><X><X>

The first line seems to be missing too.



The first 6 lines need to be like that:

SMTP:<X><X><X>[email protected]<X>%l is %s<X>status of %l (%d - %g) changed to %s at %t. Reason: %r<X><X><X><X><X><X><X>1

LOGFILE:true

GRAPHS:true

HTML:true

SMS:demo<X>demo<X>10<X>300<X>300<X><X><X><X><X><X><X><X>

# checktype|X|check label|X|retries|X|check interval in seconds|X|email alert to|X|network message to|X|sms alert to|X|fail on up/down|X|fail on value1|X|operand|X|



Reset the password.

I installed ServersCheck on a different server and copied the lines to the test server. This solved my login problems.



I am missing some of the tests now but I will recreate them.



Thanks for your help!

I have similar issue

why something like this would happen.

I keep copying the file and it keep getting deleted or adding that extra line?



I am runing 7.9.0

What steps did lead to this. Please replicate the steps leading to it so that we can isolate the issue.

I hope you don't mind me posting in this old thread, but I thought it would be best to put this here rather than starting a new one (since the problem seems like being the same).





I've been testing ServersCheck 7.15.7 and I've encountered more or less the same issue. The STMP line at the top of the serverscheck.conf file had disappeared and there were now two lines (4 & 5) with administrator credentials (named administrator in this case, not demo). This quite effectively locked me out of the configuration website with administration right, except locally on the testing rig itself.

I was able to correct this without too much trouble myself (simply editing the .conf file), but it is quite troubling that the configuration files might get broken somehow.



This happened to me when testing with monitoring rules that required Windows Login user information (adding new Windows User Credentials while creating the monitoring rule itself, rather than adding them up front and using them from the drop down).

A few times it went fine, but then 2 or 3 times in a row, it killed my administrator login. It might have something to do with the fact that I was adding credentials with their IP instead of domains (like 10.9.8.7Administrator instead of DomainAdministrator), but of that I cannot be certain.



Hopefully this helps you guys track down this issue.





(The testing setup was an Intel Dual Core, Win XP Pro, 1gb RAM, though I doubt this is hardware or OS related)

If you can define step by step what you did to get the issue, then that would be appreciated as it allows us to replicate it and post a fix for this annoying issue.

It's hard to describe the procedure step by step (it was a week & a half ago, details are a bit foggy).



From Device View, I added a new monitor to an already existing device. I picked a Windows related monitor in the wizard (like services or diskspace), configured for once every 3 minutes, 1 retry. When configuring the monitor settings, I added a new Windows User Credential, tested the settings a few times before getting the service right. After I finished off the monitor, I received a message that I wasn't allow to access the website.



I'm afraid that I cannot give any more details than that.