Jetpack thinks my dev-environment is my main website

Resolved muckaveli
(@muckaveli)

2 years, 2 months ago

Hello,

my original setup was https://domain.com.
Recently, I have created a copy of that very WordPress installation to https://dev.domain.com as a development environment.

Logging into cloud.jetpack.com I’ve just realized that the dev-version is now listed as my main website.

This brings some trouble with it, like not being able to register a Google Merchants account because “invalid site URL”.

How can I change my domain in Jetpack back to the original?

Viewing 5 replies - 1 through 5 (of 5 total)

Ted Slater
(@tedslater)

2 years, 2 months ago

I’ve had this same problem on a few occasions. I’ve found that the folks at Jetpack are the only ones able to fix this issue. I’ve been very grateful for their help.

Plugin Support Animesh Gaurav (a11n)
(@bizanimesh)

2 years, 2 months ago

Hey @muckaveli – could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread. 🙂
Thread Starter muckaveli
(@muckaveli)

2 years, 2 months ago
@bizanimesh Thank you for the reply, I’ll gladly use the contact form.

Regarding others finding this thread: is there a recommended procedure when it comes to Jetpack and cloning WordPress installations for development purposes?

It must be pretty common to have a live version and another (local or otherwise hidden-from-public) version as a development environment. Is there a proper way to connect Jetpack to this second version or should it always be disconnected while developing and re-connected when the live version will be updated with it?
- This reply was modified 2 years, 2 months ago by muckaveli.
Plugin Support Animesh Gaurav (a11n)
(@bizanimesh)

2 years, 2 months ago
Hey @muckaveli – When you do that, Jetpack safe mode helps if you want to prevent an Identity Crisis with development and staging sites.
- https://jetpack.com/support/safe-mode/#what-is-an-identity-crisis
If your site is not set up for testing purposes, and you’re seeing the Safe Mode notice, then you can click the Fix Jetpack’s Connection button. This will then give you two options to choose from for fixing your site’s connection.
- Move your settings
- Create fresh connection
You can learn more on when to choose which of the above options here:
- https://jetpack.com/support/safe-mode/#what-does-each-button-mean (please follow the tutorial from Fix Jetpack’s Connection).
Another way to do this is:

If you are cloning the site from Production to Staging, then first, please deactivate the Jetpack plugin from the Production site » and then clone the site to Staging » then reconnect Jetpack at both the Production and Staging site.

Similarly, if you are deploying the site from Staging to Production, then first, deactivate the Jetpack plugin both at Staging and Production site » then deploy the Staging site to Production » and then connect the Jetpack to the Production site.
Plugin Support Tamirat B. (a11n)
(@tamirat22)

2 years, 2 months ago

Hello @muckaveli

It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!