zoraxy icon indicating copy to clipboard operation
zoraxy copied to clipboard

Entry for 404 Error in Log.

Open DonniDoc opened this issue 1 year ago • 0 comments

Is your feature request related to a problem? Please describe. My plan was to make it difficult for port scanners. Port scanners usually don't know my domain / subdomain but access via the IP. They receive 404 NOT FOUND from Zoraxy. But this process is not logged in the log. That's bad. Because then I can't block corresponding IPs on the host using Fail2Ban.

Describe the solution you'd like Would it be possible to log an error message for Error 404 NOT FOUND?

Describe alternatives you've considered I already thought that Error 404 would be a "success" for Zoraxy and that it would be redirected to the integrated web server. But there is no 200 entry in the log with a reference to the internal web server. I also don't want to redirect Error 404 to internal resources. Things like that should stay outside.

Additional context I want to block the IP on the system because my experience is, that the same person afterwards pokes around on other ports (Wiregurad). "Close connection" in Zoraxy could be an option as it results in a log entry 444. But entry for 404 would also be nice.

DonniDoc avatar Mar 06 '25 19:03 DonniDoc