Forum Replies Created

Viewing 15 replies - 31 through 45 (of 2,075 total)
  • Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @cardozoadvocacia

    Thanks for reaching out, and I’m sorry you’re having trouble connecting your social media accounts.

    We took a closer look and can see that Jetpack isn’t fully connected to your site at the moment. Specifically, we’re seeing a 405 Not Allowed error when trying to access your site’s xmlrpc.php file. Jetpack uses that file to communicate with your site—so when it’s blocked or misconfigured, features like social media connections and the activity log won’t work properly.

    To fix this, we recommend reaching out to your hosting provider and asking them to:

    • Ensure that the xmlrpc.php file is accessible and can accept POST requests.
    • Confirm that nothing on the server (like a firewall or security plugin) is blocking Jetpack’s requests.

    Once that’s resolved, Jetpack should be able to reconnect fully and social sharing should start working again.

    Let us know if you’d like help checking the connection after your host makes the update—we’re happy to assist!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @hajtak,

    Thank you for confirming that removing the wp_jp_foreign_id field restored your posts in the app—glad to hear that part is resolved!

    As for the display issues you’re still seeing (such as “Classic – nicht unterstützt” or block errors), you’re absolutely right that this likely stems from the Classic Editor plugin. The mobile app has limited support for classic blocks and may display warnings or fallback UI for content created with older editors or unsupported block formats.

    You have a few options here:

    • If possible, try editing those posts in the block editor to convert legacy content to supported blocks.
    • Alternatively, view and manage those posts via the web version of WP Admin for a more consistent editing experience.
    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @odenwar

    Can you reach out to us via this contact form:

    https://jetpack.com/contact-support/?rel=support&hpi=1

    In your message, please include a link to this thread.

    Thanks!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @pistoscomputers

    Thanks for reaching out!

    Jetpack Boost sometimes struggles to generate Critical CSS for dynamic content like Beaver Builder templates. Even if those files aren’t truly “critical,” Boost may flag them if it can’t access or analyze them properly.

    If the page looks fine and loads normally, you can safely ignore the warning — Boost will simply skip Critical CSS for those templates and continue optimizing other parts of your site.

    Let us know if you’d like help reviewing anything further!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @tatsuyaokuwaki

    Thanks for reaching out — I understand you’re trying to access your Jetpack-connected site, but the verification code is going to a non-existent .local email address that was used during local development. That’s definitely a tricky situation, but I’d be happy to help get things sorted.

    I looked into the site, and I’m seeing that Jetpack is actually connected to a Gmail address. To make sure we’re on the right track, could you please confirm whether you have access to that Gmail address?

    If not, or if you’re unsure what that address is, just let me know — we can walk you through how to regain access from there.

    Looking forward to your reply so we can get this resolved!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Glad to hear you got back in!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @taftaff

    Thanks for reaching out, and good call sharing your custom login link!

    The message you’re seeing is from Jetpack’s Brute Force Protection. It blocked the IP (109.234.160.132) because it was flagged for suspicious activity—possibly from failed login attempts on another site.

    To regain access:

    1. Enter your email on the blocked page.
    2. Check your inbox for the unlock link.
    3. Click the link to unblock your login.

    If that doesn’t work, you can either allowlist your IP or temporarily disable Brute Force Protection via your WordPress.com Security settings.

    More help here:
    Brute force protection guide
    Troubleshooting steps

    Let us know if you need a hand with any of that!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @niveshaknews

    Thanks for reaching out, and I can see why this is confusing — let’s get this sorted.

    You mentioned that you recently received confirmation that your site was reclassified as non-commercial, and you followed the re-verification steps at wordpress.com/stats/purchase. However, your Jetpack Stats still reflect a commercial classification.

    I took a quick look at your site, and I noticed that the Contact page references advertising, brand collaborations, and guest post opportunities. These activities typically qualify a site as commercial under our current guidelines.

    That said, if you previously contacted our team and were told the site qualifies as non-commercial, it’s possible there’s a mismatch in how the classification was applied. Can you share where or how you received that confirmation? With that, I’d be happy to investigate further.

    Let us know — we’re here to help!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @alavecchia64

    Thanks for reaching out! I understand you’re trying to make your site publicly visible again after restoring it to a backup from before your Business plan expired, and you’re seeing a login screen even though your settings are set to public visibility.

    I just checked your site and can confirm it’s currently visible to the public. I tested it across Chrome, Safari, and Firefox, using both regular and private/incognito windows, and wasn’t prompted to log in.

    Since everything looks good from here, it’s possible the issue is related to local caching or a temporary configuration. Here are a few things you can try:

    • Clear your browser cache or check your site in a private/incognito window.
    • Disable any maintenance mode or coming soon plugin, if active.
    • Review your privacy settings under Settings → Reading to confirm “Discourage search engines” is unchecked (this doesn’t restrict access, but can be confusing).
    • Check with your host or security plugin to see if there are any IP-based restrictions enabled.

    Let us know if the issue persists on your end or if others are still seeing a login prompt—we’re happy to help further!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi there,

    Thanks for sharing those details — I understand you’re trying to track down the source of a recent Jetpack charge and cancel or refund it if it’s not something you actively signed up for.

    I looked up the payment ID you shared (L1DPCT5X3R), and I found that the charge on May 2nd for 88,27€ was for a Jetpack Personal plan tied to the site webenfamille.com.

    Since the site is no longer active, I’ve gone ahead and canceled the subscription and issued a full refund for you. The refund should appear on your original payment method within 5–10 business days.

    Let me know if you have any other questions or if you’d like help with anything else — happy to assist!

    All the best,

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @richbhanover

    That SecurityError: Permission denied message is a common browser console warning and isn’t harmful. It usually happens when scripts from different domains interact — in Jetpack’s case, often related to stats or other features loading from WordPress.com.

    Your Jetpack connection looks great, and everything should be working as expected. That said, the error shouldn’t interfere with site performance or functionality. If you’re seeing broken functionality alongside this error (e.g., Stats not loading), please let us know and we can investigate further.

    Let us know if anything’s not working right!

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @orrynemrys

    Could you contact us via this contact form and mention this thread?

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @odeeart

    I have confirmed that your website is for non-commercial use only and therefore qualifies for our Free Stats plan. I have adjusted this in our records. You should be able to view your stats now; please let us know if you do not see them.

    Let us know if you have other questions or if there’s anything else we can do to help! 

    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @ndhags

    Thanks so much for reaching out! I completely understand where you’re coming from — it can definitely feel a little confusing when your site isn’t aiming to make a profit in the traditional sense.

    I had a look at the site and because there are options for memberships and donations listed, it does fall under Jetpack’s definition of a commercial site. (You can see more about that here​.) Even when it’s a volunteer-driven or nonprofit effort, collecting any kind of payment unfortunately means the site needs a paid Stats plan.

    That said — if you ever remove the membership and donation information, absolutely let us know! We’ll be happy to take another look and help update your site’s status if it meets the non-commercial guidelines at that point.

    I know this might not be the news you were hoping for, but I’m glad you reached out. Please feel free to reply back if you have any other questions — we’re here to help!

    Thanks again for being part of the Jetpack community!

    • This reply was modified 11 months, 1 week ago by Bruce (a11n).
    Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    Hi @davidplusworld,

    Thanks for the feedback — I totally understand how that felt abrupt. It sounds like your site may now require a commercial plan just for Jetpack Stats. All other features you’re using should remain available.

    If you’d like us to double-check or clarify anything, feel free to reach out via this contact form and mention this thread.

Viewing 15 replies - 31 through 45 (of 2,075 total)