In my log file System > Log files > Backend, I have thousands of entries like this:
Date SeverityProcess Line
2024-07-17T10:48:10 Error api no active session, user not found
2024-07-17T10:48:10 Error api no active session, user not found
2024-07-17T10:48:08 Error api no active session, user not found
2024-07-17T10:48:07 Error api no active session, user not found
2024-07-17T10:48:06 Error api no active session, user not found
2024-07-17T10:48:05 Error api no active session, user not found
2024-07-17T10:48:05 Error api no active session, user not found
2024-07-17T10:48:03 Error api no active session, user not found
2024-07-17T10:48:02 Error api no active session, user not found
2024-07-17T10:48:01 Error api no active session, user not found
Should I be concerned about this? Any way to diagnose and track down the cause?
I've had this for a long time too. It has nothing to do with captive protal, nor does it have anything to do with the Unbound DNS resolver (as several Google results suggested).
Somebody is connecting to the UI/API and twiddling the door knob. Is your UI open to the Internet?
Quote from: Patrick M. Hausen on September 21, 2024, 06:41:36 PM
Somebody is connecting to the UI/API and twiddling the door knob. Is your UI open to the Internet?
My settings for this (Listen Interfaces): LAN
Thanks!
Then something from your LAN is accessing your UI without logging in. Do you have a monitoring system in place that checks the UI, perhaps?
Also: don't change the listen interface unless you absolutely must.