Jetpack Won’t Connect To WordPress.com

  • Resolved sterumbelow

    (@sterumbelow)


    7 years, 3 months ago

    Hi all,

    In desperate need of some help, as I’ve completely run out of ideas and search power!

    I’ve been running Jetpack without issue for five years, but recently had to restore my VPS and have had problems ever since. It asked me to disconnect and reconnect. Only, after disconnecting, I can no longer reconnect.

    Hitting the connect button results in a long wait, before a page saying there were too many redirects.

    What I’ve tried:

    1. Checked permissions on files. After the restore, some were apache owned and couldn’t be modified. After figuring out command line access, I managed to change that. No issues there anymore.

    2. XML-RPC file accesses just fine, following the URL.

    3. Can’t see anything being blocked by the server firewall. Have whitelisted some IP’s with no affect.

    4. Have disabled each plugin one-by-one, trying to connect after each deactivation. No change.

    5. Disabled primary theme. No effect.

    6. Checked URL’s in General settings, and WP-Config. Everything aligns perfectly – also the same in the database.

    7. Tried a manual Jetpack install.

    8. Checked the php.ini file, which seems to be set ok. Any adjustments had no effect.

    9. Checked SSL certificate. Now, I’ve no idea if there used to be one, or not. But my FTP has said certificate expired for absolutely ages now. From what I’ve read, Jetpack doesn’t need one anyway. However, running it through an SSL checker, returns an F-grade result.

    10. Have upgraded to PHP 7.0. From a very outdated 5.3.

    11. There is nothing in the .htaccess file to suggest anything would be blocked. I’ve also tried it without the .htaccess file, with no change.

    What do I see?

    On Jetpack Debug, it shows:

    It looks like your site cannot communicate properly with Jetpack. As well as a list of reasons it might happen – as above, I’ve tried them all with no change.

    It also shows:

    USER_TOKEN: [this user has no token]

    HTTP: PASS
HTTPS: PASS
IDENTITY_CRISIS: PASS
SELF: FAIL
    [body] => {"error":"Could not validate security token","error_description":"We were unable to validate a security token for Jetpack communication. Please try disconnecting Jetpack from your WordPress.com account, and connecting it again."}
    [response] => Array
        (
            [code] => 400
            [message] => Bad Request
    {"error":"Could not validate security token","error_description":"We were unable to validate a security token for Jetpack communication. Please try disconnecting Jetpack from your WordPress.com account, and connecting it again."}
                    [headers] => Requests_Response_Headers Object

    Happy to post the full debug from Jetpack, if it's helpful.

    I'm at the end of my tether, so any help you can give me would be brilliant.

    Website Link

    Thank you,

    Ste Rumbelow.

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

    (@sterumbelow)

    Someone asked in this thread, before it was moved, if I can update plugins through WordPress itself. Yes, I can.

    Do your have your WordPress installation in a subdirectory? All of my installations in which WordPress is in its own directory have this issue. It’s annoying, but it doesn’t seem to affect any Jetpack modules in my case. Jetpack support asked me to uninstall and reinstall the plugin, but the problem happens on ALL my sites with this installation configuration–old and new, different hosting platforms, different themes and plugins.

    While developing a site in a subdirectory, the connection is fine. Once I change the Site Address to the root directory and follow the Codex instructions for giving WordPress its own directory, I get the same messages you are getting when I check the Debug page.

    Thread Starter sterumbelow

    (@sterumbelow)

    Hi jjbte,

    My install is directly in the root of my server. No subdirectories or .htaccess rewrite for it.

    I’ve always done it this way and never had the issue!

    Do you think I should move it into a subdirectory? Is there a benefit to doing this besides JetPack actually functioning again?

    • This reply was modified 7 years, 3 months ago by sterumbelow.

    For me, the main benefit is not cluttering up my root directory, but that’s just me. There’s nothing wrong with placing WP in your root directory. Subdirectory installation is also a benefit when I’m installing a new WordPress site on an existing website. I can build the new site in a subdirectory while the old site stays live. When the new site is ready, I make the move. There is also a slight security benefit since most bots search for files like xmlrpc.php and wp-login.php in the root directory, so having these files in a subdirectory means those bots will get a 404. It’s hardly a foolproof security solution, of course, since it doesn’t take much digging to find where those files are really located.

    Anyway, your problem seems to be different from mine. I find that the Jetpack Debug tool gives a perfect reading when my WordPress and Site addresses are the same (as yours are). It’s when they’re different that I see the connection issues. Again, though, my modules appear to be unaffected. It sounds like your Jetpack modules are not working at all.

    My first suspicion would be a server issue. You did say you recently had to restore your VPS and that’s when the problem began. I’m not a server expert, so I can’t be of much help in that realm. Maybe your host (if you have one) or someone here with server knowledge can help you figure this out. I don’t think moving WP to a subdirectory would help in your particular situation.

    Thread Starter sterumbelow

    (@sterumbelow)

    Yeah I’m almost convinced that’s the issue too. My host is pretty useless and unwilling to help, saying it’s a ‘self managed platform’.

    Hopefully someone here will have an idea!

    Thanks very much for your help, appreciate it.

    Ugh. I wish I could be of more help. I have no idea how complex your site is, but it’s possible you could find a new host who includes free site migration. That’s just a last-resort suggestion, though. I know how stressful and time-consuming it can be to change web hosts, especially when you require something more advanced like VPS.

    Calling all server admins! We need some help over here! ??

    Thread Starter sterumbelow

    (@sterumbelow)

    Trust me, I’d move hosts if could face doing so! Equally, I’d love to know what’s causing the issue!

    I’m with 123-reg at the moment and the reason I’m on a VPS server is because their shared hosting was appalling for WordPress. I had so much downtime, I ended up moving to something better. I don’t need a VPS at all!

    I bet it’s such a simple fix but even after staying up until 5am this yesterday morning, I couldn’t find the solution!

    For anyone wondering, I’m using Parallels Plesk Panel. Up to date on 17.3, with PHP 7 and Cent OS 7.

    • This reply was modified 7 years, 3 months ago by sterumbelow.
    Thread Starter sterumbelow

    (@sterumbelow)

    Erm…

    I’ve just had a major breakthrough! Jetpack is activated!

    After 10 hours of trying everything under the sun yesterday, and failing, it is of course something very simple that has seemingly fixed it.

    In my wp-config.php file, was the code:

    define( 'JETPACK_CLIENT__HTTPS', 'NEVER' );

    I have no idea what this was there for, or if it should be there, but removing it instantly allowed Jetpack to connect.

    If someone can throw some light on what that code means, I’d appreciate it.

    Cheers.

    I moved to SiteGround last year. Their rates are reasonable and they are among the hosts recommended by WordPress. SiteGround’s GoGeek plan for WP hosting has worked well for me so far. I’m in the US and my site is hosted on their Chicago servers, but they do actually have servers in London. I didn’t take advantage of it, but I believe they do provide free site migration.

    Again, though, I was just making a suggestion in case you truly can’t find a solution to your problem. You may have entirely different requirements and a host that works for me may not work for you at all.

    I posted my hosting comment and immediately saw you posted while I was typing my reply. Good find! I didn’t even know that was something that could be (or needed to be) defined.

    I’m glad you found a fix!

    Thread Starter sterumbelow

    (@sterumbelow)

    Me too! Thank you for your advice. I’ll take a look at Siteground. I was with them for a small project back in about 2008. I think they were a bit smaller then though.

    Hopefully someone can help with figuring out what the code is for.

    Will mark as resolved once/if I get a reply regarding that code!

    • This reply was modified 7 years, 3 months ago by sterumbelow.

    I searched for JETPACK_CLIENT__HTTPS in the Jetpack plugin files and it looks like it’s something you would define if your site couldn’t connect to WordPress.com via HTTPS for some reason (e.g., a misconfigured SSL cert). I think JETPACK_CLIENT__HTTPS is defined as AUTO by default. Hopefully a Jetpack contributor can provide more insight.

    Plugin Contributor csonnek

    (@csonnek)

    Happiness Rocketeer ??

    @sterumbelow since you also contacted us via email, we’ll continue the conversation there. Marking this as resolved as we’re helping you via email.

    Of note: your site is showing as being connected on our end, so the issue most likely is a browser or server caching issue.

    passionspoon

    (@passionspoon)

    I know this is closed….but I need help…and if you are not insisting on it nobody helps you….here is the link to my post on the forum.

    https://www.ads-software.com/support/topic/10520-error/#postform

    Plugin Contributor Richard Archambault

    (@richardmtl)

    @passionspoon I just replied to your thread; sorry, but our support team does not usually respond to forum threads on the weekend. I apologize for the delay!

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Jetpack Won’t Connect To WordPress.com’ is closed to new replies.