critical issue

  • cjthedaddy

    (@cjthedaddy)


    1 day, 8 hours ago

    I came across a ‘critical issue’ on my site:

    “Could not reach ww.wp.xz.cn”

    The site still works fine though, although I’m having difficulty backing up on updraft plus

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator bcworkz

    (@bcworkz)

    1 day, 7 hours ago

    “Cannot reach WordPress” errors are usually temporary in nature. If the issue persists, some sort of security measures on your hosting end may be interfering. If you have any security plugins, try deactivating it to see if it resolves the issue. If so, contact the plugin developer for a more permanent fix. It could also be some kind of security measure implemented by your host, such as firewall or modSecurty. Contact your host for assistance in resolving such problems.

    Updraft AFAIK doesn’t contact ww.wp.xz.cn in order to do a backup. Backup issues also indicate security measures are interfering, assuming the connection to the backup resource was working previously.

    techy223

    (@techy223)

    20 hours, 6 minutes ago

    This usually happens due to a server or firewall issue blocking connection to ww.wp.xz.cn. Try disabling security plugins temporarily, checking with your hosting provider, and ensuring no firewall rules are blocking outgoing requests. You can also try changing DNS settings and running a Site Health check in WordPress.

    Thread Starter cjthedaddy

    (@cjthedaddy)

    17 hours, 39 minutes ago

    Thanks, but I am not technical and am struggling with all this. I’ve never really managed my website (other than updating the content) and don’t know what it involves. Maybe I need to outsource that to someone who knows what they are doing. But first I’d like to back it up myself – that’s not working on updraft plus – It just pauses indefinitely because of unspecified errors.

    Thread Starter cjthedaddy

    (@cjthedaddy)

    13 hours, 41 minutes ago

    Apologies in advance for pasting AI text here – this is the advice AI gave me to backup my site, however I’m nervous to blindly follow these instructions and make these sorts of changes….. Any thoughts?

    A 2 GB site attempting to push to Dropbox is precisely why UpdraftPlus is stalling. [1, 2]

    When a site reaches this size, UpdraftPlus bundles files into temporary .zip chunks on your local server before pushing them over an API handshake to Dropbox. If a single file chunk is too heavy, MilesWeb will violently kill the processing engine after a few minutes to protect shared server resources. Because the process is killed at the server level, UpdraftPlus loses its place and never triggers the automated resume sequence. [2, 3, 4, 5, 6, 7]

    Since your cPanel allocation is set to unlimited (∞), you have the folder storage room, but you lack the continuous processing runtime. Use these steps to bypass this issue: [2] Step 1: Force a Server Timeout Extension

    Your server is killing the script after a few minutes because it hits a maximum execution cap. You can force your server to give UpdraftPlus more time: [5, 8, 9]

    1. Log into your MilesWeb cPanel and open File Manager.
    2. Go to the public_html directory, click on your wp-config.php file, and choose Edit.
    3. Paste the following time limit parameter directly under your memory limit line:set_time_limit(600); (This expands your server execution window to 10 minutes per task chunk, giving the Dropbox upload time to clear). [8, 9]

    Step 2: Drop the Split Size to 25 MB

    Your server cannot handle processing massive zip bundles down the API pipeline all at once. Forcing tiny bundles reduces server strain to near zero: [1, 4]

    1. In your WordPress dashboard, navigate to Settings > UpdraftPlus Backups.
    2. Open the Settings tab and select Show expert settings.
    3. Change Split archives every from its current setting down to 25 MB.
    4. Click Save Changes at the base of the page.
      (Instead of choking on massive blocks of data, UpdraftPlus will seamlessly pass dozens of small 25 MB packages directly into your Dropbox app directory). [5, 8]

    Step 3: Delete Broken Leftover Temporary Dumps

    Failed and paused runs drop corrupted, partial .tmp and .zip archives directly into your server folders. These ghost files will choke out your fresh attempts: [3]

    1. Go back to your cPanel File Manager.
    2. Open public_html/wp-content/updraft.
    3. Highlight and Delete any files ending with .tmp or any standalone .zip files from your failed attempts. Leave the index files alone.

    Step 4: Split Up Your Manual Executions

    Do not run everything simultaneously. Run your database and files as separate actions to isolate server weight: [7]

    1. On the main UpdraftPlus backup screen, click Backup Now.
    2. Uncheck Include your files in the backup (Leave only the Database selected).
    3. Run the backup. Your database should complete in seconds and transfer straight to Dropbox.
    4. Once completed, click Backup Now again. Uncheck the database, check Include your files, and let the small 25 MB zipping configurations process your media libraries autonomously. [5, 7]

    If the backup continues to hang after adjusting these options, let me know:

    • What are the very last 3 lines of text written inside the UpdraftPlus backup log?
    • Do you see a yellow warning banner at the top of your dashboard explicitly stating that your WordPress Cron (Scheduler) is disabled?

    [6, 10]

    [1] https://easyupdatesmanager.com

    [2] https://ww.wp.xz.cn

    [3] https://www.reddit.com

    [4] https://www.experts-exchange.com

    [5] https://ww.wp.xz.cn

    [6] https://ww.wp.xz.cn

    [7] https://uk.ww.wp.xz.cn

    [8] https://teamupdraft.com

    [9] https://easyupdatesmanager.com

    [10] https://teamupdraft.com

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

You must be logged in to reply to this topic.