Why are users converted to RADIUS authentication unable to login?
This article is an interim workaround for this issue, which affects Statseeker 5.6.2, 25.2, and 25.3. The fix is expected towards the end of 2026.
The problem is there is an entry in the password file for the existing user that needs to be deleted.
/home/statseeker/base/etc/sspasswd
To resolve the issue please delete the line for the user from this file.
Please take a backup of the sspasswd file before editing it.
e.g.
cp -p sspasswd sspasswd.bkup
If this does not work I suggest running a tcpdump to see if Statseeker is sending anything to the RADIUS server and if it is getting something back.
e.g.
# tcpdump -D
1.vmx0 [Up, Running, Connected]
2.lo0 [Up, Running, Loopback]
# tcpdump -i vmx0 -nn port 1812 or port 1813
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on vmx0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
10:26:04.371422 IP 10.2.20.183.1026 > 10.2.1.11.1812: RADIUS, Access-Request (1), id: 0x5b length: 90
10:26:04.378464 IP 10.2.1.11.1812 > 10.2.20.183.1026: RADIUS, Access-Accept (2), id: 0x5b length: 20
^C
2 packets captured
129112 packets received by filter
0 packets dropped by kernel