{"id":21441,"date":"2025-09-09T09:01:24","date_gmt":"2025-09-09T13:01:24","guid":{"rendered":"https:\/\/kb.n0c.com\/?post_type=ht_kb&#038;p=21441"},"modified":"2025-09-12T14:46:30","modified_gmt":"2025-09-12T18:46:30","slug":"how-to-manage-403-errors-on-your-n0c-hosting","status":"publish","type":"ht_kb","link":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/","title":{"rendered":"How to Manage 403 Errors On Your N0C Hosting"},"content":{"rendered":"<div class=\"wp-block-post-author-name\">Fabrice Q. Conseiller Technique<\/div>\n\n\n<h2 class=\"wp-block-heading\">Introduction<\/h2>\n\n\n\n<p>A 403 error means that access to a page or resource on your website is prohibited. It can occur for a variety of reasons. But do not worry: it can usually be fixed quickly.<\/p>\n\n\n\n<p>In this article, we will show you how to diagnose and resolve a 403 error. We will use tools available in your N0C control panel.<\/p>\n\n\n\n<p class=\"wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-info\"><strong>Note :<\/strong> The <a href=\"https:\/\/kb.n0c.com\/en\/glossary\/\" target=\"_blank\" rel=\"noreferrer noopener\">glossary<\/a> contains explanations on a variety of topics and can be consulted to clarify certain terms.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"prerequis\">Prerequisites<\/h2>\n\n\n\n<p>Enter the following address in your web browser: <a href=\"https:\/\/mg.n0c.com\/en\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/mg.n0c.com\/en\/<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Possible Causes of 403 Errors<\/h2>\n\n\n\n<p>Once you understand what a 403 error is, it is useful to identify the most common causes. This allows you to pinpoint the source of the problem more quickly and choose the right corrective actions.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Web application firewall (<a href=\"#web-application-firewall-waf\">WAF<\/a>). The WAF may block certain requests based on security rules such as suspicious paths, abnormal behavior, or known attack signatures.<\/li>\n\n\n\n<li><a href=\"#file-permissions\">File permissions<\/a>. Incorrect permissions can prevent access to certain files or folders on your site.<\/li>\n\n\n\n<li><a href=\"#htaccess-files\">.htaccess files<\/a>. Incorrect configuration or restrictive rules in these files can block access to certain resources.<\/li>\n\n\n\n<li><a href=\"#software-functions\">Software functions<\/a>, <strong>such as <code>header()<\/code> in PHP<\/strong>. Incorrect use of HTTP headers in your code can also cause a 403 error.<\/li>\n\n\n\n<li><a href=\"#csf\">CSF<\/a> (ConfigServer Security &amp; Firewall). This server firewall can block requests based on various criteria (IP, user-agent, etc.).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"web-application-firewall-waf\"><strong>Web Application Firewall (WAF)<\/strong><\/h2>\n\n\n\n<p>The WAF protects your site by automatically blocking malicious requests, such as SQL injection attempts or penetration testing (pentesting). It filters requests before they reach your application.<\/p>\n\n\n\n<p>However, there are rules that can sometimes block legitimate actions, particularly with certain plugins or CMS modules such as WordPress or PrestaShop. This can result in 403 errors, known as \u201cfalse positives.\u201d<\/p>\n\n\n\n<p>In this case, the tools available in your N0C panel allow you to accurately diagnose the rule in question and adjust it as needed, while maintaining good overall security.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"marche-a-suivre\">Procedure<\/h3>\n\n\n\n<h4 class=\"wp-block-heading\">Step 1 &#8211; Generate a 403 Error<\/h4>\n\n\n\n<p>Try to reproduce the 403 error on your site or admin interface (e.g., access a specific page or use a feature that triggers the block). This will create an entry in the <a href=\"https:\/\/kb.n0c.com\/en\/glossaire\/firewall\/\" target=\"_blank\" rel=\"noreferrer noopener\">firewall<\/a> logs.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"151\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png\" alt=\"403 error example\" class=\"wp-image-21349\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-300x44.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-768x113.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-50x7.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-60x9.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-100x15.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403.png 1447w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<h4 class=\"wp-block-heading\">Step 2 &#8211; Note Important Informations<\/h4>\n\n\n\n<p>Immediately after reproducing the error, note the following information:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The exact <strong>date and time<\/strong>, including the <strong>time zone<\/strong>.<\/li>\n\n\n\n<li>The <strong>public IP address<\/strong>, which you can find via <a href=\"https:\/\/votreip.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">votreip.org<\/a> (French site).<\/li>\n<\/ul>\n\n\n\n<p>This data will make it easier for you to find the exact corresponding event in the logs.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Step 3 &#8211; Identify Blocks Via The Firewall Log (WAF)<\/h4>\n\n\n\n<p><a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/activating-and-deactivating-the-waf-with-n0c\/#:~:text=com\/en\/.-,How%20to%20View%20the%20Firewall%20Protection%20History,-Go%20to%20Security\" target=\"_blank\" rel=\"noreferrer noopener\">The firewall logs<\/a> are accessible from your N0C interface. They allow you to find the rules that caused a block, often related to sensitive interfaces such as back offices. Please refer to the article <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/activating-and-deactivating-the-waf-with-n0c\/\" target=\"_blank\" rel=\"noreferrer noopener\">How to Configure the Web App Firewall (WAF) and View Firewall History<\/a> for additional details.<\/p>\n\n\n\n<p>Go to <strong>Security -&gt; Firewall Protection History<\/strong>. There you will find details of the blocked event: the URL in question, the type of request, the source IP address of the error, and, most importantly, the <strong>RULE ID<\/strong> that triggered the protection.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1570\" height=\"331\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403.png\" alt=\"Details of the blocked event displayed in N0C\" class=\"wp-image-21470\" style=\"width:668px;height:auto\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403.png 1570w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-300x63.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-1024x216.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-768x162.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-50x11.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-1536x324.png 1536w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-60x13.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-log-403-100x21.png 100w\" sizes=\"auto, (max-width: 1570px) 100vw, 1570px\" \/><\/a><\/figure><\/div>\n\n\n<p class=\"wp-block-ht-blocks-messages wp-block-hb-message wp-block-hb-message--withicon is-style-danger\"><strong>Important \u2013 Carefully check the source IP address of the block.<\/strong><\/p>\n\n\n\n<p>Before modifying or disabling a WAF rule, make sure that the blocked request is coming from <strong>your own IP address<\/strong> and not from a third party.<\/p>\n\n\n\n<p>It is common for automated attacks\u2014using scanners, bots, or exploitation attempts\u2014to generate 403 errors. Unblocking a rule without checking the source IP can <strong>dangerously reduce your site&#8217;s security<\/strong> by allowing truly malicious behavior.<\/p>\n\n\n\n<p><strong>Reminder: every website online is constantly subject to attack attempts<\/strong>, even if there are no visible symptoms. Therefore, be vigilant when interpreting firewall logs.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Step 4 &#8211; Adjust Security Rules<\/h4>\n\n\n\n<p>Once you have identified the problematic rule, you can disable it individually.<\/p>\n\n\n\n<p>To do this, go to: <strong>Security -&gt; Web Application Firewall (WAF) -&gt; CUSTOMIZE RULES<\/strong>.<\/p>\n\n\n\n<p>Search for the rule by its <strong>ID<\/strong>, then disable it if it is blocking a legitimate action on your site. It is recommended that you only disable rules that are strictly necessary in order to maintain a good level of protection.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-1024x245.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"245\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-1024x245.png\" alt=\"Disable the security rule with N0C\" class=\"wp-image-21472\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-1024x245.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-300x72.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-768x184.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-50x12.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-1536x368.png 1536w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-60x14.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509-100x24.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-waf-disable-390509.png 1616w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<p>For more information, see our article on this topic: <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/activating-and-deactivating-the-waf-with-n0c\/\" target=\"_blank\" rel=\"noreferrer noopener\">How to Configure the Web App Firewall (WAF) and View Firewall History<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"file-permissions\"><strong>File Permissions<\/strong><\/h2>\n\n\n\n<p>403 errors can also be caused by incorrect permissions on your site&#8217;s files or folders. Here&#8217;s how to diagnose and fix this type of problem using your N0C interface.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1 \u2013 Identify a 403 Error Related to Permissions<\/h3>\n\n\n\n<p>In the browser, an error message such as: \u201c<strong>You don&#8217;t have permission to access this resource<\/strong>\u201d or \u201c<strong>Server unable to read the file, denying access to be safe<\/strong>\u201d may indicate a permissions issue.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-1024x151.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"151\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-1024x151.png\" alt=\"Error message for 403\" class=\"wp-image-21355\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-1024x151.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-300x44.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-768x113.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-50x7.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-60x9.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403-100x15.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/permissions-403.png 1456w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<h3 class=\"wp-block-heading\">Step 2 \u2013 Make a difference with WAF blocking<\/h3>\n\n\n\n<p>This type of error <strong>does not appear in WAF logs<\/strong>, but <strong>only in access logs<\/strong>. This confirms that it is not a WAF false positive.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Access log<\/strong>: <strong>Domains -&gt; Access log<\/strong>.<\/li>\n\n\n\n<li><strong>WAF log<\/strong> (for comparison): <strong>Security -&gt; Firewall protection history<\/strong>.<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-1024x431.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"431\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-1024x431.png\" alt=\"Access Log filtered to show only errors 400\" class=\"wp-image-21479\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-1024x431.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-300x126.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-768x323.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-50x21.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-1536x647.png 1536w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-60x25.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1-100x42.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-n0c-journal-acces-403-1.png 1582w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><figcaption class=\"wp-element-caption\">Access Log filtered to show only errors 400<\/figcaption><\/figure><\/div>\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-1024x71.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"71\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-1024x71.png\" alt=\"Example of a 403 error in the Access Log\" class=\"wp-image-21359\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-1024x71.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-300x21.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-768x53.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-50x3.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-60x4.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login-100x7.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/n0c-journal-acces-403-wp-login.png 1285w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><figcaption class=\"wp-element-caption\">Example of a 403 error in the Access Log<\/figcaption><\/figure><\/div>\n\n\n<h3 class=\"wp-block-heading\">Step 3 \u2013 Check Permissions in File Explorer<\/h3>\n\n\n\n<p>As explained in the article <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/n0c-filemanager\/\">How to use File Manager<\/a>, open <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/n0c-filemanager\/#directory\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>File Manage<\/strong><\/a><a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/n0c-filemanager\/#directory\"><strong>r<\/strong><\/a> from <strong>Files -&gt; File Manager<\/strong>.<\/p>\n\n\n\n<p>Check the permissions for the file or folder in question, as well as those for its parent folders.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Directories containing executables<\/strong> (such as <code>public_html<\/code>, <code>wp-content<\/code>, etc.) should generally have <strong>755<\/strong> permissions.<\/li>\n\n\n\n<li><strong>Files<\/strong> (such as <code>.php<\/code>, <code>.html<\/code>, <code>.htaccess<\/code> etc.) should have <strong>644<\/strong> permissions.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4 \u2013 Correct Permissions<\/h3>\n\n\n\n<p>In the <strong>File Manager<\/strong> :<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Right-click<\/strong> on the problematic file or folder.<\/li>\n\n\n\n<li>Select <strong>Permissions<\/strong>.<\/li>\n\n\n\n<li>Correct the values if necessary (for example, 644 for a file, 755 for a folder).<\/li>\n<\/ol>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full is-resized\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm.png\"><img loading=\"lazy\" decoding=\"async\" width=\"794\" height=\"1036\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm.png\" alt=\"Changing permissions in the N0C File Manager\" class=\"wp-image-21487\" style=\"width:512px;height:auto\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm.png 794w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-230x300.png 230w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-785x1024.png 785w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-768x1002.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-38x50.png 38w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-46x60.png 46w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/en-filemanager-fix-perm-77x100.png 77w\" sizes=\"auto, (max-width: 794px) 100vw, 794px\" \/><\/a><\/figure><\/div>\n\n\n<p>Once you have adjusted the permissions, reload your site to check if the 403 error has been resolved.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"htaccess-files\"><strong>.htaccess<\/strong> Files<\/h2>\n\n\n\n<p>A 403 error can also be caused by incorrect configuration in an .htaccess file. These files are very powerful, but a single incorrect directive can result in certain resources or visitors being unintentionally blocked.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1 \u2013 Identify A 403 Arror Related To <code>.htaccess<\/code><\/h3>\n\n\n\n<p>The message displayed in the browser will usually be similar to: \u201c<strong>Forbidden \u2013 You are not authorized to access this resource.<\/strong>\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2 \u2013 Differentiate From A WAF Block<\/h3>\n\n\n\n<p>As with permission errors, this type of error <strong>only appears in access logs, not in WAF logs<\/strong>.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Access log: Domains -&gt; Access log<\/strong>.<\/li>\n\n\n\n<li><strong>WAF log: Security -&gt; Firewall protection history<\/strong>.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3 \u2013 Check All Relevant<code>.htaccess<\/code> Files<\/h3>\n\n\n\n<p>Use the <strong>File Manager: Files -&gt; File Manager<\/strong>.<\/p>\n\n\n\n<p>Locate all<code>.htaccess<\/code> files located between the <strong>document root<\/strong> (visible in <strong>Domains -&gt; Domain Management<\/strong>) <strong>and the directory of the affected page<\/strong>.<\/p>\n\n\n\n<p>Common errors include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An incorrectly formatted rule (incorrect syntax).<\/li>\n\n\n\n<li>An IP block (<code>Deny from<\/code> \/ <code>Require not<\/code>).<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip.png\"><img loading=\"lazy\" decoding=\"async\" width=\"499\" height=\"315\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip.png\" alt=\"IP block\" class=\"wp-image-21420\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip.png 499w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip-300x189.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip-50x32.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip-60x38.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-ip-100x63.png 100w\" sizes=\"auto, (max-width: 499px) 100vw, 499px\" \/><\/a><\/figure><\/div>\n\n\n<ul class=\"wp-block-list\">\n<li>User-agent filtering.<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome.png\"><img loading=\"lazy\" decoding=\"async\" width=\"556\" height=\"323\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome.png\" alt=\"User-agent filtering\" class=\"wp-image-21422\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome.png 556w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome-300x174.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome-50x29.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome-60x35.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/htaccess-blocage-chrome-100x58.png 100w\" sizes=\"auto, (max-width: 556px) 100vw, 556px\" \/><\/a><\/figure><\/div>\n\n\n<ul class=\"wp-block-list\">\n<li>An incorrect redirection directive.<\/li>\n<\/ul>\n\n\n\n<p>You will find a more detailed guide on managing blocks using .htaccess in our article <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-use-htaccess-to-filter-out-malicious-robots-and-requests\/\" target=\"_blank\" rel=\"noreferrer noopener\">How to Use .htaccess to Filter Out Malicious Robots and Requests<\/a>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Step 4 \u2013 Modify or Remove Problematic Rules<\/h4>\n\n\n\n<p>In <strong>File Manager<\/strong>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Right-click <\/strong>on the suspicious<code>.htaccess<\/code> file.<\/li>\n\n\n\n<li>Select <strong>Edit File<\/strong>.<\/li>\n\n\n\n<li>Determine which rules may be causing a 403 error, <strong>then correct or temporarily comment<\/strong> them out (<code>#<\/code> at the beginning of the line).<\/li>\n<\/ol>\n\n\n\n<p>Remember to save your changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"etape-4-videz-la-cache-lscache\">Step 5 \u2014 Clear the LSCache Cache<\/h3>\n\n\n\n<p>For the rules to take effect, it may be necessary in <a href=\"https:\/\/kb.n0c.com\/en\/glossaire\/n0c\/\" target=\"_blank\" rel=\"noreferrer noopener\">N0C<\/a> to clear the cache for the domain in question (see the article <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-use-lscache\/\" target=\"_blank\" rel=\"noreferrer noopener\">How to use LSCache<\/a>).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 6 \u2014 Reload the Page and Check the Result<\/h3>\n\n\n\n<p>Once the rules have been modified and the cache cleared, <strong>refresh the page in question in your browser<\/strong> to see if the 403 error has disappeared.<\/p>\n\n\n\n<p>If the error persists:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review the .<code>.htaccess<\/code> files further up in the directory tree again.<\/li>\n\n\n\n<li>Check that no other directives (or browser cache) are continuing to interfere.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"software-functions\">Software Functions<\/h2>\n\n\n\n<p>Some 403 errors are not caused by the server or security rules, <strong>but are generated directly by your site&#8217;s code<\/strong>. For example, a condition in a PHP file may decide to block access to a resource based on business logic or an unexpected state (such as <code>header()<\/code> in PHP).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1 \u2013 Enable PHP Error Display<\/h3>\n\n\n\n<p>To facilitate diagnosis, start by enabling error display in your code. This can be done using one of the following methods.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enable display in <code><strong>N0C<\/strong> -&gt; <strong>Langages<\/strong> -&gt; <strong>PHP<\/strong> -&gt; <strong>Options<\/strong> -&gt; <strong>display_errors<\/strong><\/code> to see the errors directly in the page.<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-1024x40.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"40\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-1024x40.png\" alt=\"Seeing the errors directly in the page\" class=\"wp-image-21371\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-1024x40.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-300x12.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-768x30.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-50x2.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-60x2.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors-100x4.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/display_errors.png 1343w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<ul class=\"wp-block-list\">\n<li>By enabling error logging to a file by activating it in <code>N0C -&gt; Langages -&gt; PHP -&gt; Options -&gt; log_errors<\/code> and by chosing a log file in <code>N0C -&gt; Langages -&gt; PHP -&gt; Options -&gt; error_log<\/code>.<\/li>\n<\/ul>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-1024x40.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"40\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-1024x40.png\" alt=\"Enabling error logging to a file\" class=\"wp-image-21373\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-1024x40.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-300x12.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-768x30.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-50x2.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-60x2.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors-100x4.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/log_errors.png 1341w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-1024x40.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"40\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-1024x40.png\" alt=\"Error log filename\" class=\"wp-image-21375\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-1024x40.png 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-300x12.png 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-768x30.png 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-50x2.png 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-60x2.png 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log-100x4.png 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/error_log.png 1341w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<ul class=\"wp-block-list\">\n<li>By placing these lines at the top of your input file (often index.php) or at a strategic execution point:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>ini_set('display_errors', '1');\nini_set('display_startup_errors', '1');\nerror_reporting(E_ALL);<\/code><\/pre>\n\n\n\n<p>This will make it easier to spot logical errors or unexpected behavior.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2 \u2013 Trace the Execution of the Code<\/h3>\n\n\n\n<p>Add temporary instructions (<code>echo<\/code>, <code>var_dump()<\/code>, <code>die()<\/code>, etc.) at various points in your code to <strong>track the execution flow<\/strong> from the entry point to the location where the error is generated.<\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>echo 'Checkpoint 1';\n...\necho 'Checkpoint 2';<\/code><\/pre>\n\n\n\n<p>Continue in this manner, function by function, until the last point where the code executes normally.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3 \u2013 Identify the Source of the 403 Response<\/h3>\n\n\n\n<p>You will often end up finding a condition that triggers a voluntary block, such as:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>if ($sky === 'blue') {\n    http_response_code(403);\n    exit;\n}<\/code><\/pre>\n\n\n\n<p>These instructions are sometimes added by a developer or an extension to control access to certain resources or for testing purposes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 4 \u2013 Correct or Adjust the Application Logic<\/h3>\n\n\n\n<p>Once the blockage has been located:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>correct the condition if it is too restrictive or inappropriate;<\/li>\n\n\n\n<li>add logs to better understand the context; and<\/li>\n\n\n\n<li>check user permissions and roles if the logic is based on them.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 5 \u2013 Clean Up the Code After Correction<\/h3>\n\n\n\n<p>Once the cause of the blockage has been identified and corrected, <strong>remember to remove all debugging elements added during diagnosis<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Remove all <code>echo<\/code>, <code>var_dump()<\/code>, ou <code>die()<\/code> statements.<\/li>\n\n\n\n<li>Reset the error display settings if you have modified them, such as <code>ini_set('display_errors', '0')<\/code>.<\/li>\n\n\n\n<li>If you have modified sensitive files, remember to <strong>clear the cache<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p>This will prevent technical information from being exposed in production or disrupting the normal operation of the site.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Note \u2014 If You Are Using a Framework or CMS<\/h3>\n\n\n\n<p>Many development environments (frameworks such as <strong>Laravel<\/strong> or <strong>Symfony<\/strong>) or content management systems (CMS such as <strong>WordPress<\/strong>, <strong>PrestaShop<\/strong>) use <strong>custom error handlers, middleware, or internal access control systems<\/strong>. In these cases:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The <code>header()<\/code> function can be encapsulated or hidden.<\/li>\n\n\n\n<li>403 errors can be returned by a component such as a router, internal firewall, or controller.<\/li>\n<\/ul>\n\n\n\n<p>In these contexts, it is recommended to enable the <strong>native debug logs<\/strong> of the system in question (e.g., <code>APP_DEBUG=true<\/code>in Laravel<code>.env<\/code>, WP_DEBUG in WordPress, etc.) and to use the tools provided by the framework to trace behavior (monolog, debugbar, etc.).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"csf\"><strong>CSF<\/strong><\/h2>\n\n\n\n<p>On our N0C infrastructure, one of the <strong>CSF (ConfigServer Security &amp; Firewall) <\/strong>firewalls is used to protect servers against behavior considered abusive or suspicious. Among other things, this includes an excessive number of failed connection attempts (e.g., repeated attempts to connect to IMAP, POP, SMTP, SSH, FTP, or even via the N0C interface).<\/p>\n\n\n\n<p>In these cases, the user&#8217;s IP address may be <strong>blocked by CSF<\/strong>, resulting in a <strong>403 error<\/strong> on all attempts to access the servers, including websites, email messages, and the customer area.<\/p>\n\n\n\n<p>Fortunately, N0C offers an easy-to-use <strong>self-unblock feature<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 1 \u2013 You Encounter A 403 Error<\/h3>\n\n\n\n<p>Are you seeing a 403 error on your website, in addition to suddenly being unable to access your email account (webmail), synchronize your emails, FTP, or N0C interface? This may be due to your IP address being blocked by CSF. For more details, please refer to the article <a href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-open-a-roundcube-email\/\">How to Open a Roundcube Email<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Step 2 \u2013 Differentiate From a WAF Block<\/h3>\n\n\n\n<p>As with permission errors, CSF blocks <strong>do not appear in the WAF log<\/strong>, but only in the <strong>access logs<\/strong>.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Access log: Domains -&gt; Access log.<\/strong><\/li>\n\n\n\n<li><strong>WAF log: Security -&gt; Firewall protection history.<\/strong><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Step 3 \u2013 Check Your Email (Webmail) For an Auto-Unblock Message<\/h3>\n\n\n\n<p>Please go to the following address: <code>https:\/\/[yourdomain.com]\/webmail<\/code>.<\/p>\n\n\n\n<p>If your IP address is blocked by CSF, a <strong>custom error page<\/strong> will be displayed with an<strong> information message <\/strong>and a<strong> self-unblocking form via CAPTCHA<\/strong>.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><a href=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-1024x672.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"672\" src=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-1024x672.jpg\" alt=\"Custom error message if IP address blocked by a CSF\" class=\"wp-image-21361\" srcset=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-1024x672.jpg 1024w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-300x197.jpg 300w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-768x504.jpg 768w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-50x33.jpg 50w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-60x39.jpg 60w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped-100x66.jpg 100w, https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/captcha-cropped.jpg 1072w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/a><\/figure><\/div>\n\n\n<h3 class=\"wp-block-heading\">Step 4 \u2013 Complete the Self-Unblocking Form<\/h3>\n\n\n\n<p>Follow the instructions on the page to <strong>confirm that you are a legitimate human <\/strong>user via a simple CAPTCHA. Once the form has been submitted, <strong>your IP address will be unblocked immediately<\/strong> if the request is compliant.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>403 errors can have several causes: a restriction imposed by the application firewall (WAF), a security block by CSF, incorrect file permissions, an incorrectly formulated .htaccess rule, or even behavior defined in your application code.<\/p>\n\n\n\n<p>With the diagnostic tools available in your N0C control panel (access logs, WAF logs, file manager, and unblocking tools), you have all the resources you need to <strong>quickly identify the cause and apply the appropriate corrective actions<\/strong> while maintaining a good level of security.<\/p>\n\n\n\n<p>If you have any doubts or persistent difficulties, please consult the additional documentation available elsewhere in the <a href=\"https:\/\/kb.n0c.com\/en\/\" target=\"_blank\" rel=\"noreferrer noopener\">knowledge base<\/a> or contact technical support.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction A 403 error means that access to a page or resource on your website is prohibited. It can occur for a variety of reasons. But do not worry: it can usually be fixed quickly. In this article, we will show you how to diagnose and resolve a 403 error&#8230;.<\/p>\n","protected":false},"author":7,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"ht-kb-category":[376],"ht-kb-tag":[],"class_list":["post-21441","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-technical_advice"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.9 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Manage 403 Errors On Your N0C Hosting - N0C KB<\/title>\n<meta name=\"description\" content=\"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Manage 403 Errors On Your N0C Hosting - N0C KB\" \/>\n<meta property=\"og:description\" content=\"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/\" \/>\n<meta property=\"og:site_name\" content=\"N0C KB\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-12T18:46:30+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/\",\"url\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/\",\"name\":\"How to Manage 403 Errors On Your N0C Hosting - N0C KB\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kb.n0c.com\\\/wp-content\\\/uploads\\\/2025\\\/09\\\/waf-403-1024x151.png\",\"datePublished\":\"2025-09-09T13:01:24+00:00\",\"dateModified\":\"2025-09-12T18:46:30+00:00\",\"description\":\"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kb.n0c.com\\\/wp-content\\\/uploads\\\/2025\\\/09\\\/waf-403-1024x151.png\",\"contentUrl\":\"https:\\\/\\\/kb.n0c.com\\\/wp-content\\\/uploads\\\/2025\\\/09\\\/waf-403-1024x151.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/how-to-manage-403-errors-on-your-n0c-hosting\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/kb.n0c.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\\\/\\\/kb.n0c.com\\\/en\\\/knowledge-base\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"How to Manage 403 Errors On Your N0C Hosting\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kb.n0c.com\\\/#website\",\"url\":\"https:\\\/\\\/kb.n0c.com\\\/\",\"name\":\"N0C KB\",\"description\":\"Official documentation of the N0C hosting platform\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kb.n0c.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Manage 403 Errors On Your N0C Hosting - N0C KB","description":"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/","og_locale":"en_US","og_type":"article","og_title":"How to Manage 403 Errors On Your N0C Hosting - N0C KB","og_description":"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.","og_url":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/","og_site_name":"N0C KB","article_modified_time":"2025-09-12T18:46:30+00:00","og_image":[{"url":"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png","type":"","width":"","height":""}],"twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/","url":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/","name":"How to Manage 403 Errors On Your N0C Hosting - N0C KB","isPartOf":{"@id":"https:\/\/kb.n0c.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/#primaryimage"},"image":{"@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/#primaryimage"},"thumbnailUrl":"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png","datePublished":"2025-09-09T13:01:24+00:00","dateModified":"2025-09-12T18:46:30+00:00","description":"How to diagnose and resolve a 403 error. It can be done easily with the tools available in N0C control panel.","breadcrumb":{"@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/#primaryimage","url":"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png","contentUrl":"https:\/\/kb.n0c.com\/wp-content\/uploads\/2025\/09\/waf-403-1024x151.png"},{"@type":"BreadcrumbList","@id":"https:\/\/kb.n0c.com\/en\/knowledge-base\/how-to-manage-403-errors-on-your-n0c-hosting\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/kb.n0c.com\/"},{"@type":"ListItem","position":2,"name":"Articles","item":"https:\/\/kb.n0c.com\/en\/knowledge-base\/"},{"@type":"ListItem","position":3,"name":"How to Manage 403 Errors On Your N0C Hosting"}]},{"@type":"WebSite","@id":"https:\/\/kb.n0c.com\/#website","url":"https:\/\/kb.n0c.com\/","name":"N0C KB","description":"Official documentation of the N0C hosting platform","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kb.n0c.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb\/21441","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/comments?post=21441"}],"version-history":[{"count":44,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb\/21441\/revisions"}],"predecessor-version":[{"id":21544,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb\/21441\/revisions\/21544"}],"wp:attachment":[{"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/media?parent=21441"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb-category?post=21441"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/kb.n0c.com\/en\/wp-json\/wp\/v2\/ht-kb-tag?post=21441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}