404 error

  • MarionFW

    (@marionfw)


    9 years, 11 months ago

    Since the last update I get an error log that is full of 404-errors for which the referrer is my own website.

    The strange thing is that in the log the URL for all errors is identical:

    /wp-content/plugins/better-wp-security/C:/domains/(mysite.com)/wwwroot/wp-content/plugins/better-wp-security/core/modules/strong-passwords/js/script.js

    Under ‘details’ I only find the following text:
    query_string = ver=4041

    I checked the settings if there is any reference to c:/domains etc. but that is not the case. I googled, but found nothing on this issue, and I really have no idea where to solve this. I hope someone can help me out.

    https://ww.wp.xz.cn/plugins/better-wp-security/

Viewing 7 replies - 1 through 7 (of 7 total)
  • wildypeng

    (@wildypeng)

    9 years, 11 months ago

    I have the same issue (hosted on Windows), in the output source of the login page I see:

    I have removed the domain and windows file path for security reasons.

    <script type='text/javascript' src='http://*domain*/wp-content/plugins/better-wp-security/*Windows File Path*/wp-content/plugins/better-wp-security/core/modules/strong-passwords/js/script.js?ver=4041'></script>

    Thread Starter MarionFW

    (@marionfw)

    9 years, 11 months ago

    for the record: my site too is on Microsoft server.

    eamonlaser

    (@eamonlaser)

    9 years, 6 months ago

    Mine too – Windows server, WP 4.6.1, iThemes Security Version 5.7.0

    /wp-content/plugins/better-wp-security/E:/domains/**REMOVED**/www/wp-content/plugins/better-wp-security/core/modules/strong-passwords/js/script.js

    Looks like its jumbled the URL up and that’s causing a 404 error because the URL is rubbish.

    I read somewhere else about whitelisting that URL so I might try that, but I don’t like editing the security plugin’s settings like this!

    eamonlaser

    (@eamonlaser)

    9 years, 6 months ago

    Whitelisting the URL worked. I copied the full URL from the error log and pasted it into the whitelist of the 404 detection settings and saved that. The errors stopped straight away, and as the URL is nonsense I feel this fix probably won’t cause any problems in the future.

    Thread Starter MarionFW

    (@marionfw)

    9 years, 6 months ago

    Thanks for the reply, it certainly is a practical workaround. Let’s hope it won’t effect the good working of iThemes.
    I’m not sure if I should regard this as closed, as it is no real solution.

    burolla72

    (@burolla72)

    9 years, 4 months ago

    please fix with the script below in class ITSEC_Lib file class-itsec-lib.php at line 405 almost:

    public static function get_module_path( $file ) {
//replace the last slash if present with backslash only for windows...
		$path = str_replace( str_replace('/','\\',ITSEC_Core::get_plugin_dir()), '', dirname( $file ) );

    ciao

    pronl

    (@pronl)

    9 years, 4 months ago

    @burolla72

    Thank you for sharing that fix. However as soon as one updates the plugin to the next version the fix will be lost and needs to be reapplied …

    Not very practical.

    Also whitelisting the failing URL prevents 404s from being logged but the Strong Passwords feature is still broken.

    Best solution would be for iThemes to fix this bug.
    However that is probably not going to happen. Why not ?
    iThemes is not interested in hosting on platforms with unsignificant marketshare.
    So running this plugin on a Windows platform is a risk.
    There is no (NONE) Windows platform testing being done by iThemes.
    (If they did, this bug and a couple of other ones would not exist).

    A more practical solution (but still not ideal) would be to include a fix in the functions.php file of the active theme. Thus updating the plugin to a new version would not undo the fix.

    Another option is to switch to a Linux hosting platform 😉

    • This reply was modified 9 years, 4 months ago by pronl.
Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘404 error’ is closed to new replies.