• Resolved sicilybambolina

    (@sicilybambolina)


    My WordPress site (6.9.4) no longer detects updates – it doesn’t show that updates are available for either plugins or the core.

    When I try to update a plugin using WP Rollback, I get an error message. Whilst the steps ‘Enabling maintenance mode’, ‘Download requested version’ and ‘Creating version archive’ still run without a hitch, at ‘Validating package integrity’ I get the message ‘Error: Package not found for rollback’ and the previous version remains in place.

    Interestingly, installing new plugins works without any problems. Deactivating and removing plugins also works. An update via the workaround of deleting the plugin would therefore work, but if the update caused problems, a rollback would no longer be possible.

    As for the core, I tried to reinstall the current version via Dashboard > Updates, but this was unsuccessful. Nothing happened at all – not even an error message.

    I then tried to enable an update to the newer version using the ‘Rollback Core’ and ‘WP Downgrade’ plugins, but that also failed; there’s just a redirect to Dashboard > Updates without the option to update the core.

    Under “Site Health”, the only “Critical Issue” shown to me is that plugins and themes are not updated automatically, but this is an intended setting and has never previously resulted in available updates no longer being displayed.

    I’ve tried deactivating all plugins, clearing the cache and deleting the transients from the database but it didn’t help.

    Does anyone have any ideas?

    P.S.: Just in case it matters: uploading images or documents still works.
    P.P.S.: Strangely, another WordPress site of mine ([ redundant link deleted ], successfully updated to 6.9.5) still works perfectly with the same theme, plugins and settings.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator threadi

    (@threadi)

    If I understand correctly, does the message only appear when you’re installing updates (or downgrades) using WP Rollback? If so, I’d recommend checking out their support forum: https://wordpress.org/support/plugin/wp-rollback/

    Thread Starter sicilybambolina

    (@sicilybambolina)

    The website no longer detects any available updates at all.

    By now, the site should have detected and displayed a core update to 6.9.5 and the updates for a number of plugins.
    But it doesn’t.

    Just tried deleting WP Rollback but the problem persists.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    What happens if you do a manual update (to 7.0.2)?

    Thread Starter sicilybambolina

    (@sicilybambolina)

    Manually updated to 7.0.2.
    Problems persist… 🙁

    How can it be that new plugins are installed without a problem while updating is not?
    Especially with WR Rollback, when one version is to be replaced with another… Could it be an issue with permissions to directories that might have been changed accidentally by something without my active doing?

    Hi @sicilybambolina,

    Which hosting service are you using? Have you checked with the hosting service about this?

    Also, have you set up any firewalls, security plugins, or hosting restrictions?

    Please check whether you are seeing any errors in the Server Error Log or WordPress Debug Log.

    Hi @sicilybambolina,

    When WordPress stops checking for updates altogether and transients don’t help, it usually points to an outbound HTTP connection issue between your server and api.wordpress.org.

    Here are a few steps to diagnose and fix this:

    1. Check Site Health:
    • Go to Tools -> Site Health -> Status and check for any warnings related to HTTP Requests or cURL errors.
    1. Check Constants in wp-config.php:
    • Connect via FTP/File Manager and check your wp-config.php file.
    • Make sure neither of these lines are set to true:
      define( 'DISALLOW_FILE_MODS', true );
      define( 'AUTOMATIC_UPDATES_DISABLED', true );
    1. Server Firewall / cURL Certificate:
    • Contact your web host support and ask them to verify if outbound port 443 connections to api.wordpress.org are being blocked by a firewall, or if the server’s OpenSSL CA certificate bundle needs updating.

    Let me know what Site Health reports under HTTP requests!

    Thread Starter sicilybambolina

    (@sicilybambolina)

    Hi,

    I found that one of the plugins contained a malicious file. In the end, I decided to reinstall the entire site from scratch (thank goodness for backups), which finally sorted out the problem.

    Thank you all very much for your efforts. 🙂

    Hi @sicilybambolina,

    Glad to know you are getting the expected results now. Is it because of a customized plugin or because you are using an older version of the plugin (the one that causes the bug)?

    Thread Starter sicilybambolina

    (@sicilybambolina)

    It was a plugin named “Advanced Cache” (of which I can’t remember ever having installed it myself).

    I was going to try something by uploading my entire “wp-content” to another server when I received an error message from my provider that identified the malicious file as part of “Advanced Cache”.

    When simply deleting that plugin wouldn’t solve the issue, I knew I would reinstall my website completely.

    Moderator threadi

    (@threadi)

    That sounds very much like your project has been hacked. A name like “Advanced Cache” is unusually generic, and there is no plugin with that name in the repository: https://wordpress.org/plugins/search/Advanced%2520Cache/

    My recommendation: first read this article:

    FAQ My site was hacked

    After that I would recommend checking whether you still have a clean backup. If necessary, ask the support of your hoster. If so, delete all files and the database and restore the backup. Then change all access data in the hosting (also FTP, hosting login ..).

    So if you still have a clean backup of your website, use that.

Viewing 10 replies - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.