locked out of my own site
-
You people are pirates! I installed WooCommerce 2 days ago and Jetpack is apparently required to run that plugin? Now, Jetpack has locked me out of my own site! Can’t even login via my ftp. Can’t adjust security settings in wordpress.com account to whitelist. Angry as hell!
The blog I need help with is: (visible only to logged in users)
-
Hi bluechollaventuresllc –
Thanks for getting in touch. I’ll help you get sorted out.
To start, I don’t see southernarizonadigitalmarketing.com connected to a WordPress.com user account. Is this the site that you are working on?
I’ve run it through the Jetpack debug tool at jetpack.com/debug and the connection has come back perfect – no errors there.
Have you resolved that issue already?
Does your WooCommerce sign in work still?
Sorry for so many questions, I’m just trying to make sure I can understand where things are going awry. Thanks.
-
The site is connected to my user account Scott anders @ bluechollaventuresllc.
I was just able to login to WooCommerce account using WordPress.com
After posting my angry comment, sorry for that, I did quite a bit of research on this. Admittedly, I knew nothing about WordPress.com and Jetpack before installing WooCommerce. I also knew nothing about the apparent connection between WooCommerce and Jetpack. It would have been a big help if that information was part of the WooCommerce install. I have a better understanding, now, but still not totally clear on why I need Jetpack to run WooCommerce. Here are the actions I took.
1. I used FileZilla to rename the Jetpack plugin folder to get into the WP dashboard. That allowed me to login to my WP admin account.
2. I reactivated the plugin and disabled brute force protection. (apparently, I was locked out because JetPack saw my CloudFlare server IP addresses as malicious attempts to login?)
3. While logged into WordPress.com account, after adding the site again, I noticed a few times a notification that WP.com wasn’t able to connect to the site. It was intermittent.Am definitely open to any advice/education you can give me on all of this.
-
Hi there,
I also knew nothing about the apparent connection between WooCommerce and Jetpack.
…but still not totally clear on why I need Jetpack to run WooCommerce.
There isn’t one, really, and you don’t need Jetpack to use WooCommerce unless you’re specifically using the WooCommerce Services add-on – that’s the only thing in WooCommerce that requires Jetpack to work, as that add-on uses the WordPress.com billing system to pay for shipping labels and our server infrastructure to calculate real-time taxes and shipping rates.
If you’re not using WooCommerce Services, you should be able to remove Jetpack from your site without any issues.
Can you recall exactly where in the process of setting up WooCommerce you were asked to also install and connect Jetpack?
2. I reactivated the plugin and disabled brute force protection. (apparently, I was locked out because JetPack saw my CloudFlare server IP addresses as malicious attempts to login?)
Jetpack’s blocking feature should go via the IP address of the computer from where you’re trying to log in, not the IP address of your server. Please open a support ticket with Jetpack support so they can look into this further:
Note that Jetpack also has a single-sign-on (SSO) feature, where you can use your WordPress.com account login to log into WP-Admin instead of entering your site’s admin credentials there, which will also help you bypass any issues with your IP address being blocked.
3. While logged into WordPress.com account, after adding the site again, I noticed a few times a notification that WP.com wasn’t able to connect to the site. It was intermittent.
Renaming the Jetpack folder might have broken the connection. Please try disconnecting and reconnecting Jetpack from within WP-Admin. You can also find other troubleshooting steps here:
Jetpack support will also be able to help you troubleshoot that in more detail if you contact them about the IP blocking issue.
- The topic ‘locked out of my own site’ is closed to new replies.