Table of contents
Jetpack Blocks Admin Login Solution: Whitelist Your IP
I don’t care much about Jetpack’s new security method until I was locked out of my dashboard this afternoon. Jetpack probably thought that I was trying to hack on something due to multiple log-in activities throughout my WordPress sites.
Clearly, they are trying to separate between good guys and bad ones based on the number of sites they are trying to access wp-admin area at the same time.
Well, that’s a good criterion to base on. However, since I have many sites, the multiple login activities are inevitable. Although Jetpack sent me an email to reattempt my login, the button in the email did not work. It said “bad request”. So sad.
So, I have to add my IP to the Jetpack whitelist to prevent future blocks. Ah wait…if I was already blocked, how could I do anything? Just follow these three simple steps:
Deactivate Jetpack from your web folder
So you have cPanel or FTP access, right?
For FTP user, just go to your WordPress folder > wp-content > plugins.
You will see the Jetpack from the list. Simply rename it Jetpack-disabled. And you’re done. The plugin is disabled.
If you choose to visit cPanel, also navigate to your web folder through File Manager > public_html > your WordPress site > wp-content > plugins.
And similarly, rename the Jetpack to Jetpack-disabled.
So simple. I love simple things.
Login again to your site
Since Jetpack is disabled, you will be able to login normally to your dashboard again.
Activate Jetpack from your dashboard
Since you are already login, activating Jetpack won’t get you locked out of the site again.
Go to Plugins > Jetpack and click activate.
Whitelist your IP in Jetpack settings
When Jetpack is activated, go to Jetpack > Settings > Security.
Expand the Brute force attack protection. You will see your IP address listed there. Simply click Add to Whitelist.
And don’t forget to Save Settings.
You’re done. Your IP is now safe.
Can’t Update Plugins. Error: Download failed. Destination directory for file streaming does not exist or is not writable
This happens when the Temp directory of the host is not found, or the Temp folder url is wrong. Simply update the correct URL in wp-config.php. For Bluehost it is:
add_query_arg() missing parameters
So from add_query_arg doc:
Setting any query variable’s value to boolean false removes the key.
So if the value is false, the key will disappear from url.
Do I need to esc_url() when using wp_nonce_url()?
Following wp_nonce_url() doc, it returns a string:
Escaped URL with nonce action added.
So the string already escaped. No need to do more.