• Resolved delaitec

    (@delaitec)


    I can’t connect to jetpack after cloning my website.

    I made a clone of my website.
    And when logging into the clone site, jetpack asked me what I wanted to do.

    I chose that the CLONE SITE should get the settings from the original site.
    This way the original site would be disconnected.

    However, when logging into the Original Site,
    to create a new connection with the jetpack, I can’t.

    He says he had a problem and asks me to try later. but it never works.

    I have already checked the jetpack and wordpress versions and they are up to date.

    I’ve also tried deactivating all plugins and it didn’t work.

    It appears that something on the Jetpack server is preventing the connection.

    Can anyone help me?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter delaitec

    (@delaitec)

    On the WordPress diagnostics page I get this error:

    Connection Token Health [JETPACK]
    A healthy connection ensures that essential Jetpack services like statistics and security are provided to your WordPress site.
    Error Blog token validation failed.
    Reconnect to Jetpack.
    Reconnect Jetpack

    I click on reconnect, but it doesn’t help, I get the same error:

    An error has occurred. Please try again.”

    Thread Starter delaitec

    (@delaitec)

    I did some more tests,
    I deactivated ALL plugins.
    I disabled and uninstalled Jetpack.
    Deletes all Jetpack tables

    I tested it on the website https://jptools.wordpress.com/debug/

    With the jetpack uninstalled, and all its entries removed from the database.
    and I received this message:

    After this, I installed and activated the jetpack, “but didn’t try to connect” and received this message:

    After it was installed, I also tried accessing the link:
    https://mysite.com/xmlrpc.php

    And I received the message:
    Page not found
    The page you are looking for doesn’t exist, or it has been moved.
    Please try searching using the form below.

    (I get this message on all my sites, and on all of them I can log in to the jetpack, only on this one I can’t, so this is not the problem)

    After this, I tried AGAIN to log into the jetpack, and received the same error as before.
    Look:

    NOTE:
    After, uninstall Jetpack, and delete all tables,
    the error that appeared on the WordPress Diagnostics screen no longer appears.

    I really don’t know what’s causing this

    I believe there is a blockage on the Jetpack servers.

    Thread Starter delaitec

    (@delaitec)

    An update:

    This link:

    https://mysite.com/site/xmlrpc.php

    It’s working.
    I thought it wasn’t because my website is in the “/site” folder and I hadn’t added this part to the url when I initially tested it.

    I received the message:
    XML-RPC server accepts POST requests only.

    Correctly.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @delaitec

    Thanks for additional information here. When WordPress is installed in a subdirectory, there is a small modification that we need to make on our end for Jetpack to connect properly.

    I have made that adjustment. Please uninstall and reinstall Jetpack once more. This should cycle the connection and allow you to connect.

    If you still have issues, let us know.

    Thread Starter delaitec

    (@delaitec)

    Hello.

    I don’t know if you understood correctly.

    After you made the adjustment there, something happened

    I went to check my sites, and the “clone site” that was already connected and working, showed the message “again” saying that there were 2 Jetpack connections.

    I had to check again that I wanted to migrate the data to it from the original site to the clone (subdomain) and it connected again.

    The original site, which is the problematic one, continues to have the problem and does not connect to Jetpack. (I uninstalled and reinstalled it) but without success.

    Understand, the problem is occurring on the original site, which is not in the subdomain.

    It is this site that does not connect to Jetpack.

    The problem persists.

    Thanks

    Thread Starter delaitec

    (@delaitec)

    Taking advantage. All my sites are installed in subdirectories “…/site” and I have never had problems activating jetpack. The clone site that is in a subdomain also connected normally.

    The problem is in the ORIGINAL Site, which I cloned. It no longer connects to jetpack.

    See what I said about the blog token validation failure message, this could be the cause, or something on the jetpack server.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @delaitec

    I’m sorry for the confusion.

    Reading over the thread, you mention the following sites:

    • Original site
    • A site in example.com/site
    • A cloned site on a subdomain

    At this point, it would help if we had the URL for all 3 of these sites. Could you please post your site URL here so that we can take a look?

    If you want it to remain private, you can also contact us via this contact form:

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

    If you choose to reach out directly, please include a link to this thread.

    Thanks!

    Thread Starter delaitec

    (@delaitec)

    Sorry for the confusion.

    There are only 2 sites:

    Original: mydomain.com/site

    Clone: ??loja.mydomain.com/site

    The site that is not connecting to jetpack is the ORIGINAL site (mydomain.com/site)

    Note that to access any of my sites, you don’t need to type “/site” at the end, I’ve already made the adjustments to hide this from the URL.

    About sending the domains, I prefer to send them via private message: But look, I also asked for help on github, and I already sent the domains and information in this same form that you sent me at Jeremy Herve’s request. Can you find it there? Or do you want me to send it again?

    Have a great day!

    Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hi there,

    I have found the GitHub issue and the related ticket.
    I have just replied to the ticket. I’m marking this thread as resolved since we’ll follow up via email.

    Thank you!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.