A plugin has prevented updates by disabling wp_version_check()

  • Hello ??

    I’m gonna try to give as much detail as I can ! And sorry if it is not the right forum btw.

    WordPress 5.4

    I noticed 2 weeks ago the well known issue “A plugin has prevented updates by disabling wp_version_check()” given by the Site Health checker.
    Little precision, I’m using a custom theme.
    I’ve seen that issue a lot on forums, so here is what I’ve tried so far :

    • I’ve seen the issue on my hosted website
    • Tried to reproduce the issue locally on my Windows10-WAMP hosted website, I’ve actually the same issue. All next steps have been made both locally and in my online wordpress…
    • I disabled all my plugins, one by one, to check if there was a change. Nothing.
    • Tried to enable another theme, not homemade this time -> no change
    • Tried to delete my custom functions.php file, and even deleting the whole theme. Nothing
    • Tried to install the Health Check & Troubleshooting plugin, and test all possibilities, no change
    • Checked my wp-config.php to verify anything suspect (haven’t edit it for like 1 year so…)
    • Looked for a .htaccess rule which could cause the issue -> nothing
    • I’ve read a lot of issues kind of similar, but nothing really helps me.

    I’m looking for new line of thought because I’m working on this for a week ??

    Thank you !
    Take care !

    • This topic was modified 4 years, 7 months ago by eiaaie.
    • This topic was modified 4 years, 7 months ago by eiaaie.
    • This topic was modified 4 years, 7 months ago by eiaaie.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz

    (@bcworkz)

    AFAIK, that message is a bit of a “red herring” (misleading). More accurate would be “WP cannot communicate with the update server”. This is often caused by the version check function being disabled, but you’ve likely ruled that out by disabling plugins and changing themes. It’s possible such disabling code had wrongly been added to a core WP file, but generally the cause at this point is something about the server configuration.

    There are many reasons a server might have trouble communicating. It’s typically outside of WP itself, which is why there are so many unresolved topics about this in the forums. Tracking down the root cause requires server access which is outside of the scope of these forums. All I can tell you is that communication to api.www.ads-software.com is failing for some reason.

    Thread Starter eiaaie

    (@eiaaie)

    Hello @bcworkz
    First of all, thank you for the answser.

    Your last sentence is interesting, because I noticed as well another error (not critical though), concerning an unexpected result from REST API :

    Not Found

    The requested URL /wp-json/wp/v2/types/post was not found on this server.

    If I find a solution, I’ll post it here anyways

    Moderator bcworkz

    (@bcworkz)

    Yeah, /wp-json/wp/v2/ requests are still external requests even though the server is calling itself. You should also be seeing a “could not complete a loopback request” error in WP site health. All related to the same problem.

    Here’s a shot in the dark towards finding a solution: In verifying what the loopback message from WP normally is, I noticed a common reason for the error is some sort of allow/deny directive was added (usually in .htaccess) for better security. Your server’s own IP needs to be allowed so it can call itself.

    Thread Starter eiaaie

    (@eiaaie)

    I double checked, and I don’t have any issue concerning loopback though,
    only the one I mentionned earlier.

    For .htacess, I used W3T Cache plugin which add some custom rules in it.
    Even before adding this plugin, I had the error, and the only custom rule I had was :

    
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.my-site.fr/$1 [R,L]

    I tried another time by deleting these lines btw, same result.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘A plugin has prevented updates by disabling wp_version_check()’ is closed to new replies.