jks

"/" is considered one of the keys that are redirected to the frequency field (also 0-9 . , : - # k M enter/return backspace/delete). And that must be terminated by an enter/return. Because instead of a plain "/" you could have typed "/low,high" or "/width" (passband specification) as the frequency field help shows.

From the admin console type: cdk; rm opt.debug and then restart. That will stop those additional logging messages.

@smg Running fail2ban would kill the Linux realtime response causing the audio to break up as the Kiwi server process becomes starved for CPU cycles. You can't run a heavy process like a Python interpreter at the same time. We are already extremely lucky that running kernel iptables filtering and user mode frp proxying doesn't cause trouble.

@F5LFE This is really interesting to me because it seems to be an admin connection attack. I'll bet each of those is trying with a different password.

Here's something you can do to verify that. With the admin console type cdk; touch opt.debug. And then click the restart button on the admin control tab. This will print more messages in the log when someone connects including the attempted password. See if it changes each time.

Look for log entries of the form:

PWD admin admin RESULT: allow=0 pwd_s=<actual admin pwd> pwd_m=<attempted pwd> cant_determine=0 is_local=0 is_local_e=0 [IP address]

Wow, one of the few times the YouTube algorithm has recommended an extremely useful video.

In a few minutes I learned more about practical PCB RF design than I ever knew. Very easy to understand: https://www.youtube.com/watch?v=xhuHAhIKWoM

And there went half my day. This is from the forum server. Goddamn Chinese AI companies. OpenAI.com too (although they were slightly better behaved). I had to beef up the IP filtering on the forum server to match what the proxy/web server (kiwisdr.com) has.