{"id":2424,"date":"2026-09-21T09:02:19","date_gmt":"2026-09-21T06:02:19","guid":{"rendered":"https:\/\/www.namebox.ro\/blog\/?p=2424"},"modified":"2026-09-22T08:35:57","modified_gmt":"2026-09-22T05:35:57","slug":"eroare-403-modsecurity","status":"publish","type":"post","link":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/","title":{"rendered":"ModSecurity \u00een cPanel \u0219i eroarea 403"},"content":{"rendered":"<p><strong>ModSecurity \u00een cPanel<\/strong> reprezint\u0103 unul dintre nivelurile de protec\u021bie utilizate pentru filtrarea cererilor HTTP suspecte \u00eenainte ca acestea s\u0103 ajung\u0103 la aplica\u021bia website-ului.<\/p>\n<p>Pe infrastructura NameBox, aceast\u0103 protec\u021bie lucreaz\u0103 \u00eempreun\u0103 cu tehnologii precum <strong>LiteSpeed Web Server, Imunify360, CloudLinux \u0219i cPanel<\/strong> pentru a reduce riscul exploat\u0103rii vulnerabilit\u0103\u021bilor \u0219i al accesului neautorizat.<\/p>\n<p>\u00cen anumite situa\u021bii, \u00eens\u0103, o cerere legitim\u0103 poate sem\u0103na cu un atac \u0219i poate fi blocat\u0103. Unul dintre simptomele \u00eent\u00e2lnite este eroarea <strong>403 Forbidden<\/strong>.<\/p>\n<p>\u00cen acest articol explic\u0103m ce este ModSecurity, cum func\u021bioneaz\u0103 \u00eentr-un server cPanel cu LiteSpeed \u0219i Imunify360, cum identifici un posibil false positive \u0219i de ce nu este recomandat\u0103 dezactivarea permanent\u0103 a protec\u021biei.<\/p>\n<h2>Ce este ModSecurity?<\/h2>\n<p><strong>ModSecurity<\/strong> este o tehnologie de tip <strong>Web Application Firewall \u2013 WAF<\/strong> utilizat\u0103 pentru analizarea traficului HTTP \u0219i HTTPS care ajunge la website.<\/p>\n<p>\u00cen loc s\u0103 permit\u0103 automat fiecare request, sistemul \u00eel poate compara cu un set de reguli de securitate.<\/p>\n<p>Procesul poate fi reprezentat simplificat astfel:<\/p>\n<pre>\r\nVizitator\r\n   \u2193\r\nRequest HTTP \/ HTTPS\r\n   \u2193\r\nLiteSpeed + ModSecurity \/ WAF\r\n   \u2193\r\nReguli de securitate\r\n   \u2193\r\nRequest permis sau blocat\r\n   \u2193\r\nWebsite \/ WordPress \/ magazin online\r\n<\/pre>\n<p>Dac\u0103 o cerere corespunde unei reguli considerate periculoase, aceasta poate fi blocat\u0103 \u00eenainte ca aplica\u021bia s\u0103 o proceseze.<\/p>\n<h2>Ce tipuri de atacuri poate identifica ModSecurity?<\/h2>\n<p>Capacitatea exact\u0103 depinde de regulile instalate pe server, \u00eens\u0103 un WAF bazat pe ModSecurity poate analiza cereri asociate unor atacuri precum:<\/p>\n<ul>\n<li>SQL Injection;<\/li>\n<li>Cross-Site Scripting \u2013 XSS;<\/li>\n<li>Command Injection;<\/li>\n<li>Local File Inclusion;<\/li>\n<li>Remote File Inclusion;<\/li>\n<li>request-uri HTTP construite anormal;<\/li>\n<li>anumite \u00eencerc\u0103ri de exploatare a aplica\u021biilor web;<\/li>\n<li>upload-uri sau payload-uri suspecte.<\/li>\n<\/ul>\n<p>ModSecurity nu \u201e\u0219tie\u201d automat dac\u0103 un utilizator este atacator. Acesta analizeaz\u0103 request-ul pe baza regulilor de securitate existente.<\/p>\n<h2>Ce este un WAF?<\/h2>\n<p><strong>WAF \u2013 Web Application Firewall<\/strong> este un sistem de protec\u021bie pozi\u021bionat \u00eentre utilizator \u0219i aplica\u021bia web.<\/p>\n<p>Un firewall de re\u021bea \u0219i un WAF nu sunt acela\u0219i lucru.<\/p>\n<p>Un firewall clasic poate controla conexiuni \u0219i porturi precum:<\/p>\n<pre>\r\n22   \u2192 SSH\r\n25   \u2192 SMTP\r\n80   \u2192 HTTP\r\n443  \u2192 HTTPS\r\n<\/pre>\n<p>Un WAF analizeaz\u0103 ceea ce se transmite efectiv prin HTTP sau HTTPS.<\/p>\n<p>De exemplu, dou\u0103 request-uri pot ajunge ambele pe portul 443, \u00eens\u0103 unul poate fi o accesare normal\u0103 a unei pagini, iar cel\u0103lalt poate con\u021bine un payload specific unui SQL Injection.<\/p>\n<h2>Cum func\u021bioneaz\u0103 ModSecurity \u00eempreun\u0103 cu LiteSpeed?<\/h2>\n<p>Serverele shared NameBox utilizeaz\u0103 <strong>LiteSpeed Web Server<\/strong>.<\/p>\n<p>LiteSpeed include propriul motor de procesare compatibil cu regulile ModSecurity, astfel \u00eenc\u00e2t protec\u021bia WAF poate func\u021biona \u0219i \u00eentr-un mediu LiteSpeed.<\/p>\n<p>LiteSpeed este compatibil cu seturi de reguli precum:<\/p>\n<ul>\n<li>OWASP;<\/li>\n<li>Imunify360;<\/li>\n<li>Comodo;<\/li>\n<li>Atomicorp;<\/li>\n<li>reguli personalizate.<\/li>\n<\/ul>\n<p>\u00centr-un server cPanel, regulile ModSecurity sunt administrate \u00een mod normal prin integrarea disponibil\u0103 \u00een WHM, f\u0103r\u0103 s\u0103 fie necesar\u0103 configurarea lor separat \u00een interfa\u021ba LiteSpeed.<\/p>\n<h2>Unde intervine Imunify360?<\/h2>\n<p><strong>Imunify360<\/strong> este o platform\u0103 de securitate pentru serverele de hosting \u0219i ofer\u0103 mai multe componente de protec\u021bie.<\/p>\n<p>Printre acestea se num\u0103r\u0103:<\/p>\n<ul>\n<li>Web Application Firewall;<\/li>\n<li>reguli de protec\u021bie pentru aplica\u021biile web;<\/li>\n<li>scanare malware;<\/li>\n<li>protec\u021bie \u00eempotriva anumitor atacuri automate;<\/li>\n<li>monitorizarea evenimentelor de securitate;<\/li>\n<li>protec\u021bie la nivelul fi\u0219ierelor;<\/li>\n<li>mecanisme de reputa\u021bie \u0219i filtrare.<\/li>\n<\/ul>\n<p>Imunify360 poate utiliza un ruleset compatibil ModSecurity pentru identificarea request-urilor periculoase.<\/p>\n<p>Astfel, \u00eentr-o configura\u021bie cu LiteSpeed, fluxul poate fi simplificat astfel:<\/p>\n<pre>\r\nInternet\r\n   \u2193\r\nLiteSpeed\r\n   \u2193\r\nWAF \/ ModSecurity\r\n   \u2193\r\nReguli Imunify360\r\n   \u2193\r\nAplica\u021bia website-ului\r\n<\/pre>\n<p>LiteSpeed proceseaz\u0103 request-ul, iar regulile de securitate pot decide dac\u0103 acesta trebuie permis sau blocat.<\/p>\n<h2>ModSecurity \u0219i Imunify360 sunt acela\u0219i lucru?<\/h2>\n<p>Nu.<\/p>\n<p><strong>ModSecurity<\/strong> reprezint\u0103 motorul sau mecanismul prin care pot fi evaluate regulile WAF.<\/p>\n<p><strong>Imunify360<\/strong> este o platform\u0103 mai complex\u0103 de securitate care poate furniza \u0219i utiliza reguli WAF, dar include \u0219i alte componente precum scanarea malware.<\/p>\n<p>O compara\u021bie simplificat\u0103 ar fi:<\/p>\n<pre>\r\nModSecurity = motor de analiz\u0103 WAF\r\n\r\nImunify360 = platform\u0103 de securitate + reguli WAF + malware scanner + alte mecanisme\r\n<\/pre>\n<p>\u00cen infrastructurile moderne, motorul exact care execut\u0103 regulile poate varia. Important pentru utilizator este c\u0103 request-urile sunt analizate \u00eenainte de a ajunge la aplica\u021bie.<\/p>\n<h2>Ce rol are CloudLinux?<\/h2>\n<p><strong>CloudLinux<\/strong> are un rol diferit fa\u021b\u0103 de ModSecurity \u0219i Imunify360.<\/p>\n<p>Pe serverele shared NameBox, CloudLinux ajut\u0103 la izolarea conturilor de g\u0103zduire \u0219i la controlul resurselor utilizate de fiecare cont.<\/p>\n<p>De exemplu, poate controla sau monitoriza resurse precum:<\/p>\n<ul>\n<li>CPU;<\/li>\n<li>memorie RAM;<\/li>\n<li>I\/O;<\/li>\n<li>IOPS;<\/li>\n<li>Entry Processes;<\/li>\n<li>num\u0103rul de procese.<\/li>\n<\/ul>\n<p>CloudLinux nu \u00eenlocuie\u0219te ModSecurity.<\/p>\n<p>Cele dou\u0103 tehnologii rezolv\u0103 probleme diferite:<\/p>\n<pre>\r\nLiteSpeed   \u2192 server web \u0219i performan\u021b\u0103\r\nModSecurity \u2192 filtrarea request-urilor web\r\nImunify360  \u2192 securitate WAF + anti-malware\r\nCloudLinux  \u2192 izolare conturi \u0219i control resurse\r\ncPanel      \u2192 administrarea serviciilor\r\n<\/pre>\n<h2>Cum poate ModSecurity genera eroarea 403?<\/h2>\n<p>Atunci c\u00e2nd o regul\u0103 consider\u0103 c\u0103 request-ul reprezint\u0103 un risc, serverul poate r\u0103spunde cu:<\/p>\n<pre>403 Forbidden<\/pre>\n<p>Acest lucru \u00eenseamn\u0103 c\u0103 serverul a \u00een\u021beles cererea, dar accesul a fost refuzat.<\/p>\n<p>De exemplu, o cerere de tip POST poate con\u021bine un text asem\u0103n\u0103tor cu o comand\u0103 SQL:<\/p>\n<pre>SELECT * FROM users<\/pre>\n<p>\u00centr-un formular destinat programatorilor sau \u00eentr-un articol tehnic, acest text poate fi perfect legitim.<\/p>\n<p>Totu\u0219i, \u00eentr-un alt context poate sem\u0103na cu o tentativ\u0103 SQL Injection.<\/p>\n<p>Dac\u0103 o regul\u0103 este foarte strict\u0103, request-ul legitim poate fi blocat. Aceast\u0103 situa\u021bie este cunoscut\u0103 sub numele de:<\/p>\n<p><strong>false positive<\/strong>.<\/p>\n<h2>Ce este un false positive?<\/h2>\n<p>Un false positive apare atunci c\u00e2nd sistemul de securitate identific\u0103 o activitate legitim\u0103 drept poten\u021bial atac.<\/p>\n<p>De exemplu, problema poate ap\u0103rea atunci c\u00e2nd:<\/p>\n<ul>\n<li>salvezi un articol cu fragmente de cod;<\/li>\n<li>trimi\u021bi un formular care con\u021bine anumite caractere speciale;<\/li>\n<li>un plugin trimite un request POST complex;<\/li>\n<li>un page builder salveaz\u0103 cantit\u0103\u021bi mari de HTML sau JavaScript;<\/li>\n<li>un API transmite JSON cu anumite expresii;<\/li>\n<li>un import trimite date care coincid cu o regul\u0103 de securitate.<\/li>\n<\/ul>\n<p>Acest lucru nu \u00eenseamn\u0103 c\u0103 ModSecurity trebuie dezactivat complet.<\/p>\n<p>Trebuie identificat\u0103 regula care a blocat request-ul \u0219i analizat dac\u0103 este \u00eentr-adev\u0103r un false positive.<\/p>\n<h2>Nu orice eroare 403 este cauzat\u0103 de ModSecurity<\/h2>\n<p>Este foarte important s\u0103 nu presupunem automat c\u0103 fiecare eroare 403 este provocat\u0103 de ModSecurity.<\/p>\n<p>Un <strong>403 Forbidden<\/strong> poate ap\u0103rea \u0219i din alte motive.<\/p>\n<p>Printre acestea se num\u0103r\u0103:<\/p>\n<ul>\n<li>permisiuni incorecte ale fi\u0219ierelor;<\/li>\n<li>reguli .htaccess;<\/li>\n<li>restric\u021bii configurate \u00een aplica\u021bie;<\/li>\n<li>blocarea adresei IP;<\/li>\n<li>protec\u021bii Imunify360;<\/li>\n<li>firewall;<\/li>\n<li>reguli personalizate de securitate;<\/li>\n<li>accesarea unui director protejat;<\/li>\n<li>pluginuri WordPress de securitate.<\/li>\n<\/ul>\n<p>Din acest motiv trebuie analizat\u0103 cauza \u00eenainte de modificarea configura\u021biei.<\/p>\n<h2>Cum \u00ee\u021bi dai seama dac\u0103 ModSecurity blocheaz\u0103 request-ul?<\/h2>\n<p>Un indiciu important este modul \u00een care apare problema.<\/p>\n<p>De exemplu:<\/p>\n<ul>\n<li>website-ul func\u021bioneaz\u0103 normal;<\/li>\n<li>wp-admin func\u021bioneaz\u0103;<\/li>\n<li>po\u021bi naviga \u00eentre pagini;<\/li>\n<li>dar o anumit\u0103 opera\u021biune produce 403.<\/li>\n<\/ul>\n<p>Exemplu:<\/p>\n<pre>\r\nAccesezi wp-admin           \u2192 func\u021bioneaz\u0103\r\nEditezi articolul           \u2192 func\u021bioneaz\u0103\r\nApe\u0219i Update                \u2192 403 Forbidden\r\n<\/pre>\n<p>\u00centr-o asemenea situa\u021bie este posibil ca request-ul POST utilizat la salvare s\u0103 fi fost blocat de o regul\u0103 WAF.<\/p>\n<p>Totu\u0219i, confirmarea trebuie realizat\u0103 \u00een logurile serverului.<\/p>\n<h2>ModSecurity \u00een cPanel<\/h2>\n<p>Dac\u0103 furnizorul permite aceast\u0103 func\u021bie, utilizatorul poate g\u0103si ModSecurity \u00een:<\/p>\n<p><strong>cPanel \u2192 Security \u2192 ModSecurity<\/strong><\/p>\n<p>Interfa\u021ba permite activarea sau dezactivarea protec\u021biei pentru domeniile asociate contului.<\/p>\n<p>cPanel recomand\u0103 explicit men\u021binerea ModSecurity activ pentru toate domeniile \u0219i dezactivarea acestuia doar temporar atunci c\u00e2nd este necesar\u0103 depanarea unei probleme.<\/p>\n<h2>Este recomandat s\u0103 dezactivezi ModSecurity?<\/h2>\n<p>Nu permanent.<\/p>\n<p>Dezactivarea ModSecurity elimin\u0103 regulile WAF aplicate domeniului \u0219i reduce nivelul de protec\u021bie al website-ului.<\/p>\n<p>Dac\u0103 suspectezi un false positive, dezactivarea poate fi utilizat\u0103 <strong>temporar<\/strong> ca test.<\/p>\n<p>Un scenariu de diagnostic poate fi:<\/p>\n<pre>\r\nOpera\u021biunea produce 403\r\n        \u2193\r\nModSecurity este dezactivat temporar\r\n        \u2193\r\nOpera\u021biunea este repetat\u0103\r\n        \u2193\r\nFunc\u021bioneaz\u0103\r\n        \u2193\r\nModSecurity este reactivat\r\n        \u2193\r\nSe verific\u0103 regula care a produs blocarea\r\n<\/pre>\n<p>Dac\u0103 problema dispare doar atunci c\u00e2nd ModSecurity este dezactivat, avem un indiciu puternic c\u0103 o regul\u0103 WAF trebuie investigat\u0103.<\/p>\n<p>Dup\u0103 test, protec\u021bia trebuie reactivat\u0103.<\/p>\n<h2>De ce nu trebuie l\u0103sat ModSecurity dezactivat?<\/h2>\n<p>Un website poate con\u021bine vulnerabilit\u0103\u021bi despre care administratorul nu \u0219tie \u00eenc\u0103.<\/p>\n<p>De exemplu, un plugin WordPress poate avea o vulnerabilitate care permite trimiterea unui request mali\u021bios.<\/p>\n<p>Un WAF poate bloca anumite tentative \u00eenainte ca acestea s\u0103 ajung\u0103 la plugin.<\/p>\n<p>Dac\u0103 ModSecurity este dezactivat permanent, acest nivel suplimentar de protec\u021bie nu mai exist\u0103.<\/p>\n<p>Din acest motiv, solu\u021bia corect\u0103 pentru un false positive este identificarea regulii \u0219i aplicarea unei excep\u021bii c\u00e2t mai precise, nu dezactivarea \u00eentregului sistem de securitate.<\/p>\n<h2>Cum este identificat\u0103 regula care a blocat request-ul?<\/h2>\n<p>La nivel de server, evenimentele ModSecurity pot fi analizate din WHM.<\/p>\n<p>Administratorul serverului poate utiliza:<\/p>\n<p><strong>WHM \u2192 Security Center \u2192 ModSecurity Tools<\/strong><\/p>\n<p>Interfa\u021ba permite verificarea evenimentelor generate de reguli.<\/p>\n<p>\u00centr-un astfel de eveniment pot exista informa\u021bii precum:<\/p>\n<ul>\n<li>Rule ID;<\/li>\n<li>domeniul;<\/li>\n<li>URL-ul solicitat;<\/li>\n<li>IP-ul clientului;<\/li>\n<li>data \u0219i ora;<\/li>\n<li>motivul bloc\u0103rii;<\/li>\n<li>regula care a fost declan\u0219at\u0103.<\/li>\n<\/ul>\n<p>Aceste informa\u021bii sunt mult mai utile dec\u00e2t dezactivarea aleatorie a protec\u021biilor.<\/p>\n<h2>Ce este Rule ID?<\/h2>\n<p>Fiecare regul\u0103 ModSecurity poate avea un identificator.<\/p>\n<p>De exemplu:<\/p>\n<pre>Rule ID: 123456<\/pre>\n<p>Dac\u0103 o anumit\u0103 regul\u0103 produce un false positive, administratorul poate analiza exact regula respectiv\u0103.<\/p>\n<p>\u00cen func\u021bie de situa\u021bie, se poate decide:<\/p>\n<ul>\n<li>c\u0103 request-ul este \u00eentr-adev\u0103r mali\u021bios;<\/li>\n<li>c\u0103 aplica\u021bia trebuie modificat\u0103;<\/li>\n<li>c\u0103 regula trebuie ajustat\u0103;<\/li>\n<li>c\u0103 este necesar\u0103 o excep\u021bie specific\u0103.<\/li>\n<\/ul>\n<p>Nu este recomandat s\u0103 dezactivezi reguli f\u0103r\u0103 s\u0103 \u00een\u021belegi ce protec\u021bie ofer\u0103.<\/p>\n<h2>Ce informa\u021bii sunt utile c\u00e2nd raportezi o eroare 403?<\/h2>\n<p>Dac\u0103 un request este blocat pe un serviciu NameBox, pentru identificarea rapid\u0103 a cauzei sunt utile urm\u0103toarele informa\u021bii:<\/p>\n<ul>\n<li>domeniul afectat;<\/li>\n<li>URL-ul exact unde apare problema;<\/li>\n<li>data \u0219i ora aproximativ\u0103;<\/li>\n<li>adresa IP de la care ai realizat opera\u021biunea;<\/li>\n<li>opera\u021biunea realizat\u0103 \u00eenainte de apari\u021bia erorii;<\/li>\n<li>mesajul complet de eroare sau o captur\u0103 de ecran.<\/li>\n<\/ul>\n<p>Adresa IP poate fi verificat\u0103 acces\u00e2nd:<\/p>\n<pre>https:\/\/ip.namebox.ro\/<\/pre>\n<p>Ora exact\u0103 este foarte important\u0103 deoarece permite corelarea request-ului cu evenimentul din logurile serverului.<\/p>\n<h2>Exemplu: WordPress afi\u0219eaz\u0103 403 c\u00e2nd salvezi o pagin\u0103<\/h2>\n<p>S\u0103 presupunem c\u0103 utilizezi WordPress \u0219i Elementor.<\/p>\n<p>Po\u021bi:<\/p>\n<ul>\n<li>intra \u00een wp-admin;<\/li>\n<li>deschide pagina;<\/li>\n<li>edita con\u021binutul;<\/li>\n<\/ul>\n<p>dar \u00een momentul \u00een care ape\u0219i:<\/p>\n<p><strong>Update<\/strong><\/p>\n<p>prime\u0219ti:<\/p>\n<pre>403 Forbidden<\/pre>\n<p>Nu trebuie s\u0103 concluzionezi imediat c\u0103 Elementor este defect.<\/p>\n<p>Request-ul transmis de editor poate con\u021bine:<\/p>\n<ul>\n<li>HTML;<\/li>\n<li>CSS;<\/li>\n<li>JavaScript;<\/li>\n<li>JSON;<\/li>\n<li>URL-uri;<\/li>\n<li>fragmente de cod.<\/li>\n<\/ul>\n<p>Una dintre aceste valori poate coincide cu o regul\u0103 de securitate.<\/p>\n<p>Administratorul poate verifica Rule ID-ul asociat request-ului \u0219i poate stabili dac\u0103 avem un false positive.<\/p>\n<h2>Exemplu: formularul de contact returneaz\u0103 403<\/h2>\n<p>Un alt scenariu poate ap\u0103rea atunci c\u00e2nd un utilizator introduce \u00eentr-un formular un text care con\u021bine anumite expresii tehnice.<\/p>\n<p>De exemplu:<\/p>\n<pre>\r\nAvem problema cu SELECT * FROM users\r\n<\/pre>\n<p>Pentru utilizator este doar text.<\/p>\n<p>Pentru o regul\u0103 WAF poate sem\u0103na cu un fragment SQL.<\/p>\n<p>Dac\u0103 regula consider\u0103 request-ul periculos, formularul poate fi blocat.<\/p>\n<p>Acesta este motivul pentru care regulile trebuie analizate \u00een context, nu eliminate f\u0103r\u0103 verificare.<\/p>\n<h2>Imunify360 poate bloca \u0219i alte tipuri de activitate<\/h2>\n<p>Este important s\u0103 nu asociem toate bloc\u0103rile cu ModSecurity.<\/p>\n<p>Imunify360 include mai multe componente de securitate, iar o adres\u0103 IP sau un request poate fi afectat \u0219i de alte mecanisme.<\/p>\n<p>Din acest motiv, atunci c\u00e2nd investig\u0103m un incident trebuie s\u0103 diferen\u021biem:<\/p>\n<pre>\r\nRequest blocat de WAF\r\nIP blocat\r\nFi\u0219ier identificat ca malware\r\nLogin brute force\r\nRegul\u0103 aplica\u021bie\r\nFirewall\r\n<\/pre>\n<p>Fiecare situa\u021bie necesit\u0103 o verificare diferit\u0103.<\/p>\n<h2>Ce leg\u0103tur\u0103 are Imunify360 cu fi\u0219ierele infectate?<\/h2>\n<p>ModSecurity analizeaz\u0103 \u00een principal request-urile web.<\/p>\n<p>Imunify360 include \u0219i un <strong>malware scanner<\/strong> care poate verifica fi\u0219ierele din conturile de g\u0103zduire.<\/p>\n<p>Astfel, cele dou\u0103 componente ofer\u0103 protec\u021bie \u00een puncte diferite:<\/p>\n<pre>\r\nRequest mali\u021bios\r\n      \u2193\r\nWAF \/ ModSecurity\r\n      \u2193\r\nWebsite\r\n\r\nFi\u0219ier mali\u021bios existent \u00een cont\r\n      \u2193\r\nImunify360 Malware Scanner\r\n<\/pre>\n<p>Un website poate avea ModSecurity activ \u0219i totu\u0219i s\u0103 fie compromis printr-o vulnerabilitate necunoscut\u0103, o parol\u0103 furat\u0103 sau un plugin vulnerabil.<\/p>\n<p>De aceea securitatea trebuie realizat\u0103 pe mai multe niveluri.<\/p>\n<h2>LiteSpeed Cache nu este o func\u021bie de securitate<\/h2>\n<p>LiteSpeed \u0219i LiteSpeed Cache sunt asociate frecvent cu website-urile WordPress, \u00eens\u0103 trebuie f\u0103cut\u0103 o diferen\u021b\u0103 important\u0103.<\/p>\n<p><strong>LiteSpeed Web Server<\/strong> este serverul web care poate procesa inclusiv regulile WAF.<\/p>\n<p><strong>LiteSpeed Cache<\/strong> este o solu\u021bie de cache \u0219i optimizare a performan\u021bei.<\/p>\n<p>LSCache nu \u00eenlocuie\u0219te ModSecurity sau Imunify360.<\/p>\n<p>Rolurile sunt diferite:<\/p>\n<pre>\r\nLiteSpeed Web Server \u2192 server web\r\nLSCache              \u2192 cache \u0219i performan\u021b\u0103\r\nModSecurity \/ WAF    \u2192 filtrare request-uri\r\nImunify360           \u2192 protec\u021bie \u0219i malware\r\nCloudLinux           \u2192 izolare \u0219i resurse\r\n<\/pre>\n<h2>CloudLinux poate provoca eroare 403?<\/h2>\n<p>\u00cen mod obi\u0219nuit, atingerea limitelor CloudLinux nu genereaz\u0103 un 403 ModSecurity.<\/p>\n<p>Limit\u0103rile de CPU, memorie, I\/O sau Entry Processes pot duce mai degrab\u0103 la \u00eencetinirea website-ului, \u00eentreruperi temporare sau alte erori asociate resurselor.<\/p>\n<p>Dac\u0103 prime\u0219ti 403, trebuie verificat\u0103 separat cauza \u0219i nu trebuie presupus automat c\u0103 limita de CPU sau RAM este responsabil\u0103.<\/p>\n<h2>Cum verifici dac\u0103 problema este de la permisiuni?<\/h2>\n<p>O eroare 403 poate ap\u0103rea \u0219i atunci c\u00e2nd permisiunile fi\u0219ierelor sau directoarelor sunt incorecte.<\/p>\n<p>Pentru configura\u021biile obi\u0219nuite cPanel sunt utilizate frecvent:<\/p>\n<pre>\r\nFi\u0219iere   \u2192 0644\r\nDirectoare \u2192 0755\r\n<\/pre>\n<p>Dac\u0103 ai acces SSH, po\u021bi verifica un fi\u0219ier cu:<\/p>\n<pre>ls -l fisier.php<\/pre>\n<p>sau un director cu:<\/p>\n<pre>ls -ld public_html<\/pre>\n<p>Permisiunile trebuie verificate \u00eenainte de a modifica ModSecurity.<\/p>\n<h2>Verific\u0103 \u0219i fi\u0219ierul .htaccess<\/h2>\n<p>Regulile din:<\/p>\n<pre>.htaccess<\/pre>\n<p>pot limita accesul anumitor IP-uri, directoare sau URL-uri.<\/p>\n<p>De exemplu, pot exista reguli precum:<\/p>\n<pre>Require all denied<\/pre>\n<p>sau alte condi\u021bii care genereaz\u0103 un r\u0103spuns 403.<\/p>\n<p>Din acest motiv, atunci c\u00e2nd ModSecurity nu apare \u00een loguri trebuie verificat\u0103 \u0219i configura\u021bia aplica\u021biei.<\/p>\n<h2>Protec\u021bia pe mai multe niveluri \u00een infrastructura NameBox<\/h2>\n<p>Pe infrastructura de g\u0103zduire NameBox sunt utilizate mai multe tehnologii care au roluri complementare.<\/p>\n<table>\n<thead>\n<tr>\n<th>Tehnologie<\/th>\n<th>Rol principal<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>LiteSpeed<\/strong><\/td>\n<td>Server web \u0219i procesarea traficului HTTP\/HTTPS<\/td>\n<\/tr>\n<tr>\n<td><strong>ModSecurity \/ WAF<\/strong><\/td>\n<td>Analizarea \u0219i filtrarea request-urilor web<\/td>\n<\/tr>\n<tr>\n<td><strong>Imunify360<\/strong><\/td>\n<td>WAF, protec\u021bie activ\u0103 \u0219i scanare malware<\/td>\n<\/tr>\n<tr>\n<td><strong>CloudLinux<\/strong><\/td>\n<td>Izolarea conturilor \u0219i controlul resurselor<\/td>\n<\/tr>\n<tr>\n<td><strong>cPanel<\/strong><\/td>\n<td>Administrarea website-urilor \u0219i serviciilor<\/td>\n<\/tr>\n<tr>\n<td><strong>JetBackup \/ Synconix<\/strong><\/td>\n<td>Backup \u0219i restaurarea datelor<\/td>\n<\/tr>\n<tr>\n<td><strong>Arbor Networks<\/strong><\/td>\n<td>Protec\u021bie la nivel de infrastructur\u0103 \u00eempotriva traficului DDoS<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Aceste tehnologii nu se \u00eenlocuiesc \u00eentre ele. Fiecare protejeaz\u0103 o component\u0103 diferit\u0103 a serviciului.<\/p>\n<h2>De ce este important backup-ul dac\u0103 avem Imunify360?<\/h2>\n<p>Nicio solu\u021bie de securitate nu poate garanta blocarea tuturor incidentelor.<\/p>\n<p>Un website poate fi compromis din cauze precum:<\/p>\n<ul>\n<li>plugin vulnerabil;<\/li>\n<li>parol\u0103 compromis\u0103;<\/li>\n<li>cont WordPress compromis;<\/li>\n<li>cod custom vulnerabil;<\/li>\n<li>acces FTP sau SSH compromis;<\/li>\n<li>vulnerabilitate nou\u0103 pentru care nu exist\u0103 \u00eenc\u0103 o regul\u0103.<\/li>\n<\/ul>\n<p>Din acest motiv, backup-ul reprezint\u0103 un nivel separat de protec\u021bie.<\/p>\n<p>Infrastructura NameBox utilizeaz\u0103 solu\u021bii de backup precum <strong>JetBackup \u0219i Synconix<\/strong>, care permit restaurarea datelor atunci c\u00e2nd exist\u0103 un punct de backup disponibil.<\/p>\n<h2>Ce s\u0103 faci dac\u0103 ModSecurity blocheaz\u0103 o opera\u021biune legitim\u0103?<\/h2>\n<p>Dac\u0103 suspectezi un false positive, nu dezactiva permanent protec\u021bia.<\/p>\n<p>Urmeaz\u0103 aceast\u0103 ordine:<\/p>\n<ol>\n<li>noteaz\u0103 URL-ul unde apare eroarea;<\/li>\n<li>noteaz\u0103 ora exact\u0103;<\/li>\n<li>verific\u0103 adresa IP de pe care ai realizat opera\u021biunea;<\/li>\n<li>repet\u0103 opera\u021biunea o singur\u0103 dat\u0103 pentru a reproduce problema;<\/li>\n<li>verific\u0103 dac\u0103 eroarea este 403;<\/li>\n<li>transmite informa\u021biile echipei tehnice;<\/li>\n<li>administratorul verific\u0103 evenimentul \u0219i Rule ID-ul;<\/li>\n<li>dac\u0103 este false positive, se analizeaz\u0103 o excep\u021bie specific\u0103.<\/li>\n<\/ol>\n<p>Este preferabil\u0103 eliminarea unei singure reguli pentru situa\u021bia justificat\u0103 sau configurarea unei excep\u021bii precise dec\u00e2t dezactivarea \u00eentregului WAF.<\/p>\n<h2>Ce s\u0103 NU faci c\u00e2nd apare un 403?<\/h2>\n<p>Nu recomand\u0103m s\u0103:<\/p>\n<ul>\n<li>dezactivezi permanent ModSecurity;<\/li>\n<li>setezi permisiuni 777;<\/li>\n<li>\u0219tergi reguli .htaccess f\u0103r\u0103 s\u0103 \u0219tii ce fac;<\/li>\n<li>dezactivezi Imunify360;<\/li>\n<li>adaugi IP-uri \u00een whitelist f\u0103r\u0103 s\u0103 verifici motivul bloc\u0103rii;<\/li>\n<li>dezactivezi toate pluginurile de securitate f\u0103r\u0103 diagnostic;<\/li>\n<li>modifici simultan mai multe sisteme de protec\u021bie.<\/li>\n<\/ul>\n<p>Dac\u0103 modifici cinci componente simultan \u0219i problema dispare, nu vei mai \u0219ti care dintre acestea era cauza.<\/p>\n<h2>ModSecurity protejeaz\u0103 \u0219i WordPress?<\/h2>\n<p>Da. ModSecurity func\u021bioneaz\u0103 la nivelul serverului web \u0219i poate analiza request-urile \u00eenainte ca acestea s\u0103 ajung\u0103 la WordPress.<\/p>\n<p>Prin urmare, protec\u021bia nu depinde de instalarea unui plugin WordPress.<\/p>\n<p>Acest lucru este util deoarece un request mali\u021bios poate fi blocat \u00eenainte ca WordPress sau pluginul vulnerabil s\u0103 \u00eel proceseze.<\/p>\n<p>Totu\u0219i, ModSecurity nu \u00eenlocuie\u0219te actualizarea platformei.<\/p>\n<p>WordPress, pluginurile \u0219i temele trebuie men\u021binute actualizate.<\/p>\n<h2>ModSecurity protejeaz\u0103 \u0219i magazinele online?<\/h2>\n<p>Da. Request-urile c\u0103tre WooCommerce, PrestaShop sau alte platforme sunt analizate \u00een acela\u0219i mod.<\/p>\n<p>\u00cen cazul magazinelor online exist\u0103 \u00eens\u0103 multe opera\u021biuni dinamice:<\/p>\n<ul>\n<li>checkout;<\/li>\n<li>pl\u0103\u021bi;<\/li>\n<li>API-uri;<\/li>\n<li>importuri;<\/li>\n<li>webhook-uri;<\/li>\n<li>administrarea produselor;<\/li>\n<li>filtre complexe.<\/li>\n<\/ul>\n<p>Acest lucru \u00eenseamn\u0103 c\u0103 este cu at\u00e2t mai important s\u0103 nu dezactivezi arbitrar regulile WAF.<\/p>\n<p>Dac\u0103 apare un false positive, trebuie identificat\u0103 exact cererea \u0219i regula care o blocheaz\u0103.<\/p>\n<h2>ModSecurity este doar o component\u0103 a securit\u0103\u021bii<\/h2>\n<p>Un website sigur nu se bazeaz\u0103 pe o singur\u0103 tehnologie.<\/p>\n<p>Protec\u021bia corect\u0103 presupune mai multe niveluri:<\/p>\n<pre>\r\nHTTPS\r\n   \u2193\r\nLiteSpeed\r\n   \u2193\r\nWAF \/ ModSecurity\r\n   \u2193\r\nImunify360\r\n   \u2193\r\nAplica\u021bie actualizat\u0103\r\n   \u2193\r\nParole sigure + 2FA\r\n   \u2193\r\nCloudLinux\r\n   \u2193\r\nBackup\r\n<\/pre>\n<p>Dac\u0103 unul dintre aceste niveluri nu este configurat corespunz\u0103tor, celelalte pot reduce riscul, dar nu \u00eel pot elimina complet.<\/p>\n<h2>ModSecurity trebuie men\u021binut activ<\/h2>\n<p><strong>ModSecurity \u00een cPanel<\/strong> reprezint\u0103 un nivel important de protec\u021bie pentru website-urile g\u0103zduite pe server.<\/p>\n<p>\u00cempreun\u0103 cu LiteSpeed \u0219i regulile de securitate Imunify360, acesta poate analiza request-urile HTTP \u0219i HTTPS \u0219i poate bloca anumite tentative \u00eenainte ca acestea s\u0103 ajung\u0103 la aplica\u021bie.<\/p>\n<p>Uneori poate ap\u0103rea un false positive \u0219i o opera\u021biune legitim\u0103 poate primi eroarea 403. \u00cen aceast\u0103 situa\u021bie, solu\u021bia corect\u0103 nu este dezactivarea permanent\u0103 a ModSecurity, ci identificarea request-ului \u0219i a regulii care a declan\u0219at blocarea.<\/p>\n<p>Pe infrastructura NameBox utiliz\u0103m <strong>cPanel, LiteSpeed, CloudLinux \u0219i Imunify360<\/strong>, al\u0103turi de sisteme de backup \u0219i protec\u021bie la nivelul infrastructurii, astfel \u00eenc\u00e2t securitatea website-urilor s\u0103 fie realizat\u0103 pe mai multe niveluri.<\/p>\n<p>Dac\u0103 un website g\u0103zduit la NameBox prime\u0219te eroarea <strong>403 Forbidden<\/strong> \u00een timpul unei anumite opera\u021biuni, transmite echipei tehnice URL-ul, ora apari\u021biei problemei \u0219i adresa IP de pe care ai realizat accesarea. Aceste informa\u021bii ne ajut\u0103 s\u0103 verific\u0103m logurile \u0219i s\u0103 identific\u0103m dac\u0103 blocarea provine de la ModSecurity sau de la o alt\u0103 component\u0103 de securitate.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>ModSecurity \u00een cPanel reprezint\u0103 unul dintre nivelurile de protec\u021bie utilizate pentru filtrarea cererilor HTTP suspecte \u00eenainte ca acestea s\u0103 ajung\u0103 la aplica\u021bia website-ului. Pe infrastructura NameBox, aceast\u0103 protec\u021bie lucreaz\u0103 \u00eempreun\u0103 cu tehnologii precum LiteSpeed Web Server, Imunify360, CloudLinux \u0219i cPanel pentru a reduce riscul exploat\u0103rii vulnerabilit\u0103\u021bilor \u0219i al accesului neautorizat. \u00cen anumite situa\u021bii, \u00eens\u0103, o &#8230; <a title=\"ModSecurity \u00een cPanel \u0219i eroarea 403\" class=\"read-more\" href=\"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/\" aria-label=\"Cite\u0219te mai multe despre ModSecurity \u00een cPanel \u0219i eroarea 403\">Cite\u0219te mai mult<\/a><\/p>\n","protected":false},"author":8,"featured_media":2425,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-2424","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-securitate"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox<\/title>\n<meta name=\"description\" content=\"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/\" \/>\n<meta property=\"og:locale\" content=\"ro_RO\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox\" \/>\n<meta property=\"og:description\" content=\"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/\" \/>\n<meta property=\"og:site_name\" content=\"NAMEBOX\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/nameboxro\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-21T06:02:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-22T05:35:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1479\" \/>\n\t<meta property=\"og:image:height\" content=\"592\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Pop George\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@nameboxro\" \/>\n<meta name=\"twitter:site\" content=\"@nameboxro\" \/>\n<meta name=\"twitter:label1\" content=\"Scris de\" \/>\n\t<meta name=\"twitter:data1\" content=\"Pop George\" \/>\n\t<meta name=\"twitter:label2\" content=\"Timp estimat pentru citire\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/\"},\"author\":{\"name\":\"Pop George\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#\\\/schema\\\/person\\\/16c3a696f4e4ad7793ae5cb71b24e13d\"},\"headline\":\"ModSecurity \u00een cPanel \u0219i eroarea 403\",\"datePublished\":\"2026-09-21T06:02:19+00:00\",\"dateModified\":\"2026-09-22T05:35:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/\"},\"wordCount\":2700,\"publisher\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/modsecurity.jpg\",\"articleSection\":[\"Securitate\"],\"inLanguage\":\"ro-RO\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/\",\"url\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/\",\"name\":\"ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/modsecurity.jpg\",\"datePublished\":\"2026-09-21T06:02:19+00:00\",\"dateModified\":\"2026-09-22T05:35:57+00:00\",\"description\":\"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#breadcrumb\"},\"inLanguage\":\"ro-RO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/modsecurity.jpg\",\"contentUrl\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/modsecurity.jpg\",\"width\":1479,\"height\":592,\"caption\":\"text alternativ\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/eroare-403-modsecurity\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ModSecurity \u00een cPanel \u0219i eroarea 403\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/\",\"name\":\"NAMEBOX.RO\",\"description\":\"Ghidul tau complet pentru gazduirea site-urilor web si solutiile de securitate cibernetice\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ro-RO\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#organization\",\"name\":\"NAMEBOX SRL\",\"url\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/04\\\/namebox-logo-square.jpg\",\"contentUrl\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/04\\\/namebox-logo-square.jpg\",\"width\":696,\"height\":696,\"caption\":\"NAMEBOX SRL\"},\"image\":{\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/nameboxro\",\"https:\\\/\\\/x.com\\\/nameboxro\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.namebox.ro\\\/blog\\\/#\\\/schema\\\/person\\\/16c3a696f4e4ad7793ae5cb71b24e13d\",\"name\":\"Pop George\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g\",\"caption\":\"Pop George\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox","description":"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.","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:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/","og_locale":"ro_RO","og_type":"article","og_title":"ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox","og_description":"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.","og_url":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/","og_site_name":"NAMEBOX","article_publisher":"https:\/\/www.facebook.com\/nameboxro","article_published_time":"2026-09-21T06:02:19+00:00","article_modified_time":"2026-09-22T05:35:57+00:00","og_image":[{"width":1479,"height":592,"url":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg","type":"image\/jpeg"}],"author":"Pop George","twitter_card":"summary_large_image","twitter_creator":"@nameboxro","twitter_site":"@nameboxro","twitter_misc":{"Scris de":"Pop George","Timp estimat pentru citire":"14 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#article","isPartOf":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/"},"author":{"name":"Pop George","@id":"https:\/\/www.namebox.ro\/blog\/#\/schema\/person\/16c3a696f4e4ad7793ae5cb71b24e13d"},"headline":"ModSecurity \u00een cPanel \u0219i eroarea 403","datePublished":"2026-09-21T06:02:19+00:00","dateModified":"2026-09-22T05:35:57+00:00","mainEntityOfPage":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/"},"wordCount":2700,"publisher":{"@id":"https:\/\/www.namebox.ro\/blog\/#organization"},"image":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#primaryimage"},"thumbnailUrl":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg","articleSection":["Securitate"],"inLanguage":"ro-RO"},{"@type":"WebPage","@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/","url":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/","name":"ModSecurity cPanel: Cum func\u021bioneaz\u0103 \u0219i eroarea 403 | NameBox","isPartOf":{"@id":"https:\/\/www.namebox.ro\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#primaryimage"},"image":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#primaryimage"},"thumbnailUrl":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg","datePublished":"2026-09-21T06:02:19+00:00","dateModified":"2026-09-22T05:35:57+00:00","description":"Afl\u0103 ce este ModSecurity \u00een cPanel, cum func\u021bioneaz\u0103 \u00eempreun\u0103 cu LiteSpeed \u0219i Imunify360 \u0219i de ce unele cereri pot genera eroarea 403.","breadcrumb":{"@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#breadcrumb"},"inLanguage":"ro-RO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/"]}]},{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#primaryimage","url":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg","contentUrl":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2026\/09\/modsecurity.jpg","width":1479,"height":592,"caption":"text alternativ"},{"@type":"BreadcrumbList","@id":"https:\/\/www.namebox.ro\/blog\/eroare-403-modsecurity\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.namebox.ro\/blog\/"},{"@type":"ListItem","position":2,"name":"ModSecurity \u00een cPanel \u0219i eroarea 403"}]},{"@type":"WebSite","@id":"https:\/\/www.namebox.ro\/blog\/#website","url":"https:\/\/www.namebox.ro\/blog\/","name":"NAMEBOX.RO","description":"Ghidul tau complet pentru gazduirea site-urilor web si solutiile de securitate cibernetice","publisher":{"@id":"https:\/\/www.namebox.ro\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.namebox.ro\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ro-RO"},{"@type":"Organization","@id":"https:\/\/www.namebox.ro\/blog\/#organization","name":"NAMEBOX SRL","url":"https:\/\/www.namebox.ro\/blog\/","logo":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/www.namebox.ro\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2023\/04\/namebox-logo-square.jpg","contentUrl":"https:\/\/www.namebox.ro\/blog\/wp-content\/uploads\/2023\/04\/namebox-logo-square.jpg","width":696,"height":696,"caption":"NAMEBOX SRL"},"image":{"@id":"https:\/\/www.namebox.ro\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/nameboxro","https:\/\/x.com\/nameboxro"]},{"@type":"Person","@id":"https:\/\/www.namebox.ro\/blog\/#\/schema\/person\/16c3a696f4e4ad7793ae5cb71b24e13d","name":"Pop George","image":{"@type":"ImageObject","inLanguage":"ro-RO","@id":"https:\/\/secure.gravatar.com\/avatar\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/76911c48cdc44783217d3056a6793dc997179cd7ba76d07382f69207bbf8efac?s=96&d=mm&r=g","caption":"Pop George"}}]}},"_links":{"self":[{"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/posts\/2424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/comments?post=2424"}],"version-history":[{"count":3,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/posts\/2424\/revisions"}],"predecessor-version":[{"id":2429,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/posts\/2424\/revisions\/2429"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/media\/2425"}],"wp:attachment":[{"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/media?parent=2424"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/categories?post=2424"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.namebox.ro\/blog\/wp-json\/wp\/v2\/tags?post=2424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}