WordPress login error 403
I’m currently trying to log into a WordPress website, which I downloaded off the virtual server, now in my local server (MAMP, because I’m on a Mac machine). When I try and log into the backend, it successfully gives me the WordPress login screen. After I log in with the correct credentials, it gives me the following:
We’re sorry, but we could not fulfill your request for /wp-login.php on this server.
You do not have permission to access this server. Data may not be posted from offsite forms.
Your technical support key is: key number
You can use this key to fix this problem yourself.
If you are unable to fix the problem yourself, please contact wiley at illinimedia.com and be sure to provide the technical support key shown above.
One of the plugins we use on this site is Bad Behavior, which I believe is the cause of the problem. So, I looked up different support posts, such as:
I’ve tried removing the bad behavior folder out of the plugin folder, "deactivating" the plugin. Then, I restarted my Apache server. But no luck.
Is there something else that I could be trying?
Thanks in advance!
It sounds like you did not correctly move WordPress and your local install is trying to login to the hosted site. I am guessing that this is the problem becasue of this sentence, "Data may not be posted from offsite forms." Your login form should not really ever be "offsite". You need to change the site URL just as if you’ve moved the site from one domain name to another.
Common Problems with WordPress#
Expat or Parsing Error#
This is very common and usually involves a bad plugin! If you just installed a plugin, you should try disabling and try again. If that doesn’t help, just contact support and ask us to check our logs, we’ll do our best to identify the troubled plugin for you!
Author is the Authenticated User Rather Than Specified Author#
This can happen if the authenticated user does not have an appropriate role. Please review WordPress’ details on Roles and Capabilities as you will need an authenticated user who at least has an Editor role to post as other authors.
500 Internal Server Error or other trouble connecting.#
In order to connect to WordPress, you must have XML-RPC functionality turned on. This is turned on by default in WordPress 3.5+. If you’re having issues connecting, go to Settings > Writing > Remote Publishing and check the checkbox.
You may also receive this error if your WordPress installation is secured and not publicly available. Unfortunately, the installation must be publicly accessible to work with Zapier.
Also, we’re unable to provide IPs to whitelist as our IPs are not static – they rotate because we use AWS. If you’d like, you should be able to whitelist a block of IPs from AWS to make this work. You would just need to make sure the list you’re whitelisting is the us-east-1 IP range.
AWS provides a list of their IP address ranges at https://ip-ranges.amazonaws.com/ip-ranges.json. You can read more about how to use those IPs here.
Additionally, Zapier’s calls will always include the header User-Agent: Zapier , so this may be an alternative when whitelisting a whole range of IPs isn’t feasible.
(403) Forbidden Error#
Jetpack Protect (official WordPress module) will occasionally block some AWS IPs — you can either whitelist the IP listed in the error, disable Protect altogether, or if try and whitelist all AWS us-east-1 IPs. You can read more about how to use those IPs here.
- Whitelist with Jetpack : https://jetpack.com/support/security-features/#unblock.
- Whitelist the xmlrpc.php file: You can find help here. You’ll want to whitelist our AWS range (all the US-East IPs from here).
- Enable/Disable : https://jetpack.com/support/security-features/#enable
Once you do that, try reconnecting your WordPress account to see if this resolves the issue.
Error: XML-RPC server accepts POST requests only#
This error could mean that you’re using the wrong Base URL in the login screen. If you’re using http: try using https: . If you’re using www.example.com try using it example.com .
If you continue to get this error, then it’s likely because the XML-RPC is being blocked on the WordPress site. It’s most likely being blocked by a plugin, the hosting provider, or a security setting. To fix, try disabling a your plugins one and a time, then try reconnecting to WordPress account to see if you can isolate the problem plugin.