JS file requested which does not exist

  • Resolved Tim Reeves

    (@tim-reeves)


    2 years, 9 months ago

    This is a real killer for me, my Nginx Config is returning a 403 for JS files which don’t exist (hackers looking for an attack vector) and Fail2Ban picks that up and blocks the user – in this case, my boss )-:

    Here’s an extract from the Nginx log:
    “GET /wp-content/plugins/fluent-smtp/assets/admin/js/vendor.js?ver=2.1.0 HTTP/2.0” 403 86 “https://gesandtschaft.com/wp-admin/options-general.php?page=fluent-mail”

    The directory assets/admin/js exists, but no file vendor.js – which sounds like something left over from dev…

    Would be really grateful if this can be fixed – should be a trivial job.

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘JS file requested which does not exist’ is closed to new replies.