"invalid password" for most users on hotspot login

RouterOS Beginner Basics
1

Hi.. guys .. this is my first post on mikrotik forum

OK i will jump ahead to the problem ..
most of the users "created in user manager" has to input their login information "twice" before the success to login !!
for first time the "invalid password" appears to the user although he puts the right password
and the second time he types the username and password .. he logs in successfully !!!

take a look at the info to see if i missed something! by the way it's 5.25 version

/ip hotspot profile
add dns-name=www.bytezone.net hotspot-address=10.0.5.1 html-directory=hotspot http-cookie-lifetime=3d http-proxy=0.0.0.0:0 login-by=cookie,http-chap,http-pap

name=hsprof1
nas-port-type=wireless-802.11 radius-accounting=yes radius-default-domain="" radius-interim-update=received radius-location-id="" radius-location-name=""
radius-mac-format=XX:XX:XX:XX:XX:XX rate-limit="" smtp-server=0.0.0.0 split-user-domain=no use-radius=yes

/radius
add accounting-backup=no accounting-port=1813 address=192.168.1.2 authentication-port=1812 called-id="" disabled=no domain="" realm="" secret=123456

service=hotspot
timeout=300ms
/radius incoming
set accept=yes port=3799

/tool user-manager router
add customer=admin disabled=no ip-address=192.168.1.2 log=auth-fail,acct-fail name=bytezone shared-secret=123456 use-coa=no

and finally this is a snapshot of the log i get for most users

OK guys i really trust you and sure you can help me solve this strange problem ... Thanks in advanced

2

We have been having this same issue with a few exceptions.

Started with 3 or 4 customers a few days ago, and had been progressively getting worse. Then when the daylight savings time change happened the whole radius server stopped working. Anyone who was not logged in at the time was unable to establish a connection. Even if they attempted to sign in with the right credentials the router would show a failed log in attempt and say “Radius server failure”

Then Magically it started working again.

Any idea why this might happen?