Warning message remains although plugin wp-cron-http-auth up & running

  • Reproduction:

    1. Had Media Deduper installed on staging server for a while now.
    2. Recently activated HTTP Basic Auth on my Staging Server.
    3. Henceforth had warning:

    It looks like your site is password-protected, which may interfere with Media Deduper’s ability to index your media and content.?Check our documentation?for more info and suggested troubleshooting.
    Check again

    1. I read the linked documentation, then accordingly:
    2. Installed + activated plugin wp-cron-http-auth, configured credentials.
    3. All other wp-cron related issues on the website, like plugin auto-updates, which had stalled, soon thereafter resolved themselves. So wp-cron seems to be up and running.
    4. Nevertheless Media Deduper’s warning remained. And I can’t get it away anymore.
    5. Clicking “Check again” leads to:

    /wp-admin/options-general.php?page=mdd_pro&mdd_cbur_nonce=XXX

    which returns HTTP 403 Forbidden with a minimalist error page “Sorry, you are not allowed to access this page” not rendered from the Webserver, but clearly rendered by WordPress itself as in the HTML it has <title>WordPress ? Error</title>).

    1. Tried to delete the transient manually with wp-cli:
    $ wp transient delete mdd_wp_cron_request
Warning: Transient was not deleted; however, the transient does not appear to exist.
    1. Temporarily also disabled OPCache. Made no difference.

    Henceforth this warning remains to get thrown in various Admin UI pages!

    Solution

    1. Temporarily disable HTTP Basic Auth directives in my .htaccess.
    2. Go to Media Deduper’s main UI at: WordPress → Media → Manage Duplicates
      wp-admin/upload.php?page=media-deduper&tab=index
    3. Index of Duplicate Media → Clicking “Index Media”.
      ? Remains stuck at 0% although HTTP Auth is off, so the server is reachable from the outside freely.
    4. Then also disabling plugin wp-cron-http-auth.
      ?? Because if this is active, Media Deduper seems to assume that HTTP Auth is ON too. Whether really or not it does not check on its own anymore then, it seems. This way I send a strong signal to Media Deduper “Hey, there’s really no more HTTP Auth anymore. Try again”
    5. Returning to: WordPress → Media → Manage Duplicates
      ? Media is already indexed.
      ? Clicking Re-Index to be sure. Works fine too.
    6. Going to another Admin UI page (e.g. “Plugins” or “Media”).
      ? Now finally that warning is gone!
    7. Now trying to re-enable HTTP Auth. The order seems to matter:
      a) Re-activated the already configured wp-cron-http-auth
      b) Re-enabled HTTP Auth directives in .htaccess
    8. All works fine now:
      a) WordPress → Media → Manage Duplicates: ? Re-indexing works.
      b) WordPress → Media: Upload duplicate: ? Dupe upload intercepted, warning thrown.

    Followup:

    1. Maybe you can make your heuristics more stable to detect an existing HTTP Auth or its de-activation more reliably.
    2. If that’s not possible, please update your documentation with this my findings. The order of the procedure seems to make a difference.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter abitofmind

    (@abitofmind)

    Sadly a few days later this warning message re-surfaced.

    Thread Starter abitofmind

    (@abitofmind)

    But it think it is a “false positive” warning message for these reasons:

    1. I can re-index the media.
    2. And when uploading a new file, and then that same file again the dupe detection kicks in. Which means that the indexing of valid new files still works.

    So all in all WP-cron seems to be accessible to Media Deduper through the wp-cron-http-auth plugin.

    • Then why this error message?
    • It is somehow annoying as it takes the upper part of every media related activity in WordPress.
    • This reply was modified 1 year, 6 months ago by abitofmind.
    Thread Starter abitofmind

    (@abitofmind)

    On the other side I have some doubts whether wp-cron-http-auth works as it should because WordPress → Site Health Info → Shows 3 infos which indicate that the loopback may not work as it should:

    • A scheduled event has failed
    • The REST API encountered an unexpected result
    • The authorization header is invalid

    Therefore I also contacted wp-cron-http-auth ‘s developer on their contact form as provided in the plugin FAQs.

    A reaction would be appreciated! Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Warning message remains although plugin wp-cron-http-auth up & running’ is closed to new replies.