Viewing 15 replies - 1 through 15 (of 29 total)
  • Plugin Contributor James Huff

    (@macmanx)

    Your site doesn’t appear to be properly connected with Jetpack, so let’s try that first.

    Please try disconnecting Jetpack from WordPress.com at Jetpack > Dashboard > Site Connection > Manage Site Connection in your site’s Dashboard, then connect again when prompted.

    If anything, that process will either fix it, or give us a better error to go off of.

    Thread Starter mattdrown

    (@mattdrown)

    You can look at https://2ontherun.com/ or https://neeleydrown.com/ same error.

    Manage Site Connection tells me that I’m connected. But I disconnected, and reconnected. And re-tested, same issue.

    Thread Starter mattdrown

    (@mattdrown)

    I notice that Jetpacks “free” support is “temporarily” down when I went to file a bug about this. Is that something that is normal, or should I expect to be able to file something about this in the near future?

    I’ve also now tried deleting and re-installing the plugin with no change in behavior (other than having to reconfigure the jetpack setup).

    Plugin Contributor James Huff

    (@macmanx)

    According to tests from our end, the other two sites are working just fine.

    Is your server running mod_security? If so, do you have control over switching it on/off? And, if so, would you please check with it switched off?

    Support for our free customers is temporarily down while we work through an unusual backlog, but we’re still active here for now, at least once each weekday.

    Thread Starter mattdrown

    (@mattdrown)

    I just re-tested everything, and I may have found the issue with the mix of nextgen-gallery and jetpack. I had tested no plugins but jetpack and could reproduce, but I don’t appear to be able to reproduce right now. I will update if this changes.

    The other issues of jetpack reporting an error on connection, I have no idea. I’ve gone through the process a couple different times, including deleting and re-installing jetpack, and clearing out the jetpack connections. It never reports a proper connection (including with all plugins deactivated). The debugging page seems to imply that I pass all the tests except #9, as below. 0-8 report “test passed”.

    [9] => Array
    (
    [name] => test__wpcom_self_test
    [pass] =>
    [message] => Jetpack.com detected an error.
    [resolution] => Visit the Jetpack.com debugging page for more information or contact support.
    [group] => Array
    (
    [0] => default
    )

    )

    Thread Starter mattdrown

    (@mattdrown)

    Quick update, the 403 error doesn’t occur if jetpack is installed, but not connected.

    • This reply was modified 7 years, 5 months ago by mattdrown.
    Plugin Support lizkarkoski

    (@lizkarkoski)

    Good morning 🙂

    Thanks for the update. Are you able to reconnect Jetpack to https://mattdrown.com so that we can continue to trouble shoot what’s going on? At the moment the site is not connected to Jetpack.

    It sounds like you’re seeing the xml-rpc error in the debugger. Is that right?

    ——–update———

    Do things work any better if you try a manual installation of Jetpack? Or is this what you’ve been using? https://codex.wordpress.org/Managing_Plugins/

    • This reply was modified 7 years, 5 months ago by lizkarkoski.
    Thread Starter mattdrown

    (@mattdrown)

    Jetpack debugging page reports I’m connected on mattdrown.com:

    mattdrown.com…/wordpress/wp-admin/admin.php?page=jetpack-debugger
    Debugging Center
    Testing your site’s compatibility with Jetpack…
    Your Jetpack setup looks a-okay!

    The 2ontherun.com site reports “test__wpcom_self_test” fail, with no other information.

    Both show up on wordpress.com stats, including information about today.

    Plugin Support lizkarkoski

    (@lizkarkoski)

    Here’s what I see now for mattdrown.com:

    It looks like XML-RPC is not responding correctly. Please make sure XML-RPC is turned on for your site and is set up to respond to all content types. You can test this yourself by running the following command from the command line:

    curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' http://mattdrown.com/xmlrpc.php

    The answer should be:

    <?xml version="1.0" encoding="UTF-8"?>
    <methodResponse>
      <params>
        <param>
          <value>
          <string>Hello!</string>
          </value>
        </param>
      </params>
    </methodResponse>

    Check out #4 on this page to fix that: https://jetpack.com/support/getting-started-with-jetpack/troubleshooting-tips/

    Thread Starter mattdrown

    (@mattdrown)

    If you switch to HTTPS that responds correctly, AND go to the correct directory which is /wordpress/xmlrpc.php, since wordpress is located, not at the top level. Is that the problem?

    https://mattdrown.com/xmlrpc.php = does not work
    https://mattdrown.com/wordpress/xmlrpc.php = works

    I have wordpress in the /wordpress folder, do I need to redirect /xmlrpc.php to /wordpress/xmlrpc.php?

    Plugin Contributor James Huff

    (@macmanx)

    Please try disconnecting Jetpack from WordPress.com at Jetpack > Dashboard > Site Connection > Manage Site Connection in your site’s Dashboard, then connect again when prompted.

    This should correct the URL on our end.

    Thread Starter mattdrown

    (@mattdrown)

    mattdrown.com is connected
    2ontherun.com is not connected

    both are in the /wordpress directory

    I have disconnected and reconnected both.

    
    # curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' https://2ontherun.com/wordpress/xmlrpc.php
    <?xml version="1.0" encoding="UTF-8"?>
    <methodResponse>
      <params>
        <param>
          <value>
          <string>Hello!</string>
          </value>
        </param>
      </params>
    </methodResponse>
    

    I also just disabled all plugins except jetpack, and then disconnected/reconnected, and am still getting the selftest error above.

    • This reply was modified 7 years, 5 months ago by mattdrown.
    • This reply was modified 7 years, 5 months ago by mattdrown.
    Plugin Contributor James Huff

    (@macmanx)

    That is very odd, everything does look correct on our end now, but I guess it didn’t address the problem.

    Do you see anything in your server error log at the time the draft failed?

    I’m suspecting maybe a server-based security measure is blocking it.

    Thread Starter mattdrown

    (@mattdrown)

    No server side errors, no mod_security, no error logs for apache, access logs look like this when i go to the jetpack debugging page (tokens and nonce removed):

    
     - - [12/Mar/2019:14:55:29 -0700] "POST /wordpress/xmlrpc.php?for=jetpack&token=xxxxxxxxxxxxxxxxxx&timestamp=1552427729&nonce=xxxxxx&body-hash=xxxxxxxxxxxD&signature=xxxxxxxxxxxxxxxxxxxxx HTTP/1.1" 200 131
     - - [12/Mar/2019:14:55:32 -0700] "GET /wordpress/xmlrpc.php HTTP/1.1" 405 42
     - - [12/Mar/2019:14:55:28 -0700] "GET /wordpress/wp-admin/admin.php?page=jetpack-debugger HTTP/1.1" 200 21397
     - - [12/Mar/2019:14:55:33 -0700] "GET /wordpress/wp-admin/admin-ajax.php?action=atd_settings&ver=20150715 HTTP/1.1" 200 236
     - - [12/Mar/2019:14:55:36 -0700] "GET /wp-json/jetpack/v4/jitm?message_path=wp%3Aadmin_page_jetpack-debugger%3Aadmin_notices&query=page%253Djetpack-debugger&_wpnonce=xxxxx HTTP/1.1" 200 2
    
    • This reply was modified 7 years, 5 months ago by mattdrown.
    • This reply was modified 7 years, 5 months ago by mattdrown.
    Plugin Contributor James Huff

    (@macmanx)

    “GET /wordpress/xmlrpc.php HTTP/1.1” 405

    Ok, so something _is_ blocking us, maybe just for that one action.

    Are you running any security plugins? If so, would you please try with those deactivated?

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

The topic ‘Save Draft causing hang and 403 with Gutenberg’ is closed to new replies.