¿Estás lidiando con el error 403 Forbidden en tu sitio WordPress?
El error 403 Forbidden es uno de los errores más molestos con los que se puede encontrar el propietario de un sitio web WordPress. Puede impedirle acceder a su área de administrador de WordPress y/o a páginas específicas de su sitio web.
En este artículo, le mostraremos cómo corregir fácilmente el error 403 Forbidden en WordPress.
¿Qué es el error 403 Forbidden en WordPress?
El código de error 403 Prohibido se muestra cuando los permisos de su servidor no permiten el acceso a una página específica de su sitio web WordPress.
Este error suele ir acompañado del texto
403 Prohibido – No tiene permiso para acceder a ‘/’ en este servidor.
Además, se ha producido un error 403 Forbidden al intentar utilizar un ErrorDocument para gestionar la solicitud.
He aquí un ejemplo:
Existen diferentes escenarios en los que puede aparecer este error. Por ejemplo:
- 403 Prohibido – Acceso denegado en la página wp-admin o de administrador de WordPress.
- 403 Prohibido – Durante la instalación de WordPress.
- Error 403 Forbidden – Al visitar cualquier página de su sitio WordPress.
También puede ver “Acceso denegado” en lugar del estado completo 403 Prohibido. Alternativamente, el mensaje podría decir, ‘El acceso a sudominio.com fue denegado. No tiene autorización para ver esta página”.
Para más explicaciones acerca de los códigos de error de WordPress, puede consultar nuestra lista de los errores más comunes de WordPress y cómo corregirlos.
Ahora que ya conoce los distintos tipos de errores 403, hablemos de sus causas.
¿Qué causa el error 403 Forbidden en WordPress?
El código de error 403 Forbidden aparece cuando su servidor no permite el acceso a una página específica. Hay varias causas que pueden hacer que esto ocurra.
Una causa común del error 403 Forbidden en WordPress son los plugins de seguridad mal configurados. Muchos plugins de seguridad de WordPress pueden bloquear una dirección IP (o toda una serie de direcciones IP) si consideran que son malintencionadas.
Otra posible causa podría ser un archivo .htaccess corrupto o permisos de archivo incorrectos en su servidor.
Su empresa de alojamiento de WordPress a veces puede hacer cambios accidentales en los ajustes de su servidor. Esto puede provocar un error 403 Forbidden en su sitio.
Dicho esto, veamos cómo corregir el error 403 forbidden en WordPress.
Nota: Antes de hacer nada, le recomendamos que cree una copia de seguridad completa de su sitio web en WordPress. Puedes marcar / comprobar nuestra guía sobre cómo hacer una copia de seguridad de tu sitio WordPress. Si está utilizando un plugin de copia de seguridad automática de WordPress, asegúrese de que tiene acceso a la copia de seguridad más reciente antes de seguir adelante.
Puede utilizar estos enlaces rápidos si desea omitir un método concreto:
Tutorial en vídeo
Si prefiere instrucciones escritas, siga leyendo.
Método 1: Corregir el error 403 Forbidden causado por un plugin de WordPress
Lo primero que debe hacer es comprobar si uno de sus plugins de WordPress está causando el error 403 Forbidden. Para ello, debe desactivar temporalmente todos los plugins de WordPress. Esto incluye cualquier plugin de seguridad que haya instalado en su sitio.
Si esto resuelve su problema, entonces esto significa que uno de los plugins en su sitio web estaba causando este error.
Puedes averiguar qué plugin estaba causando el error activando todos tus plugins de uno en uno hasta que reproduzcas el error 403 Prohibido. Entonces, tendrás que borrar el plugin problemático y buscar una alternativa o contactar con los desarrolladores para dar soporte.
Si este método no funciona, siga leyendo.
Método 2: Corrección del error 403 Forbidden causado por un archivo .htaccess corrupto
A menudo, el error 403 Forbidden es causado por un archivo .htaccess corrupto en su sitio WordPress. La buena noticia es que corregir este archivo es bastante fácil.
En primer lugar, debe conectarse a su sitio web mediante un cliente FTP como FileZilla o la aplicación Administrador de archivos de cPanel.
A continuación, busque el archivo .htaccess en la carpeta raíz de su sitio WordPress. Consulta esta guía si no encuentras el archivo.htaccess en la carpeta de tu WordPress.
Deberá descargar el archivo .htaccess a su ordenador para tener una copia de seguridad del mismo. Después, simplemente borre el archivo de su servidor. No te preocupes, tu WordPress seguirá funcionando.
Ahora, intente acceder a su sitio web. Si el error 403 prohibido se resuelve, entonces esto significa que su archivo .htaccess estaba dañado.
Puede generar un nuevo archivo .htaccess accediendo a su área de administrador de WordPress y yendo a la página Ajustes ” Enlaces permanentes.
Basta con hacer clic en el botón “Guardar cambios” situado en la parte inferior de la página, y WordPress generará un nuevo archivo .htaccess.
Método 3: Corrección del error 403 Forbidden causado por los permisos de archivo en WordPress
Si las otras soluciones no han corregido el error 403 prohibido en su sitio, entonces la causa más probable son los permisos incorrectos del archivo.
Todos los archivos almacenados en su sitio web tienen permisos de archivo. Estos permisos de archivo controlan quién puede acceder a los archivos y carpetas de su sitio web WordPress.
Permisos de archivo incorrectos pueden causar el error 403 Prohibido. Hacen que tu servidor web piense que no tienes permiso para acceder a esos archivos.
Puedes pedir a tu proveedor de alojamiento WordPress que compruebe que tu sitio web tiene los permisos de archivo correctos. Algunos alojamientos son muy compatibles, así que no les importará y probablemente te lo corregirán.
Cambiar los permisos de archivo usted mismo puede tener graves consecuencias. Si no se siente seguro haciéndolo usted mismo, lo mejor es pedir ayuda a otro propietario de un sitio web WordPress o contratar a un profesional.
Sin embargo, si desea hacerlo usted mismo, a continuación le indicamos cómo comprobar los permisos de sus archivos.
Simplemente conéctese a su sitio WordPress utilizando un cliente FTP. Navegue hasta la carpeta raíz que contiene todos sus archivos de WordPress.
Haz clic para seleccionar una carpeta, haz clic con el botón derecho y, a continuación, selecciona “Permisos de archivo” en el menú.
Tu cliente FTP te mostrará un cuadro de diálogo de permisos de archivo como éste:
Todas las carpetas de su sitio WordPress deben tener un permiso de archivo de 744 o 755.
Mientras tanto, todos los archivos de su sitio WordPress deben tener un permiso de archivo de 644 o 640.
Puedes establecer el permiso de archivo de la carpeta raíz en 744 o 755. También tienes que marcar la casilla siguiente a “Recurse into subdirectories” y luego marcar la opción que dice “apply to directories only”.
Sólo tienes que hacer clic en el botón “Aceptar”. Tu cliente FTP empezará a establecer permisos para todos los subdirectorios de esa carpeta.
Una vez hecho esto, debes repetir el proceso para todos los archivos. Esta vez, utilizarás un permiso de archivo de 644 o 640, y no olvides seleccionar las opciones ‘Recurse into subdirectories’ y ‘Apply to files only’.
Haga clic en el botón “Aceptar”, y su cliente FTP comenzará a establecer los permisos de archivo para todos los archivos seleccionados.
Intenta acceder a tu sitio web ahora y comprueba si el error 403 prohibido ha desaparecido. Ya está.
Esperamos que este artículo te haya ayudado a corregir el error 403 forbidden en WordPress. Puede que también quieras ver nuestros consejos de expertos y hacks para proteger tu área de administrador de WordPress y nuestro artículo sobre por qué usamos Sucuri para mejorar la seguridad de todos nuestros sitios WordPress.
If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.
Syed Balkhi says
Hey WPBeginner readers,
Did you know you can win exciting prizes by commenting on WPBeginner?
Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
You can get more details about the contest from here.
Start sharing your thoughts below to stand a chance to win!
Gary Parker says
None of these fix my problem as it is one page and the only way i could fix it was to rename the permalink, The page in trouble is https://example.com/blog/ and the only way i could fix it was to change it to /blog2/, any ideas?
Michael says
Please somebody help me. I have two websites on the same host. I just added a third addon domain recently and installed wordpress to it through the softaculous installer.
The problem is not from wordpress, and other websites on the same host is accessible.
Please help.
Andreas Johansson says
I hade one page Forbiden 403 and tryied all the steps. And now i dont have permission to login wp-admin on my site?
WPBeginner Support says
Hey Andreas,
Please see our WordPress troubleshooting guide. It will help you find out the issue and then you can fix it.
Administrador
Marcus says
It worked like magic
Juliet Julius says
Thank you so much for this article. My problem was a corrupted htaccess file. My website is now working fine.
Aleli Sanchez Mendez says
I still having this problem. I tried all the steps. The problem began when I installed the WooCommerce plugin in my WordPress Site. Now in my wordpress y receive a 403 Forbidden and in my other site, without wordpress i recieived a 502 Bad Gateway error.
Please someone can help me?
Scott Munson says
I discovered – after all else failed and many hours spent, that at one time (but no longer) I used Bullet Proof security. It left a stray .htaccess file in my wp-admin folder – THAT, was causing the 403 error for me. ARGH!
WPBeginner Support says
Hey Scott,
Thanks for sharing, glad you found the solution
Administrador
joshua jenish zibhu says
how i solve this probkem…. in windows 10……
john says
Thank you, it worked for me.
Oluwaseun says
Thanks!
changing file permission works for me.
Yogesh says
Thanks a ton. Deleting .htaccess worked for me.
JU says
There has to be a fourth step. None of these steps applied. The plugins weren’t the cause. The .htaccess file wasn’t the cause. All the permissions in all files and folders are set to the correct numerical values.
Sendhil Kumar S K says
Hi Friends, One Easy step will make You free from the existing problem.
1. Go to CPanel of Your Domain
2. Click to Expand public_html folder present at the extreme left of the screen.
3. Double click on wp folder present on the write side of the screen
4. Copy All files & Folders inside the wp folder
5. Move all the files & folders inside the wp folder to UP ONE LEVEL
6. Now All files & Folders are out of WP folder, hence WP folder is empty, come one level up & delete the empty WP folder
7. Now go to browser & type your domain_name.com, PERFEFETLY it will be WORKING
All the Best…if you have doubts regarding this mail me to
Also if time permits visit my site
Thank You All
Sergio Casabona says
Hi, there! Thanks for this article!
I got this error, so I access with my ftp and deleted .htaccess file. I’m now able to access my dashboard. But when I go to settings and save again as you say, the error 403 comes back. What can I do?
Thank you, guys!
Josh Allen says
What if I had a dedicated server, and its happening to all 43 of my sites…I just did some kind of WHM update on Bluehost, then it happened….Ive been waiting for an hour to talk to bluehost.
Ronald says
Josh –
I had a similar thing happening to me here. “All of a sudden” none of my sites worked anymore.
I am hosting the sites on my own MacMini, running OS-X Server. After a night of trouble-shooting, I eventually found out that the root cause was me enabling the FTP server in OS-X Server. In there, I set folder permissions for the website root folder for “Everyone Else” to “None” (seemed a bit tricky to give everyone Read access to my sites!). Apparently one is also blocking the _www user access to the websites then…
After I changed this back to “Read Only”, my sites started working again… Pffff.
I’m now looking for a permanent solution, which is not: “Close my firewall for FTP traffic.
Hope this helps,
Ronald
Krishna Patel says
This post saved my life! I can’t thank you enough for this helpful information but.. thanks a million
shah faisal says
You don’t have permission to access /loading.php on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request
James says
The file permission option fixed it, thanks a lot.
gab says
I am getting the 403 error for my page and cannot even login into WordPress because of it… I don’t know how to fix it and don’t see anyone with the same issue.
Reshan says
Hi. My WordPress is handled by the hosting company itself. So I dont have root access. How can I solve this problem?
WPBeginner Support says
Hi Reshan,
Please contact your hosting company. They will be able to fix it for you.
Administrador
Prince says
Thank you. You helped me solved my problem.
Rafael Hernandez-Padilla says
Thank you, the article resolved the issue I was having on my site.
Yves says
Same problem here, and ftp same result… checked in Cpanel and noticed my maindir permissions was 0000 , changed to 0755 and was fixed
Mimi says
In my case, I had my website for 4 years and all of a sudden today I got this error although I did not touch the files or change any permissions. I logged into the control panel and noticed that for some reason the index.php file was missing from the WordPress root folder. I downloaded a new copy of WordPress and copied the index.php file on to the root folder of my WordPress website and the website came back!
So perhaps if anyone is getting the same error, please double check that you have an index.php or index.html file. I hope that helps.
Cian says
Lifesaver – thank you! This worked for me also.
justin says
Ditto…no idea why/how but the index.php disappeared while I was working on a project…I was saved a load of hassle by an automatic backup where the index still existed.
Nick says
Thanks Mimi! This worked for me while the solutions in the article didn’t. In my case, the index.php file wasn’t actually missing but when I replaced the one that was there with a fresh one the site started working again so I guess it was corrupted or had some kind of other problem.
My specific error message did also mention the index.php file so that also makes sense:
Forbidden
You don’t have permission to access /index.php on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
AMar pal says
Help me my website is down.I tried all the given solutions but nothing worked…
Edgar says
Nothing worked for me until I added “Options +FollowSymLinks” (without the quotes) above “RewriteEngine On”.
Doni says
I did all three possible causing 403 error fixing that you informed but it still produced the error. By the way i wanted to edit footer template but when i saved / updated file it produced “403 Forbidden Access to this resource on the server is denied!”
Mimi says
This is a reply to your comment on wpbegginer.com (comment quoted below)
I am not sure if you were able to resolve your problem but I would like to let you know that I got the same error today and I found that the problem was a missing index.php file from the root folder of my website.
———————————————————————–
“I did all three possible causing 403 error fixing that you informed but it still produced the error. By the way i wanted to edit footer template but when i saved / updated file it produced “403 Forbidden Access to this resource on the server is denied!””
Alexandra says
Hello,
I need help, while trying install wordpress with mamp, after i did everything what i supposed to do, it showed me this error :
‘Forbidden
You don’t have permission to access /mysite on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.’
Please help me!
Vasil says
Hello guys.
Forbidden
You don’t have permission to access /shop/ on this server.
I’ve tried everything and doesn’t work.
if someone can help would be great thank you.
KimD says
Thanks. Great article. To fix my problem I had to do a slight variant on what was written. When I looked I found that I had two htaccess files, one in the root directory and another in the wp-admin directory. I regained access to my site by renaming the htaccess file in the wp-admin directory.
Alex says
So glad you posted this, this was my exact issue! Thanks!
Kingsley Felix says
Hello;
Mine happens when i want to save changes of an article by a deleted admin user
Steve says
I have a user who is getting the following 403 when he tries to leave a comment:
403 Forbidden Error Page
If you arrived here due to a search or clicking on a link click your Browser’s back button to return to the previous page. Thank you.
IP Address: xxx.xx.xx.xx” (his actual IP address shows up here)
What could be wrong?
David says
my problem is in .htaccess File. the passage saves my site. Thanks so much
WPBeginner Support says
You are welcome
Administrador
Omotayo Adeoye says
Hi,
I get a ‘Forbidden’ on the wp-admin page of my website. It doesn’t say error 403 – forbidden; it just says forbidden”.
I have re-installed wordpress, checked file permissions, checked htpaccess, deactivated all plugins etc. yet it doesn’t work.
Pls what can i do!
Thanks a lot.
Ricardo says
Hi! When I share my website link to facebook, the title is 403 Forbidden. Directly on my website I didn’t saw any kind of 403 forbidden message. I tried a lot of advises I found, as removing .htaccess file, desactivating all the plugins and also checked permissions. I tried to debug at facebook debugger, but the informations doesn’t change. Anyone can help me to fix this problem?
Mukesh Sharma says
Hello Ricardo,
send me your website link. I can help.
Harney Cercado says
Awesome! You’re a life saver!
Thanks!
Shane says
This was very helpful, thank you guys very much , as we say in Jamaica “Respect”
Javier Gomez says
I have many errors 403 with my images, I will take your advice thanks for the information
An apology for my bad english
Christopher Sowerby says
Hi. my problem is that i can logout from the backend dashboard but i cant logout from the front end (using the bar at the top).
It seems that the nonce in the logout url is different when on the backend. Do you know why this could be? i have cleared everything out of my functions.php but it still happens.
Rameez Ramzan says
Hi,
I am newbie in WordPress and Currently I am facing some problem while login WordPress Dashboard.
It’s showing 403 forbidden errors while login but on the other side my friend open similar site on their internet then its working correctly. Kindly let me know
Thanks,
Pascal says
Thank you for this great post! I resolved my 403 error!!!
WPBeginner Support says
Hey Pascal, glad you found it helpful
Don’t forget to join us on Twitter for more WordPress tips and tutorials.
Administrador
Erik Kubica says
I have similar issue, as a company on our dev server we are running much wordpress sites where to only 1 WP site i started to get 403 and only on wp-admin. 2 Days before i have lived elsewhere when it worked.
foo.bar/somewebsite/* -> 200 OK
foo.bar/somewebsite/wp-admin -> rediret to wp-login.php -> 403 err
foo.bar/somewebsite2/* -> 200 OK
foo.bar/somewebsite2/wp-admin -> rediret -> 200 OK
Ftp to foo.bar is ok, ssh to foo.bar is ok.
On “somewebsite” the WP admin is blocked only for me (all browsers, all existing incognito modes, all cache cleared incl. cookies….). For all people i have asked to try it worked without any problems.
There is nothing wrong with htaccess, wordfence was disabled from ftp (also checked the DB if there is any ban to my IP). checked the main apache2 access log over ssh where i see the 403 record.
Any idea what can be wrong?
Vinish Chaudhary says
Forbidden
You don’t have permission to access / on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
and none of above method work on this error my cpanel not showing. I read the whole article
plz, help me solve this.
thanks
WPBeginner Support says
Please try these troubleshooting tips if nothing works then contact your WordPress hosting provider.
Administrador
Dewlance says
Uhh! WordPress wp-admin 403 error is really time killing.
I try your all tricks but still getting a error. Going to change wp-admin folder with fresh files of wp-admin files.
Maybe it will help me or other option is apache configuration or poorly mod_security configuration.
Greg says
We work with WordPress everyday and recently encountered the 403 error. It was the file permissions and htaccess file that was reconfigured due to one of the security plugins. Your post on the matter was very helpful. Thanks for taking the time to post it.
WPBeginner Support says
Glad you found it helpful
Administrador
zulfiqar ali says
dear sir my site name is my site give me error like
Forbidden
You don’t have permission to access / on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
and non of above method work on this error my cpane not showing any files in file explorer and also not connecting via FTP client.. i read whole article
plz help me solve this..
thanks
Lindani says
I cant my thinks now because of this forbidden error help please
hardik says
Hi i really impress with your suggestion thanks u so much i have solve my error
Oliver says
Hi, we have also been experiencing a 403 error. It first started happening when I tried to update the wp-core to 4.5. Ever since we get a 403 about once a day. I have done everything that I can think of to rectify the issue; reverted to a back-up of the site previous to the update; deactivated all plugins; checked file permissions; contacted hosts to see if our IP addresses were blacklisted; deleted .htaccess; changed theme to default 2016 the only thing that works when getting a 403 is to turn off the router wait for the IP to change and then we can access again. So it would seem to be an IP issue but I cannot find where this is IP blockage is.
Does anybody know of any other place where an IP blacklist maybe?
Thanks.
Barbara Puchala says
We just had this error. A outside web designer was creating a WordPress site for us and kept getting the 403 error.
Turns out our hosting company, as part of its security measures, has its servers block any attempt to sign in with the user name ‘Admin’. I know, you would think he would know better. A change to the user name was all that was needed.
george says
your typo
[due to a poorly configured security plugins]
due to a poorly configured security plugin
WPBeginner Support says
Thanks, we have fixed it.
Administrador