{"id":2321,"date":"2026-01-21T20:45:12","date_gmt":"2026-01-21T20:45:12","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2321"},"modified":"2026-01-21T20:45:12","modified_gmt":"2026-01-21T20:45:12","slug":"continut-mixt-dupa-activarea-ssl-gasirea-si-remedierea-elementelor-nesecurizate","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/continut-mixt-dupa-activarea-ssl-gasirea-si-remedierea-elementelor-nesecurizate\/","title":{"rendered":"Con\u021binut mixt dup\u0103 activarea SSL: G\u0103sirea \u0219i remedierea elementelor nesecurizate"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Ai f\u0103cut munca grea. Ai achizi\u021bionat un certificat SSL (sau ai generat unul gratuit prin Let&#8217;s Encrypt din panoul t\u0103u de control ServerSpan), l-ai instalat pe server \u0219i ai actualizat set\u0103rile URL-ului WordPress pentru a \u00eencepe cu <code>https:\/\/<\/code>. Navighezi pe pagina principal\u0103, a\u0219tept\u00e2ndu-te s\u0103 vezi acel lac\u0103t verde lini\u0219titor l\u00e2ng\u0103 URL. \u00cen schimb, e\u0219ti \u00eent\u00e2mpinat de un avertisment strident &#8220;Not Secure&#8221; (Nesecurizat) sau, mai r\u0103u, de un layout stricat, unde stilurile lipsesc \u0219i imaginile refuz\u0103 s\u0103 se \u00eencarce.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este capcana &#8220;Con\u021binutului Mixt&#8221; (Mixed Content) \u0219i este singurul obstacol major pe care webmasterii \u00eel \u00eent\u00e2mpin\u0103 cel mai des imediat dup\u0103 migrarea la HTTPS. Din experien\u021ba noastr\u0103 \u00een gestionarea a mii de <a href=\"https:\/\/www.serverspan.ro\/blog\/de-ce-vps-hosting-nu-inseamna-acelasi-lucru-la-toti-furnizorii\/\">servere virtuale private (VPS)<\/a> \u0219i medii WordPress, estim\u0103m c\u0103 aproape <strong>60% dintre migr\u0103rile manuale SSL rezult\u0103 \u00een avertismente de con\u021binut mixt<\/strong> dac\u0103 baza de date nu este gestionat\u0103 corespunz\u0103tor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru nu \u00eenseamn\u0103 c\u0103 certificatul t\u0103u SSL este stricat. \u00censeamn\u0103 c\u0103 site-ul t\u0103u sufer\u0103 de o criz\u0103 de identitate: \u00een timp ce pagina principal\u0103 este livrat\u0103 securizat prin HTTPS, aceasta \u00eenc\u0103 cere browserului vizitatorului s\u0103 preia resurse nesecurizate (imagini, scripturi, fonturi) prin vechiul protocol HTTP. Browserul, detect\u00e2nd o poten\u021bial\u0103 bre\u0219\u0103 de securitate, blocheaz\u0103 sau semnalizeaz\u0103 aceste resurse.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen acest ghid extins, vom trece dincolo de sfaturile de baz\u0103. Vom oferi un tutorial aprofundat despre diagnosticarea acestor probleme folosind instrumentele pentru dezvoltatori, \u00een\u021belegerea modelului de securitate al browserului \u0219i repararea permanent\u0103 a con\u021binutului mixt direct de la surs\u0103 \u2014 f\u0103r\u0103 a ne baza pe plugin-uri care consum\u0103 resurse \u0219i \u00eencetinesc site-ul.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00cen\u021belegerea modelului de securitate: De ce intr\u0103 browserele \u00een panic\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru a rezolva problema, trebuie mai \u00eent\u00e2i s\u0103 \u00een\u021belegi de ce browserele moderne precum Chrome, Firefox \u0219i Safari reac\u021bioneaz\u0103 at\u00e2t de agresiv la con\u021binutul mixt. Totul se rezum\u0103 la integritatea conexiunii.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd un utilizator se conecteaz\u0103 la site-ul t\u0103u prin HTTPS, conexiunea este criptat\u0103. Acest lucru garanteaz\u0103 trei aspecte:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Autentificarea:<\/strong> Utilizatorul vorbe\u0219te cu serverul real, nu cu un impostor.<\/li>\n\n\n\n<li><strong>Integritatea datelor:<\/strong> Datele nu au fost modificate \u00een tranzit.<\/li>\n\n\n\n<li><strong>Criptarea:<\/strong> Nicio ter\u021b\u0103 parte nu poate citi datele.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Con\u021binutul mixt \u00eencalc\u0103 aceast\u0103 garan\u021bie. Dac\u0103 o pagin\u0103 securizat\u0103 \u00eencarc\u0103 un fi\u0219ier JavaScript prin HTTP nesecurizat, un hacker aflat pe aceea\u0219i re\u021bea Wi-Fi ar putea efectua un atac Man-in-the-Middle (MitM), ar putea modifica acel script \u0219i ar putea fura cookie-urile de sesiune securizate sau datele de autentificare ale utilizatorului. Deoarece un singur activ nesecurizat poate compromite \u00eentreaga pagin\u0103 securizat\u0103, browserele trateaz\u0103 con\u021binutul mixt ca pe o vulnerabilitate sever\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cele dou\u0103 tipuri de con\u021binut mixt<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Browserele disting \u00eentre dou\u0103 tipuri de con\u021binut mixt, gestion\u00e2ndu-le diferit. Cunoa\u0219terea diferen\u021bei te ajut\u0103 s\u0103 prioritizezi remedierile.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1. Con\u021binut mixt pasiv (Display Content)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 categorie include con\u021binut care nu poate interac\u021biona cu restul codului paginii, \u00een principal <strong>imagini, fi\u0219iere video \u0219i audio<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Comportamentul browserului:<\/strong> Majoritatea browserelor permit, de obicei, \u00eenc\u0103rcarea acestui con\u021binut, dar vor penaliza indicatorul de securitate al site-ului. \u00cen Google Chrome, de exemplu, lac\u0103tul dispare sau este \u00eenlocuit cu un avertisment &#8220;Not Secure&#8221;. De\u0219i pagina func\u021bioneaz\u0103, \u00eencrederea utilizatorului este erodat\u0103 instantaneu.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">2. Con\u021binut mixt activ (Scripting Content)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta este categoria periculoas\u0103. Include <strong>scripturi (JavaScript), foi de stil (CSS), iframe-uri \u0219i fonturi (WOFF\/TTF)<\/strong>. Deoarece aceste active pot modifica Document Object Model (DOM) al paginii, ele au acces complet la datele securizate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Comportamentul browserului:<\/strong> Browserele moderne <strong>blocheaz\u0103 implicit con\u021binutul mixt activ<\/strong>. Pur \u0219i simplu refuz\u0103 s\u0103 \u00eencarce fi\u0219ierul. Acesta este motivul pentru care site-ul t\u0103u ar putea ar\u0103ta ca un schelet HTML nestilizat sau de ce meniurile derulante \u0219i formularele de checkout nu mai func\u021bioneaz\u0103 dup\u0103 o migrare SSL. Activele nu lipsesc; browserul protejeaz\u0103 utilizatorul de ele.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 1: Diagnosticarea problemei<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a rula orice remedieri \u00een mas\u0103, trebuie s\u0103 identifici exact ce anume cauzeaz\u0103 problema. De\u0219i exist\u0103 scanere online, acestea omit adesea con\u021binutul dinamic \u00eenc\u0103rcat prin JavaScript. Cel mai fiabil instrument este deja instalat pe computerul t\u0103u: Instrumentele pentru dezvoltatori ale browserului web (DevTools).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Diagnosticare pas cu pas prin Chrome DevTools<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 metod\u0103 dezv\u0103luie exact care fi\u0219iere declan\u0219eaz\u0103 avertismentele.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Deschide Developer Tools:<\/strong> D\u0103 click dreapta oriunde pe site-ul t\u0103u \u0219i selecteaz\u0103 <strong>Inspect<\/strong> (Inspecteaz\u0103), sau apas\u0103 <code>Ctrl+Shift+I<\/code> (Windows) \/ <code>Cmd+Opt+I<\/code> (Mac).<\/li>\n\n\n\n<li><strong>Navigheaz\u0103 la tab-ul Console:<\/strong> Caut\u0103 tab-ul etichetat &#8220;Console&#8221; \u00een partea de sus a panoului.<\/li>\n\n\n\n<li><strong>Identific\u0103 erorile:<\/strong> Erorile de con\u021binut mixt sunt distincte. De obicei, vor fi eviden\u021biate cu ro\u0219u (pentru con\u021binut activ blocat) sau galben (pentru avertismente de con\u021binut pasiv).<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Un mesaj de eroare tipic arat\u0103 astfel:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Mixed Content: The page at 'https:\/\/exemplu.ro\/' was loaded over HTTPS, but requested an insecure image 'http:\/\/exemplu.ro\/wp-content\/uploads\/2024\/01\/hero-bg.jpg'. This content should also be served over HTTPS.<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Analiz\u0103:<\/strong> \u00cen acest exemplu, pagina este securizat\u0103, dar imaginea de fundal este hardcodat\u0103 cu <code>http:\/\/<\/code>. Browserul ar putea s\u0103 o afi\u0219eze, dar va afi\u0219a un avertisment de securitate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Verificarea tab-ului Network pentru cereri &#8220;Blocate&#8221;<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 layout-ul site-ului este stricat, verific\u0103 tab-ul <strong>Network<\/strong> \u00een DevTools.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Click pe tab-ul <strong>Network<\/strong>.<\/li>\n\n\n\n<li>Re\u00eencarc\u0103 pagina (F5 sau Cmd+R).<\/li>\n\n\n\n<li>Uit\u0103-te la coloana &#8220;Status&#8221;. Dac\u0103 vezi statusul <strong>(blocked:mixed-content)<\/strong> cu text ro\u0219u, acel activ a fost \u00eempiedicat complet s\u0103 se \u00eencarce.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru este comun \u00een cazul scripturilor externe (cum ar fi biblioteci jQuery vechi) sau fonturilor \u00eenc\u0103rcate de pe servere ter\u021be care nu folosesc SSL.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 2: Repararea bazei de date (Modul corect)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen 90% dintre cazurile WordPress, con\u021binutul mixt apare deoarece baza de date con\u021bine \u00eenc\u0103 URL-uri absolute care indic\u0103 spre <code>http:\/\/<\/code>. C\u00e2nd \u00eencarci o imagine \u00een WordPress, acesta salveaz\u0103 calea complet\u0103 (de ex., <code>http:\/\/domeniu.ro\/imagine.jpg<\/code>) \u00een tabelul <code>wp_posts<\/code>. Schimbarea URL-ului site-ului din set\u0103ri <strong>nu<\/strong> actualizeaz\u0103 aceste mii de referin\u021be existente.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">De ce NU ar trebui s\u0103 folose\u0219ti un plugin pentru asta<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Mul\u021bi \u00eencep\u0103tori instaleaz\u0103 plugin-uri precum &#8220;Really Simple SSL&#8221; sau &#8220;SSL Insecure Content Fixer&#8221;. De\u0219i aceste plugin-uri func\u021bioneaz\u0103, ele opereaz\u0103 adesea folosind PHP Output Buffering. Ele intercepteaz\u0103 pagina HTML \u00eenainte de a fi trimis\u0103 utilizatorului, o scaneaz\u0103 pentru link-uri <code>http:\/\/<\/code> \u0219i le \u00eenlocuiesc cu <code>https:\/\/<\/code> \u00een timp real.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problema:<\/strong> Acest proces adaug\u0103 timp de procesare la <em>fiecare \u00eenc\u0103rcare a paginii<\/em>. Cre\u0219te timpul p\u00e2n\u0103 la primul octet (TTFB) \u0219i mascheaz\u0103 problema \u00een loc s\u0103 o rezolve. La ServerSpan, sus\u021binem solu\u021bii curate \u0219i performante: repararea datelor permanent.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u00cen\u021belegerea datelor serializate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Avertisment crucial:<\/strong> Ai putea fi tentat s\u0103 rulezi o interogare SQL simpl\u0103 precum <code>UPDATE wp_posts SET post_content = REPLACE(...)<\/code>. <strong>Nu face acest lucru.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress stocheaz\u0103 set\u0103rile temei \u0219i datele widget-urilor \u00een &#8220;matrice serializate&#8221; (serialized arrays). Acesta este un format \u00een care lungimea datelor este stocat\u0103 al\u0103turi de date (de ex., <code>s:4:\"http\"<\/code>). Dac\u0103 schimbi <code>http<\/code> cu <code>https<\/code> (4 caractere \u00een 5 caractere) f\u0103r\u0103 a actualiza num\u0103rul de serializare, datele devin corupte, iar set\u0103rile site-ului t\u0103u vor disp\u0103rea.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Metoda A: Solu\u021bia profesional\u0103 prin WP-CLI (Recomandat)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti g\u0103zduit pe un <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">VPS ServerSpan<\/a>, ai acces root \u0219i po\u021bi folosi <strong>WP-CLI<\/strong> (WordPress Command Line Interface). Acesta este standardul de aur pentru actualizarea URL-urilor deoarece gestioneaz\u0103 automat serializarea \u0219i execut\u0103 comenzile \u00een c\u00e2teva secunde.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Conecteaz\u0103-te la server<\/strong> prin SSH.<\/li>\n\n\n\n<li><strong>Navigheaz\u0103 \u00een directorul r\u0103d\u0103cin\u0103 al site-ului:<\/strong><br><code>cd \/var\/www\/domeniultau.ro\/public_html<\/code><\/li>\n\n\n\n<li><strong>F\u0103 un backup al bazei de date mai \u00eent\u00e2i:<\/strong><br><code>wp db export pre-ssl-fix.sql<\/code><\/li>\n\n\n\n<li><strong>Ruleaz\u0103 o simulare (dry run):<\/strong> Aceasta \u00ee\u021bi arat\u0103 c\u00e2te \u00eenlocuiri <em>ar fi<\/em> f\u0103cute f\u0103r\u0103 a schimba nimic efectiv.<br><code>wp search-replace 'http:\/\/domeniultau.ro' 'https:\/\/domeniultau.ro' --dry-run<\/code><\/li>\n\n\n\n<li><strong>Execut\u0103 \u00eenlocuirea:<\/strong><br><code>wp search-replace 'http:\/\/domeniultau.ro' 'https:\/\/domeniultau.ro'<\/code><\/li>\n\n\n\n<li><strong>Cur\u0103\u021b\u0103 cache-ul:<\/strong><br><code>wp cache flush<\/code><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Baza ta de date este acum actualizat\u0103 permanent. Nu sunt necesare plugin-uri.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Metoda B: Plugin-ul &#8220;Better Search Replace&#8221; (F\u0103r\u0103 cod)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu e\u0219ti confortabil cu linia de comand\u0103, plugin-ul <strong>Better Search Replace<\/strong> este cea mai bun\u0103 alternativ\u0103 cu interfa\u021b\u0103 grafic\u0103. Spre deosebire de plugin-urile de &#8220;reparare \u00een timp real&#8221;, acesta ruleaz\u0103 o singur\u0103 dat\u0103, actualizeaz\u0103 corect baza de date (gestion\u00e2nd serializarea) \u0219i apoi poate fi dezinstalat.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Instaleaz\u0103 \u0219i activeaz\u0103 <strong>Better Search Replace<\/strong>.<\/li>\n\n\n\n<li>Mergi la <strong>Tools (Unelte) > Better Search Replace<\/strong>.<\/li>\n\n\n\n<li>\u00cen c\u00e2mpul &#8220;Search for&#8221; (Caut\u0103), introdu: <code>http:\/\/domeniultau.ro<\/code><\/li>\n\n\n\n<li>\u00cen c\u00e2mpul &#8220;Replace with&#8221; (\u00cenlocuie\u0219te cu), introdu: <code>https:\/\/domeniultau.ro<\/code><\/li>\n\n\n\n<li>Selecteaz\u0103 toate tabelele.<\/li>\n\n\n\n<li>Bifeaz\u0103 mai \u00eent\u00e2i &#8220;Run as dry run&#8221; pentru a verifica.<\/li>\n\n\n\n<li>Debifeaz\u0103 &#8220;dry run&#8221; \u0219i apas\u0103 &#8220;Run Search\/Replace&#8221;.<\/li>\n\n\n\n<li><strong>\u0218terge plugin-ul<\/strong> dup\u0103 ce ai terminat.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 3: Repararea activelor &#8220;\u00eenc\u0103p\u0103\u021b\u00e2nate&#8221; (Teme \u0219i Buildere)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Uneori, repararea bazei de date nu este suficient\u0103. Fi\u0219ierele temei sau constructorii de pagini (page builders) ar putea avea propriul mod de a stoca link-uri.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenariul 1: Foi de stil Elementor<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Elementor salveaz\u0103 fi\u0219iere CSS \u00eentr-un folder specific de upload. Chiar \u0219i dup\u0103 actualizarea bazei de date, Elementor poate servi \u00een continuare vechile fi\u0219iere CSS care con\u021bin link-uri HTTP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mergi \u00een Panoul de Control WordPress.<\/li>\n\n\n\n<li>Navigheaz\u0103 la <strong>Elementor > Tools (Unelte)<\/strong>.<\/li>\n\n\n\n<li>Click pe tab-ul <strong>Regenerate CSS &amp; Data<\/strong>.<\/li>\n\n\n\n<li>Apas\u0103 butonul <strong>Regenerate Files<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru for\u021beaz\u0103 Elementor s\u0103 \u00ee\u0219i reconstruiasc\u0103 foile de stil externe folosind noile URL-uri HTTPS din set\u0103rile bazei de date.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenariul 2: Fi\u0219iere de tem\u0103 hardcodate<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 un dezvoltator a personalizat tema ta, este posibil s\u0103 fi hardcodat un link direct \u00eentr-un fi\u0219ier PHP sau CSS (de ex., <code>background-image: url('http:\/\/...')<\/code> \u00een <code>style.css<\/code>). C\u0103utarea \u00een baza de date nu va g\u0103si aceste link-uri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cum s\u0103 le g\u0103se\u0219ti folosind GREP (Linux):<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Din terminal, ruleaz\u0103 o c\u0103utare recursiv\u0103 \u00een folderul temei tale:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep -r \"http:\/\/\" \/var\/www\/domeniultau.ro\/public_html\/wp-content\/themes\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aceasta va lista fiecare fi\u0219ier care con\u021bine &#8220;http:\/\/&#8221;. Deschide aceste fi\u0219iere \u0219i actualizeaz\u0103 manual link-urile la <code>https:\/\/<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Sfat Pro:<\/strong> \u00cen loc s\u0103 hardcodezi <code>https:\/\/domeniultau.ro\/imagine.png<\/code>, folose\u0219te func\u021bii dinamice WordPress precum <code>get_stylesheet_directory_uri()<\/code> \u00een PHP. Acest lucru asigur\u0103 c\u0103 link-ul se potrive\u0219te \u00eentotdeauna cu protocolul actual al site-ului.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 4: &#8220;Op\u021biunea Nuclear\u0103&#8221; (Content Security Policy)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Exist\u0103 cazuri rare \u00een care nu po\u021bi g\u0103si sursa con\u021binutului nesecurizat. Poate provine dintr-un script publicitar ter\u021b care genereaz\u0103 dinamic frame-uri HTTP, sau este \u00eengropat \u00eentr-un plugin vechi pe care nu \u00eel po\u021bi edita.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen aceste cazuri, po\u021bi utiliza un antet HTTP specific numit <strong>Content Security Policy (CSP)<\/strong> pentru a for\u021ba browserul s\u0103 rezolve problema \u00een locul t\u0103u.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Upgrade-Insecure-Requests<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ad\u0103ug\u00e2nd directiva <code>upgrade-insecure-requests<\/code> la antetul serverului t\u0103u, \u00eei spui browserului: <em>&#8220;Chiar dac\u0103 codul cere HTTP, trateaz\u0103-l automat ca HTTPS.&#8221;<\/em><\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Implementare pe Nginx (Implicit la ServerSpan)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Adaug\u0103 aceast\u0103 linie \u00een blocul de configurare al serverului Nginx:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>add_header Content-Security-Policy \"upgrade-insecure-requests\";<\/code><\/pre>\n\n\n\n<h4 class=\"wp-block-heading\">Implementare pe Apache\/OpenLiteSpeed (.htaccess)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Adaug\u0103 acest cod la \u00eenceputul fi\u0219ierului t\u0103u <code>.htaccess<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;IfModule mod_headers.c&gt;\n    Header always set Content-Security-Policy \"upgrade-insecure-requests\"\n&lt;\/IfModule&gt;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Not\u0103 important\u0103:<\/strong> Aceast\u0103 directiv\u0103 practic &#8220;c\u00e2rpe\u0219te&#8221; problema la nivel de client. Elimin\u0103 eficient avertismentele de con\u021binut mixt, dar presupune c\u0103 resursa <em>este<\/em> de fapt disponibil\u0103 prin HTTPS. Dac\u0103 ai un link c\u0103tre o imagine extern\u0103 de pe un server care nu are certificat SSL, browserul va \u00eencerca s\u0103 o \u00eencarce securizat, va e\u0219ua, iar imaginea nu se va \u00eenc\u0103rca. Totu\u0219i, lac\u0103tul verde va r\u0103m\u00e2ne intact.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Caz special: <a href=\"https:\/\/www.serverspan.ro\/blog\/prabusirea-globala-cloudflare-din-18-noiembrie-2025-de-ce-infrastructura-centralizata-este-un-punct-unic-de-esec-si-ce-face-hosting-ul-vps-corect\/\">Cloudflare \u0219i bucla &#8220;Flexible SSL&#8221;<\/a><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Vedem adesea utilizatori care activeaz\u0103 Cloudflare \u0219i \u00eent\u00e2mpin\u0103 probleme masive de con\u021binut mixt sau erori de tip &#8220;Too Many Redirects&#8221;. Acest lucru se datoreaz\u0103 de obicei set\u0103rii <strong>Flexible SSL<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Scenariul:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Vizitator c\u0103tre Cloudflare:<\/strong> Se conecteaz\u0103 prin HTTPS.<\/li>\n\n\n\n<li><strong>Cloudflare c\u0103tre Serverul t\u0103u de origine:<\/strong> Se conecteaz\u0103 prin HTTP (Modul Flexible).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Deoarece serverul t\u0103u de origine prime\u0219te o cerere pe portul 80 (HTTP), WordPress crede c\u0103 este accesat nesecurizat. \u00ce\u0219i genereaz\u0103 toate link-urile interne (meniuri, imagini, antete) folosind URL-uri <code>http:\/\/<\/code>. Vizitatorul prime\u0219te o pagin\u0103 securizat\u0103 plin\u0103 de link-uri nesecurizate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solu\u021bia:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Instaleaz\u0103 un certificat SSL valid pe VPS-ul t\u0103u de origine (ServerSpan ofer\u0103 AutoSSL\/Let&#8217;s Encrypt gratuit).<\/li>\n\n\n\n<li>Mergi \u00een Panoul Cloudflare > <strong>SSL\/TLS<\/strong>.<\/li>\n\n\n\n<li>Schimb\u0103 modul din <strong>Flexible<\/strong> \u00een <strong>Full (Strict)<\/strong>.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru for\u021beaz\u0103 conexiunea dintre Cloudflare \u0219i serverul t\u0103u s\u0103 fie securizat\u0103, permi\u021b\u00e2nd WordPress s\u0103 detecteze corect protocolul HTTPS \u0219i s\u0103 genereze link-urile corespunz\u0103tor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Concluzie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Erorile de con\u021binut mixt pot fi frustrante, dar sunt o problem\u0103 logic\u0103 ce poate fi rezolvat\u0103. Printr-o diagnosticare metodic\u0103 folosind instrumentele browserului \u0219i aplicarea unor remedieri permanente la nivel de baz\u0103 de date \u0219i cod \u2014 \u00een loc s\u0103 te bazezi pe plugin-uri temporare \u2014 te asiguri c\u0103 site-ul t\u0103u r\u0103m\u00e2ne rapid, profesional \u0219i securizat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Repararea con\u021binutului mixt este un pas critic \u00een administrarea serverului, dar este doar o parte a men\u021binerii unei infrastructuri s\u0103n\u0103toase. Dac\u0103 serializarea manual\u0103 a bazei de date \u0219i configurarea antetelor Nginx sun\u0103 ca distrageri de la activitatea ta principal\u0103, ia \u00een considerare explorarea solu\u021biilor <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">Managed VPS<\/a> de la ServerSpan.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Echipa noastr\u0103 se ocup\u0103 de munca grea legat\u0103 de securizare, implementarea SSL \u0219i optimizarea performan\u021bei, astfel \u00eenc\u00e2t lac\u0103tul verde s\u0103 fie standardul, nu o lupt\u0103.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ai f\u0103cut munca grea. Ai achizi\u021bionat un certificat SSL (sau ai generat unul gratuit prin Let&#8217;s Encrypt din panoul t\u0103u de control ServerSpan), l-ai instalat pe server \u0219i ai actualizat set\u0103rile URL-ului WordPress pentru a \u00eencepe cu https:\/\/. Navighezi pe pagina principal\u0103, a\u0219tept\u00e2ndu-te s\u0103 vezi acel lac\u0103t verde lini\u0219titor l\u00e2ng\u0103 URL. \u00cen schimb, e\u0219ti \u00eent\u00e2mpinat [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2318,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[13699,13700,13689,13698,13691,13690,13697,13685,13693,13687,13706,13694,13702,13701,13695,13696,13686,13692,13705,13704,13680,13703,13664,13684,13688],"class_list":["post-2321","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-antet-content-security-policy","tag-apache-fortare-https","tag-chrome-blocare-continut-mixt","tag-configurare-ssl-nginx","tag-continut-mixt-pasiv-vs-activ","tag-elementor-regenerare-css-https","tag-eliminare-linkuri-http-wordpress","tag-eroare-continut-mixt","tag-eroare-continut-securizat","tag-fixare-continut-mixt-ssl","tag-gazduire-managed-ssl","tag-ghid-migrare-ssl","tag-impact-seo-https","tag-lacat-securizat-lipsa","tag-migrare-baza-de-date-wordpress","tag-plugin-better-search-replace","tag-reparare-avertisment-not-secure","tag-reparare-imagine-nesecurizata-wordpress","tag-reparare-ssl-stricat-wordpress","tag-scaner-continut-mixt","tag-serverspan-vps","tag-tab-securitate-developer-tools","tag-upgrade-insecure-requests-nginx","tag-wordpress-https-continut-mixt","tag-wp-cli-cautare-inlocuire"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2321"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2321\/revisions"}],"predecessor-version":[{"id":2322,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2321\/revisions\/2322"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2318"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}