Você está lidando com o erro 403 Forbidden em seu site WordPress?
O erro 403 Forbidden é um dos erros mais incômodos que um proprietário de site do WordPress pode encontrar. Ele pode impedi-lo de acessar a área de administração do WordPress e/ou páginas específicas do seu site.
Neste artigo, mostraremos a você como corrigir facilmente o erro 403 Forbidden no WordPress.
O que é o erro 403 Forbidden no WordPress?
O código de erro 403 Forbidden é exibido quando as permissões do servidor não permitem o acesso a uma página específica no site do WordPress.
Esse erro geralmente é acompanhado pelo texto:
403 Forbidden – Você não tem permissão para acessar ‘/’ neste servidor.
Além disso, foi encontrado um erro 403 Forbidden ao tentar usar um ErrorDocument para tratar a solicitação.
Aqui está um exemplo de como ele se parece:
Há diferentes cenários em que você pode ver esse erro. Por exemplo:
- 403 Forbidden – Acesso negado na página de login do wp-admin ou do WordPress.
- 403 Forbidden – Durante a instalação do WordPress.
- Erro 403 Forbidden – Ao visitar qualquer página em seu site WordPress.
Você também pode ver “Access Denied” (Acesso negado) em vez do status completo 403 Forbidden (Proibido). Como alternativa, a mensagem pode dizer: “O acesso a yourdomain.com foi negado. Você não tem autorização para visualizar esta página”.
Para obter mais explicações sobre os códigos de erro do WordPress, consulte nossa lista dos erros mais comuns do WordPress e como corrigi-los.
Agora que você conhece os diferentes tipos de erros 403, vamos falar sobre suas causas.
O que causa o erro 403 Forbidden no WordPress?
O código de erro 403 Forbidden aparece quando seu servidor não permite o acesso a uma página específica. Há várias causas que podem fazer com que isso aconteça.
Uma causa comum do erro 403 Forbidden no WordPress são os plug-ins de segurança mal configurados. Muitos plug-ins de segurança do WordPress podem bloquear um endereço IP (ou um intervalo inteiro de endereços IP) se acreditarem que eles são mal-intencionados.
Outra causa possível pode ser um arquivo .htaccess corrompido ou permissões de arquivo incorretas em seu servidor.
Sua empresa de hospedagem WordPress pode, às vezes, fazer alterações acidentais nas configurações do servidor. Isso pode resultar em um erro 403 Forbidden em seu site.
Dito isso, vamos dar uma olhada em como corrigir o erro 403 forbidden no WordPress.
Observação: antes de fazer qualquer coisa, recomendamos criar um backup completo do WordPress em seu site. Você pode conferir nosso guia sobre como fazer backup do seu site WordPress. Se estiver usando um plug-in de backup automático do WordPress, certifique-se de ter acesso ao backup mais recente antes de prosseguir.
Você pode usar esses links rápidos se quiser pular para um método específico:
Tutorial em vídeo
Se você preferir instruções por escrito, continue lendo.
Método 1: Como corrigir o erro 403 Forbidden causado por um plug-in do WordPress
A primeira coisa que você precisa fazer é verificar se um dos seus plug-ins do WordPress está causando o erro 403 Forbidden. Para fazer isso, você precisa desativar temporariamente todos os plug-ins do WordPress. Isso inclui todos os plug-ins de segurança que você possa ter instalado em seu site.
Se isso resolver seu problema, significa que um dos plug-ins do seu site estava causando esse erro.
Você pode descobrir qual plugin estava causando o erro ativando todos os plugins, um de cada vez, até reproduzir o erro 403 Forbidden. Em seguida, será necessário excluir o plug-in com problema e procurar uma alternativa ou entrar em contato com os desenvolvedores para obter suporte.
Se esse método não funcionar, continue lendo.
Método 2: Como corrigir o erro 403 Forbidden causado por um arquivo .htaccess corrompido
Geralmente, o erro 403 Forbidden é causado por um arquivo .htaccess corrompido em seu site WordPress. A boa notícia é que corrigir esse arquivo é muito fácil.
Primeiro, você precisa se conectar ao seu site usando um cliente FTP como o FileZilla ou o aplicativo File Manager no cPanel.
Em seguida, localize o arquivo .htaccess na pasta raiz de seu site WordPress. Consulte este guia se não conseguir encontrar o arquivo .htaccess na pasta do WordPress.
Será necessário fazer o download do arquivo .htaccess para o seu computador para que você tenha um novo backup dele. Depois disso, basta excluir o arquivo do seu servidor. Não se preocupe, seu WordPress ainda poderá funcionar.
Agora, tente acessar o site. Se o erro 403 forbidden for resolvido, isso significa que seu arquivo .htaccess estava corrompido.
Você pode gerar um novo arquivo .htaccess fazendo login na área de administração do WordPress e acessando a página Configurações ” Permalinks.
Basta clicar no botão “Salvar alterações” na parte inferior da página, e o WordPress gerará um novo arquivo .htaccess.
Método 3: Como corrigir o erro 403 Forbidden causado por permissões de arquivo no WordPress
Se as outras soluções não corrigiram o erro 403 proibido em seu site, as permissões incorretas de arquivo são a causa mais provável.
Todos os arquivos armazenados em seu site têm permissões de arquivo. Essas permissões de arquivo controlam quem pode acessar os arquivos e as pastas no seu site WordPress.
Permissões incorretas de arquivos podem causar o erro 403 Forbidden. Elas fazem o servidor da Web pensar que você não tem permissão para acessar esses arquivos.
Você pode solicitar ao seu provedor de hospedagem WordPress que verifique se as permissões de arquivo do seu site estão corretas. Alguns hosts são muito prestativos, portanto, não se importarão e provavelmente resolverão o problema para você.
Alterar as permissões de arquivos por conta própria pode ter consequências graves. Se você não se sentir confiante para fazer isso sozinho, é melhor pedir ajuda a um colega proprietário de site do WordPress ou contratar um profissional.
No entanto, se você quiser fazer isso sozinho, veja como verificar as permissões de arquivo.
Basta conectar-se ao seu site WordPress usando um cliente FTP. Navegue até a pasta raiz que contém todos os seus arquivos do WordPress.
Clique para selecionar uma pasta, clique com o botão direito do mouse nela e selecione “File permissions” (Permissões de arquivo) no menu.
Seu cliente FTP mostrará uma caixa de diálogo de permissões de arquivo como esta:
Todas as pastas em seu site WordPress devem ter uma permissão de arquivo de 744 ou 755.
Enquanto isso, todos os arquivos em seu site WordPress devem ter uma permissão de arquivo de 644 ou 640.
Você pode definir a permissão de arquivo para a pasta raiz como 744 ou 755. Você também precisa marcar a caixa ao lado de “Recurse into subdirectories” e, em seguida, marcar a opção que diz “apply to directories only”.
Basta clicar no botão “OK”. Seu cliente FTP começará a definir as permissões para todos os subdiretórios dessa pasta.
Quando isso for feito, você precisará repetir o processo para todos os arquivos. Desta vez, você usará a permissão de arquivo de 644 ou 640 e não se esqueça de selecionar as opções “Recurse into subdirectories” e “Apply to files only”.
Clique no botão “OK” e seu cliente FTP começará a definir as permissões de todos os arquivos selecionados.
Tente acessar seu site agora e veja se o erro 403 proibido desapareceu. É isso aí!
Esperamos que este artigo tenha ajudado você a corrigir o erro 403 forbidden no WordPress. Talvez você também queira ver nossas dicas e hacks de especialistas para proteger sua área de administração do WordPress e nosso artigo sobre por que usamos a Sucuri para melhorar a segurança de todos os nossos sites WordPress.
Se você gostou deste artigo, inscreva-se em nosso canal do YouTube para receber tutoriais em vídeo sobre o WordPress. Você também pode nos encontrar no Twitter e no 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