Jetpack Publicize error -32300

  • Resolved danpreston

    (@danpreston)


    10 years, 1 month ago

    Jetpack works fine in most respects on my site, but not when I try to connect the Publicize feature to Facebook, Twitter or any of the others. This is the result:

    Sharing Settings
    Something which should never happen, happened. Sorry about that. If you try again, maybe it will work.
    Error code: -32300
    Publicize

    This is my site: telequestinc.com
    The host is 1and1

    Here’s the output of the Jetpack Compatibility Test:

    Site info

    SITE_URL: https://telequestinc.com
    HOME_URL: https://telequestinc.com

    TEST: HTTP Connection
    Array
    (
    [headers] => Array
    (
    [server] => nginx
    [date] => Thu, 05 Feb 2015 18:23:12 GMT
    [content-type] => text/plain;charset=utf-8
    [connection] => close
    [vary] => Cookie
    [x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
    [expires] => Wed, 11 Jan 1984 05:00:00 GMT
    [cache-control] => no-cache, must-revalidate, max-age=60
    [pragma] => no-cache
    [x-hacker] => Jetpack Test
    )

    [body] => OK
    [response] => Array
    (
    [code] => 200
    [message] => OK
    )

    [cookies] => Array
    (
    )

    [filename] =>
    )

    TEST: HTTPS Connection
    Array
    (
    [headers] => Array
    (
    [server] => nginx
    [date] => Thu, 05 Feb 2015 18:23:13 GMT
    [content-type] => text/plain;charset=utf-8
    [connection] => close
    [vary] => Cookie
    [x-pingback] => https://jetpack.wordpress.com/xmlrpc.php
    [expires] => Wed, 11 Jan 1984 05:00:00 GMT
    [cache-control] => no-cache, must-revalidate, max-age=60
    [pragma] => no-cache
    [x-hacker] => Jetpack Test
    )

    [body] => OK
    [response] => Array
    (
    [code] => 200
    [message] => OK
    )

    [cookies] => Array
    (
    )

    [filename] =>
    )

    TEST: Self Connection
    Array
    (
    [headers] => Array
    (
    [date] => Thu, 05 Feb 2015 18:23:13 GMT
    [server] => Apache
    [x-powered-by] => PHP/5.5.20
    [connection] => close
    [content-type] => text/plain
    )

    [body] => XML-RPC server accepts POST requests only.
    [response] => Array
    (
    [code] => 200
    [message] => OK
    )

    [cookies] => Array
    (
    )

    [filename] =>
    )

    https://www.ads-software.com/plugins/jetpack/

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter danpreston

    (@danpreston)

    I’ve used the Jetpack debugger tool and it gives a green light, everything’s fine message.
    Also checked the XMLRPC file and that behaves correctly.
    Please let me know if there are any additional diagnostics I can do on this end. Looking forward to your help, it’ll be much appreciated.

    Plugin Contributor Adam Heckler

    (@adamkheckler)

    It seems like your XMLRPC.php file is not behaving correctly, or something is blocking it. It should be accessible at this URL as well:

    https://telequestinc.com/xmlrpc.php?for=jetpack

    … but as you can see, it returns a 403 error.

    Since your site returns an error for this page, I would recommend that you check the following:

    1) Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall WordPress” button.

    2) Do you use any security plugins that may block access to this file? If so, could you try to disable them?

    3) Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

    Thanks!

    Thread Starter danpreston

    (@danpreston)

    Thanks Adam. In answer to your steps above:
    1) xmlrpc.php is there at the root of the installation
    2) The only security plugin is Akismet which I assume would not be a problem. I tried disabling it anyway and no change in behavior (and have since re-enabled it).
    3) I have contacted 1and1 support to see if they block the file. I suspect that may be the case because last summer they blogged about xmlrpc.php security issues. Do you know if there is any current reason they might insist on disabling the file?

    Thread Starter danpreston

    (@danpreston)

    Hi again.
    I’ve continued to hunt for solutions to no avail.
    – some forum posts suggested changing line 29 in xmlrpc from ./wp-load to wp-load (no effect)
    – tried XML-RPC De Whitespacer plugin, no effect

    Here’s something curious:
    https://www.telequestinc.com/xmlrpc.php gives the expected response of “XML-RPC server accepts POST requests only.”
    But so does https://www.telequestinc.com/xmlrpc.php?for=whatever
    And so does https://www.telequestinc.com/xmlrpc.php?for=jetpac … or pretty much any string replacing “whatever” EXCEPT for https://www.telequestinc.com/xmlrpc.php?for=jetpack (or any string beginning with “jetpack”
    So there’s something very specific that’s blocking Jetpack, it would seem.

    Does that in any way narrow down the issue?
    BTW, still waiting for meaningful response from 1and1. Will keep on them. Thanks!
    FYI theme is a child theme of twentytwelve

    Thread Starter danpreston

    (@danpreston)

    Here’s the word back from my web host tech support:

    We have received an escalated case support regarding the Jetpack plugin not working correctly in the WordPress website “www.telequestinc.com”. Accessing the xmlrpc.php file directly (https://www.telequestinc.com/xmlrpc.php) will display the term “XML-RPC server accepts POST requests only”, which is part of ./wp-includes/class-IXR.php handled by WordPress itself. Instead the 403 error from (https://www.telequestinc.com/xmlrpc.php?for=jetpack) is indeed handled by 1&1 Apache mod_sec rule. The URL “xmlrpc.php\?for=jetpack” is strict protected by Apache mod_security to defend against malicious requests, and prevent brute Force Attacks. There have been many vulnerabilities and attacks in the past directed to the xmlrpc.php file with requests from sources not related to WordPress.com. The xmlrpc.php file can get updates and requests from WordPress IP addresses only, other external request are blocked by the rules set in Apache mod_sec. Based on the global rules set in our Linux shared hosting platform xmlrpc.php will run without any error in most case scenarios. Also Jetpack should run with most of the modules, however we cannot guarantee that some Jetpack modules will fully work since we cannot disable Apache mod_sec in our Shared Hosting Platform.

    Any suggestions beyond getting a new web host?

    Same issue, same host. I’ve deactivated all other plugins, still have 32300. Permissions on xlmrpc.php are 644. Haven’t heard from 1and1 support. WordPress support tech logged in and could link to twitter using publicize however I could not.

    Hey all,

    I’m working for 1&1 as their WordPress specialist. I’m just noticing this tread after being a few days off. We do indeed have security rules in place. We have done this in collaboration with the Jetpack team so unsure what goes wrong. That said, there was an update and I was not in the loop for that so I will check it out tomorrow first with our It department so see what is going wrong.

    I assume within 36 hours things are fixed. Sorry for this delay but since I’m based in Europe it’s already 9pm.

    Best,

    Marko

    Thread Starter danpreston

    (@danpreston)

    Hey Marko and Adam,
    It would be great if 1&1 and the Jetpack team could resolve this. I totally understand the need for security, but it sounds like you had this figured out in the past. Thanks for looking into this.
    Best,
    Dan

    Hey Dan,

    The issue has been resolved but still need to be deployed. This will happen in hour daily deploys which happens in the next 8 hours. I can only assume here since it’s not my department. During an update to prevent this for happening we missed a few IPs.

    I will check with our support to see what we can do to handle this cases faster. For now hopefully things are fixed by the morning.

    Best,
    Marko

    Thread Starter danpreston

    (@danpreston)

    Marko,
    Beautiful! I’ll give it a try tomorrow and report back.
    Looking forward to checking that “resolved” box!

    ha, me too ??

    Hi!

    I ‘m having this same problem . But I am unable to solve.
    I tried all of the above solutions.

    What should I do in xmlrpc.php file?

    Plugin Contributor Ryan C.

    (@ryancowles)

    @luanmiguel2015: We’ve replied to your comment here:
    https://www.ads-software.com/support/topic/cannot-publicize-error-32300-32301?replies=10

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Jetpack Publicize error -32300’ is closed to new replies.

Tags