When something else than a SOCKS5 client touches the file transfer proxy, a very verbose exception is logged on level ERROR.

Administrators can’t really fix anything here, nor does this likely affect functionality (this can be triggered by something as silly as a port scan, I believe).

Let's reduce the verbosity of messages like these: