• Resolved dawgscurvy

    (@dawgscurvy)


    Over the last few weeks, 9/10 attempts to save a post (manually or using autosave) fails, with the page stuck saving with the button greyed out.
    I have spent countless hours re-doing work. After some troubleshooting, the problem seems to be with Jetpack

    1. If I disable all plugins, the problem disappears
    2. If I enable Jetpack as the only plugin, the problem appears
    3. If I don’t sign in to Jetpack, the problem doesn’t appear
    4. The problem doesn’t disappear if I pause Cloudflare globally for my site (wp-admin) is excluded using a rule, anyways
    5. No problem with viewing my site pages, only saving posts in editor
    6. The “Health Check & Troubleshooting” plugin finds nothing wrong

    I use very few Jetpack features, login for comments, sharing to social media and newsletters. CDN etc are all disabled.

    What can I do to find out what is wrong and consequently fix this?

    PS: My hosting provider (Hostinger) reports that CPU, Memory, Processes, PHP workers are all below 10%. Caching is disabled.

    • This topic was modified 1 year, 2 months ago by dawgscurvy.
    • This topic was modified 1 year, 2 months ago by dawgscurvy. Reason: Added more details

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

Viewing 15 replies - 1 through 15 (of 17 total)
  • Thread Starter dawgscurvy

    (@dawgscurvy)

    I did some more troubleshooting and found the “modules” page for Jetpack. The funny part is, even if I disable every single module, the problem is still there. In fact the problem is connected to my WordPress account being signed in to Jetpack. Also, I think it is related to it syncing my post to Jetpack cloud, because for the times it is stuck saving, the logs on Jetpack cloud don’t show changes being saved.

    Thread Starter dawgscurvy

    (@dawgscurvy)

    It seems that whenever I save a post on my blog, the Jetpack plugin tries to sync the post up to Jetpack cloud, but sometimes fails.
    Further, it seems the bigger a post is, more the chances of it getting stuck saving.

    Thread Starter dawgscurvy

    (@dawgscurvy)

    I upgraded the PHP memory limit to 512M, no joy.

    Thread Starter dawgscurvy

    (@dawgscurvy)

    Looks like a compatibility problem between Safari and Jetpack

    1. Windows 11 with edge – 100 saves, no problem
    2. Safari on iPhone/iPad/Mac – 4-5/10 saves fail

    Can this issue be addressed? I am running the latest safari on all my iDevices.

    Thread Starter dawgscurvy

    (@dawgscurvy)

    Deleting the “website data” for my blog from all my devices seems to have solved the issue.

    Thread Starter dawgscurvy

    (@dawgscurvy)

    The problem reappeared after a day. Can I have some support, please?

    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @dawgscurvy,

    You’ve done a really impressive job narrowing this down — thanks for all the detailed troubleshooting so far. That gives us a clear head start.

    I tried to reproduce the issue in Safari on MacOS, with Jetpack connected, but I wasn’t able to trigger the problem — post saves worked normally, even with longer content.

    Since the issue came back for you after clearing website data, the next thing that might help is checking the browser console in Safari the next time it happens. If any errors show up there, a screenshot could give us more to work with and help pinpoint what’s going wrong during the save.

    Let me know what you see — I’m happy to keep looking into this with you.

    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @dawgscurvy,

    You’ve done a really impressive job narrowing this down — thanks for all the detailed troubleshooting so far. That gives us a clear head start.

    I tried to reproduce the issue in Safari on MacOS with Jetpack connected, but I wasn’t able to trigger the problem — post saves worked normally, even with longer content.

    Since the issue came back for you after clearing website data, the next thing that might help is checking the browser console in Safari the next time it happens. If any errors show up there, a screenshot could give us more to work with and help pinpoint what’s going wrong during the save.

    Let me know what you see — I’m happy to keep looking into this with you.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @dawgscurvy,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

    Thread Starter dawgscurvy

    (@dawgscurvy)

    Hello. Apologies, I didn’t get a notification for your comment. I don’t have access to a Mac anymore, so I cannot test this again.
    I do have an iPad which I mostly blog on, and I can still recreate the problem on it, on iPadOS 18.4.1. Unfortunately, safari on iPadOS doesn’t have much in the way of logs or troubleshooting.
    There’re no errors. It just gets stuck in “saving”.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @dawgscurvy,

    Thanks for the follow-up. When you recreate the problem on your iPad, what browser do you use? Can you try using a different browser, such as Chrome or FireFox?

    If the posts get stuck while saving, it’s possible that your hosting provider can find some info we can use as a clue to understand what’s happening, since we cannot replicate it at our end. You can ask to share the PHP error logs, and maybe we can find a good clue.

    If you have this info to share, it’d be better if you reach out via email so to not share sensitive info; please use this contact form and mention this thread. Thanks!

    Thread Starter dawgscurvy

    (@dawgscurvy)

    hello. The problem occurs in Safari. On Firefox, there are no issues.
    what kind of information should I ask from my hosting provider?

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @dawgscurvy,

    This is progress – if the issue happens on Safari only, we have at least pinpointed one root of the problem. While we address this issue, I recommend using Firefox as a workaround in the meantime.

    You can gather the following info that can be useful from your host:

    • Apache/Nginx error logs or any relevant logs that coincide with the time you try to save a post in Safari. Specify the time and date you tried to save, and the exact URL or post ID if possible.
    • Check if there are any PHP errors or warnings during post saving, especially when Safari is used.
    • Ask if server-level caching (e.g., Varnish, LiteSpeed Cache) is active and if it’s known to behave differently based on user agent (i.e., Safari vs. Firefox)

    Other information you can collect by yourself that can help us address the problem:

    • Browser console logs from Safari: look for any JavaScript errors or failed network requests when saving a post.
    • Safari version and macOS version, as sometimes bugs are specific to a version combo.

    Hope that’s all clear and helps 🙂

    Thread Starter dawgscurvy

    (@dawgscurvy)

    1. Web server logs – cannot be provided for shared hosting
    2. PHP logs – I just enabled PHP logging and reproduced the problem and noted the time. There’s a 2 day delay in the logs being available to me, I will fetch the correct logs in 2 days time
    3. Server level caching is enabled on Cloudflare, but, it is excluded for /wp-admin and I can also see the problem disabling Cloudflare globally for my website
    4. Browser console logs – The issue happens only on safari on iOS and iPadOS, there are no logs for these platform
    5. Safari/iOS/iPadOS version – 18.4.1

    PS: I see many Jetpack errors in my logs already, but since they are historical, I can’t match the timestamps to my specific issue.

    Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hi again,

    The issue happens only on safari on iOS and iPadOS, there are no logs for these platform

    If the problem only happens on iOS and iPadOS in mobile Safari then the browser logs may be most relevant.

    You can access those logs by connecting your device to a Mac using a cable. Do you have a Mac?

    If so, here is how to proceed (the same method applies for an iPhone):

    • On your iPad, go to Settings > Safari > Advanced and enable Web Inspector.
    • Connect your iPad to your Mac using a cable.
    • On your Mac, open Safari, then go to Safari > Preferences > Advanced and check Show Develop menu in menu bar.
    • With your iPad connected and Safari open on both devices, open the website you want to debug on your iPad.
    • In the Mac’s Safari menu bar, select Develop > [Your iPad Name] > [Page Title]. This opens the Web Inspector for the page running on your iPad.
    • Select the Console tab in Web Inspector to view logs in real time. Note: Console logs only appear if Web Inspector is open at the time the log is generated, so keep it open while reproducing issues.

    Would you be open to further testing this way? Please let us know how it goes?

    Thank you!

Viewing 15 replies - 1 through 15 (of 17 total)

The topic ‘Jetpack breaking post save’ is closed to new replies.