{"id":2296,"date":"2026-01-16T15:29:55","date_gmt":"2026-01-16T15:29:55","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2296"},"modified":"2026-01-16T15:38:38","modified_gmt":"2026-01-16T15:38:38","slug":"eroarea-err_ssl_version_or_cipher_mismatch-ce-inseamna-si-cum-se-rezolva","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/eroarea-err_ssl_version_or_cipher_mismatch-ce-inseamna-si-cum-se-rezolva\/","title":{"rendered":"Eroarea ERR_SSL_VERSION_OR_CIPHER_MISMATCH: ce \u00eenseamn\u0103 \u0219i cum se rezolv\u0103"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">ERR_SSL_VERSION_OR_CIPHER_MISMATCH \u00eenseamn\u0103 c\u0103 browserul \u0219i serverul nu au putut conveni asupra unei versiuni TLS compatibile \u0219i a unei suite de cifrare \u00een timpul str\u00e2ngerii de m\u00e2n\u0103 SSL\/TLS (handshake), astfel c\u0103 browserul refuz\u0103 s\u0103 stabileasc\u0103 o conexiune HTTPS. \u00cen termeni practici, fie dispozitivul t\u0103u este prea vechi pentru set\u0103rile TLS ale site-ului, fie configura\u021bia TLS a site-ului este defect\u0103 sau prea strict\u0103. \u00cen experien\u021ba noastr\u0103 rul\u00e2nd stive de g\u0103zduire \u00een produc\u021bie, aceast\u0103 eroare este una dintre cele mai rapid de diagnosticat atunci c\u00e2nd urmezi o list\u0103 de verificare strict\u0103 \u00een loc s\u0103 \u0219tergi cache-uri la \u00eent\u00e2mplare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest ghid \u00ee\u021bi arat\u0103 un flux de lucru pas cu pas pentru a confirma unde se afl\u0103 problema (dispozitiv vizitator vs configura\u021bie server), cum s\u0103 o reproduci cu instrumente de linie de comand\u0103 \u0219i cum s\u0103 o repari pe set\u0103rile comune de g\u0103zduire (Nginx, Apache \u0219i proxy-uri inverse). Include, de asemenea, c\u00e2teva capcane opera\u021bionale pe care le vedem \u00een timpul migr\u0103rilor, re\u00eennoirilor AutoSSL \u0219i \u00eent\u0103ririi securit\u0103\u021bii.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce \u00eenseamn\u0103 de fapt aceast\u0103 eroare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2nd deschizi https:\/\/domeniultau.com, browserul t\u0103u ini\u021biaz\u0103 un handshake TLS. Browserul trimite un ClientHello care listeaz\u0103 versiunile de protocol suportate (de exemplu TLS 1.2, TLS 1.3) \u0219i o list\u0103 de suite de cifrare pe care este dispus s\u0103 le foloseasc\u0103. Serverul alege o versiune de protocol \u0219i o suit\u0103 de cifrare din acea list\u0103 \u0219i r\u0103spunde cu un ServerHello, apoi lan\u021bul de certificate, apoi detaliile schimbului de chei.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ERR_SSL_VERSION_OR_CIPHER_MISMATCH apare atunci c\u00e2nd acea negociere e\u0219ueaz\u0103 pentru c\u0103 nu exist\u0103 suprapunere. Cele mai comune motive sunt:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Serverul permite doar protocoale vechi (TLS 1.0 sau TLS 1.1) pe care browserele moderne refuz\u0103 s\u0103 le foloseasc\u0103.<\/li>\n\n\n\n<li>Serverul permite doar protocoale \u0219i cifruri moderne, dar un client vechi (OS vechi, dispozitiv \u00eencorporat, runtime Java vechi) nu le poate vorbi.<\/li>\n\n\n\n<li>Lista de cifruri a serverului este configurat\u0103 gre\u0219it \u0219i ajunge s\u0103 nu permit\u0103 niciun cifru utilizabil pentru tipul de cheie ales (RSA vs ECDSA) sau build-ul OpenSSL.<\/li>\n\n\n\n<li>Un proxy invers sau un load balancer termin\u0103 TLS cu o politic\u0103 diferit\u0103 dec\u00e2t se a\u0219teapt\u0103 backend-ul.<\/li>\n\n\n\n<li>Un middlebox (VPN, inspec\u021bie SSL antivirus, proxy corporativ) interfereaz\u0103 \u0219i stric\u0103 handshake-ul.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Distinc\u021bie important\u0103: aceast\u0103 eroare nu este aceea\u0219i cu o problem\u0103 de \u00eencredere a certificatului, cum ar fi un certificat expirat. Po\u021bi avea un certificat perfect valid \u0219i totu\u0219i s\u0103 vezi ERR_SSL_VERSION_OR_CIPHER_MISMATCH dac\u0103 politica TLS a serverului este incompatibil\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Mai \u00eent\u00e2i, afl\u0103 cine este defect<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a atinge configura\u021bia serverului, confirm\u0103 dac\u0103 problema este specific\u0103 unui dispozitiv sau se \u00eent\u00e2mpl\u0103 global. Acest lucru conteaz\u0103 deoarece repara\u021bia difer\u0103 complet.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Testeaz\u0103 de pe alt dispozitiv \u0219i re\u021bea:<\/strong> Deschide acela\u0219i URL de pe telefon folosind date mobile. Apoi \u00eencearc\u0103 dintr-un al doilea browser pe laptop. Dac\u0103 site-ul func\u021bioneaz\u0103 altundeva, serverul t\u0103u este probabil \u00een regul\u0103 \u0219i dispozitivul sau re\u021beaua ta este problema.<\/li>\n\n\n\n<li><strong>\u00centreab\u0103 un resolver neutru:<\/strong> Dac\u0103 eroarea a \u00eenceput imediat dup\u0103 o schimbare DNS sau migrare, verific\u0103 mai \u00eent\u00e2i <a href=\"https:\/\/www.serverspan.ro\/blog\/propagarea-dns-demistificata-cum-sa-verifici-ce-vede-lumea-pas-cu-pas\/\">propagarea DNS<\/a>. Un IP gre\u0219it poate trimite vizitatorii c\u0103tre un server vechi cu TLS \u00eenvechit.<\/li>\n\n\n\n<li><strong>Verific\u0103 dac\u0103 doar un subdomeniu e\u0219ueaz\u0103:<\/strong> exemplu.com func\u021bioneaz\u0103, dar www.exemplu.com e\u0219ueaz\u0103. Asta indic\u0103 adesea o nepotrivire SNI sau vhost.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen coada noastr\u0103 de suport, cel mai rapid indiciu este recunoa\u0219terea tiparelor. Dac\u0103 doar un utilizator raporteaz\u0103 eroarea, este de obicei o problem\u0103 local\u0103 de stiv\u0103 TLS. Dac\u0103 mai mul\u021bi utilizatori o raporteaz\u0103 de pe diferi\u021bi ISP, este de obicei configura\u021bia TLS server-side sau o problem\u0103 de terminare proxy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Repara\u021bii pentru vizitatori (client-side)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu controlezi website-ul (sau suspectezi c\u0103 propriul t\u0103u dispozitiv este excep\u021bia), acestea sunt repara\u021biile care rezolv\u0103 majoritatea cazurilor client-side.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1) Actualizeaz\u0103 browserul \u0219i sistemul de operare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Site-urile moderne necesit\u0103 de obicei TLS 1.2 sau TLS 1.3. Sistemele de operare vechi livreaz\u0103 biblioteci TLS \u0219i magazine r\u0103d\u0103cin\u0103 \u00eenvechite. Actualizarea Chrome sau Firefox ajut\u0103, dar stiva cripto a OS-ului conteaz\u0103 \u00eenc\u0103 pe multe platforme. Dac\u0103 OS-ul t\u0103u este end-of-life, a\u0219teapt\u0103-te la e\u0219ecuri de negociere TLS pe tot mai multe website-uri \u00een timp.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2) Gole\u0219te starea SSL (Windows) \u0219i reporne\u0219te browserul<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Windows memoreaz\u0103 starea SSL \u0219i certificatele. Dac\u0103 configura\u021bia TLS a site-ului s-a schimbat recent, starea memorat\u0103 \u00eenvechit\u0103 poate declan\u0219a e\u0219ecuri ciudate de handshake. Gole\u0219te starea SSL, apoi re\u00eencearc\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Windows: Control Panel -&gt; Internet Options -&gt; Tab-ul Content -&gt; Clear SSL state. Apoi \u00eenchide complet browserul \u0219i redeschide-l.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3) Dezactiveaz\u0103 VPN, proxy \u0219i scanarea HTTPS antivirus (temporar)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Unii clien\u021bi VPN \u0219i suite antivirus efectueaz\u0103 inspec\u021bie HTTPS. Ele intercepteaz\u0103 TLS, emit un certificat local, apoi re-cripteaz\u0103 traficul c\u0103tre destina\u021bie. Dac\u0103 politica lor cripto este \u00eenvechit\u0103 sau are bug-uri, ele stric\u0103 negocierea \u0219i vezi ERR_SSL_VERSION_OR_CIPHER_MISMATCH. Dezactiveaz\u0103 aceste instrumente temporar pentru un test curat, apoi reactiveaz\u0103-le \u0219i ajusteaz\u0103 set\u0103rile dac\u0103 confirmi c\u0103 ele au cauzat eroarea.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4) Comut\u0103 pe un resolver DNS curat (test de sanitate)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru nu repar\u0103 direct negocierea TLS, dar ajut\u0103 c\u00e2nd DNS-ul ISP-ului t\u0103u te trimite c\u0103tre serverul gre\u0219it \u00een timpul unei migr\u0103ri. Ca un test rapid, seteaz\u0103 DNS pe un resolver public, gole\u0219te cache-ul DNS, apoi re\u00eencearc\u0103. Dac\u0103 eroarea dispare, probabil ai ajuns la un endpoint diferit cu o politic\u0103 TLS diferit\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Repara\u021bii pentru proprietarii de site-uri (server-side)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 de\u021bii site-ul \u0219i mai mul\u021bi vizitatori raporteaz\u0103 problema, trateaz-o ca un incident de produc\u021bie. O nepotrivire TLS blocheaz\u0103 toate conversiile, autentific\u0103rile, finaliz\u0103rile de comenzi \u0219i apelurile API prin HTTPS. Scopul este s\u0103 identifici care endpoint termin\u0103 TLS, apoi s\u0103 validezi versiunile de protocol \u0219i suitele de cifrare suportate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 1: Identific\u0103 endpoint-ul TLS real<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Multe configura\u021bii nu termin\u0103 TLS pe aceea\u0219i ma\u0219in\u0103 care ruleaz\u0103 aplica\u021bia web. Configura\u021biile comune includ un proxy invers \u00een fa\u021ba Apache, un load balancer \u00een fa\u021ba mai multor servere web, sau un panou de control de g\u0103zduire care gestioneaz\u0103 \u0219abloanele vhost. Trebuie s\u0103 confirmi unde se \u00eent\u00e2mpl\u0103 handshake-ul TLS \u00eenainte de a schimba configura\u021biile.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dac\u0103 folose\u0219ti un proxy invers, verific\u0103 configura\u021bia sa mai \u00eent\u00e2i. Proxy-ul de\u021bine de obicei portul 443.<\/li>\n\n\n\n<li>Dac\u0103 folose\u0219ti <a href=\"https:\/\/www.serverspan.ro\/blog\/de-ce-latimea-de-banda-nelimitata-este-o-minciuna-intelegerea-inodes-a-limitelor-i-o-si-de-ce-site-urile-cu-trafic-mare-mor-pe-hostingul-partajat\/\">g\u0103zduire partajat\u0103<\/a>, stiva platformei gestioneaz\u0103 TLS (adesea prin AutoSSL). Modific\u0103rile tale trebuie s\u0103 se alinieze cu \u0219abloanele platformei.<\/li>\n\n\n\n<li>Dac\u0103 folose\u0219ti <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-alegi-un-plan-vps-pentru-un-site-web-o-lista-simpla-de-verificare-pentru-dimensionare\/\">un VPS cu propriul<\/a> Nginx sau Apache, de\u021bii \u00eentreaga politic\u0103 TLS.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Insight opera\u021bional: \u00een timpul migr\u0103rilor, echipele testeaz\u0103 adesea serverul backend direct, apoi uit\u0103 c\u0103 traficul de produc\u021bie love\u0219te un endpoint TLS diferit. Proxy-ul ar putea rula \u00eenc\u0103 OpenSSL vechi sau o politic\u0103 de cifrare veche, chiar dac\u0103 backend-ul este modern.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2: Reprodu handshake-ul din linia de comand\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Folose\u0219te OpenSSL pentru a testa exact ce negociaz\u0103 serverul \u0219i ce refuz\u0103. Include \u00eentotdeauna SNI cu -servername, altfel s-ar putea s\u0103 love\u0219ti vhost-ul implicit \u0219i s\u0103 ob\u021bii rezultate \u00een\u0219el\u0103toare.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Test de handshake TLS de baz\u0103 (cu SNI)\nopenssl s_client -connect domeniultau.com:443 -servername domeniultau.com\n\n# For\u021beaz\u0103 TLS 1.2\nopenssl s_client -connect domeniultau.com:443 -servername domeniultau.com -tls1_2\n\n# For\u021beaz\u0103 TLS 1.3\nopenssl s_client -connect domeniultau.com:443 -servername domeniultau.com -tls1_3<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ce s\u0103 cau\u021bi \u00een rezultat:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Protocol<\/strong>: arat\u0103 TLSv1.2 sau TLSv1.3 dac\u0103 negocierea a reu\u0219it.<\/li>\n\n\n\n<li><strong>Cipher<\/strong>: arat\u0103 suita de cifrare negociat\u0103.<\/li>\n\n\n\n<li><strong>Cod de retur verificare<\/strong>: ar trebui s\u0103 fie 0 (ok) pentru un lan\u021b de \u00eencredere, dar chiar \u0219i cu un cod diferit de zero handshake-ul se poate completa \u00eenc\u0103. Acest articol se concentreaz\u0103 pe cazurile \u00een care handshake-ul nu se completeaz\u0103.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 TLS 1.2 e\u0219ueaz\u0103 \u0219i TLS 1.3 e\u0219ueaz\u0103, probabil ai un listener TLS defect, c\u0103i gre\u0219ite de certificat\/cheie sau o problem\u0103 de proxy pe portul 443. Dac\u0103 TLS 1.2 func\u021bioneaz\u0103 dar TLS 1.3 e\u0219ueaz\u0103, s-ar putea s\u0103 ai o problem\u0103 de compatibilitate OpenSSL sau o nepotrivire de politic\u0103 TLS 1.3. Dac\u0103 TLS 1.3 func\u021bioneaz\u0103 dar TLS 1.2 e\u0219ueaz\u0103, probabil ai dezactivat TLS 1.2 \u0219i ai stricat clien\u021bii \u0219i integr\u0103rile mai vechi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 3: Confirm\u0103 protocoalele \u0219i cifrurile suportate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Browserele nu \u00ee\u021bi arat\u0103 o list\u0103 ordonat\u0103 cu ce suport\u0103 serverul. Folose\u0219te instrumente server-side sau scanere externe pentru a enumera protocoalele \u0219i cifrurile. Dac\u0103 preferi un instrument local, instaleaz\u0103 testssl.sh pe o ma\u0219in\u0103 Linux \u0219i ruleaz\u0103-l \u00eempotriva domeniului t\u0103u. Dac\u0103 preferi o verificare web rapid\u0103, folose\u0219te un scaner TLS care listeaz\u0103 suportul protocolului \u0219i suitele de cifrare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Insight opera\u021bional: nu copia \u0219iruri de cifruri aleatorii din post\u0103ri de blog vechi. Vedem asta constant. Adminii lipesc o list\u0103 de cifruri pe care build-ul lor OpenSSL nu o suport\u0103, re\u00eencarc\u0103 Nginx \u0219i accidental se las\u0103 cu o list\u0103 goal\u0103 de cifruri pentru TLS 1.2. Serverul porne\u0219te, dar clien\u021bii nu pot negocia.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cele mai comune cauze r\u0103d\u0103cin\u0103 server-side (\u0219i repara\u021bii)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Mai jos sunt cauzele r\u0103d\u0103cin\u0103 pe care le vedem cel mai des \u00een mediile reale de g\u0103zduire, cu repara\u021bii care se aplic\u0103 stivelor tipice de VPS \u0219i g\u0103zduire web.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cauza 1: Serverul suport\u0103 doar TLS vechi (TLS 1.0 sau TLS 1.1)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru se \u00eent\u00e2mpl\u0103 pe servere vechi care nu au primit niciodat\u0103 actualiz\u0103ri de \u00eent\u0103rire TLS, sau pe stive blocate pe pachete OS antice. Browserele moderne refuz\u0103 s\u0103 negocieze cu TLS 1.0 \u0219i TLS 1.1 pe majoritatea configura\u021biilor, deci handshake-ul e\u0219ueaz\u0103 \u0219i prime\u0219ti eroarea de nepotrivire.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Repara\u021bie:<\/strong> Activeaz\u0103 TLS 1.2 \u0219i TLS 1.3, apoi re\u00eencarc\u0103 serverul web. Pe Nginx:<\/p>\n\n\n<pre class=\"wp-block-code\"><code># \u00cen interiorul blocului server relevant sau blocului http\nssl_protocols TLSv1.2 TLSv1.3;<\/code><\/pre>\n<p><!-- \/wp:post-content --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Apoi re\u00eencarc\u0103 Nginx \u00een siguran\u021b\u0103:<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<pre class=\"wp-block-code\"><code>nginx -t &amp;&amp; systemctl reload nginx<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Pe Apache (mod_ssl), configureaz\u0103 SSLProtocol pentru a permite versiuni moderne \u0219i a dezactiva pe cele vechi:<\/p>\n<p><!-- \/wp:code --><\/p>\n<pre class=\"wp-block-code\"><code># Exemplu Apache 2.4\nSSLProtocol all -SSLv3 -TLSv1 -TLSv1.1<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 nu po\u021bi activa TLS modern din cauza constr\u00e2ngerilor OS, trateaz\u0103 acea ma\u0219in\u0103 ca un risc de securitate \u0219i migreaz\u0103. O solu\u021bie temporar\u0103 este s\u0103 plasezi un proxy invers modern \u00een fa\u021b\u0103, s\u0103 termini TLS acolo \u0219i s\u0103 faci proxy c\u0103tre backend printr-o re\u021bea privat\u0103, dar planific\u0103 retragerea stivei vechi.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h3>Cauza 2: Ai dezactivat TLS 1.2 \u0219i ai stricat integr\u0103rile<\/h3>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Echipele \u00eent\u0103resc uneori TLS permi\u021b\u00e2nd doar TLS 1.3. Asta poate fi \u00een regul\u0103 pentru browsere moderne, dar poate strica aplica\u021bii mobile mai vechi, dispozitive \u00eencorporate, clien\u021bi API mai vechi \u0219i unele medii enterprise care \u00eenc\u0103 se bazeaz\u0103 pe TLS 1.2.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p><strong>Repara\u021bie:<\/strong> Activeaz\u0103 at\u00e2t TLS 1.2 c\u00e2t \u0219i TLS 1.3 dac\u0103 nu ai un mediu client foarte controlat:<\/p>\n<p><!-- \/wp:code --><\/p>\n<pre class=\"wp-block-code\"><code>ssl_protocols TLSv1.2 TLSv1.3;<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Insight opera\u021bional: dac\u0103 rulezi un API folosit de ter\u021bi, p\u0103streaz\u0103 TLS 1.2 activat chiar dac\u0103 propriul frontend folose\u0219te TLS 1.3. Reduce overhead-ul de suport \u0219i evit\u0103 \u00eentreruperile silen\u021bioase pentru clien\u021bi.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h3>Cauza 3: Lista suitei de cifrare este goal\u0103 sau incompatibil\u0103<\/h3>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Un \u0219ir de cifruri prea strict sau defect poate elimina toate cifrurile TLS 1.2 utilizabile. Nginx \u0219i Apache pot porni \u00eenc\u0103, dar clien\u021bii nu pot negocia un cifru comun. Acest lucru se \u00eent\u00e2mpl\u0103 adesea dup\u0103 o schimbare de \u00eent\u0103rire gr\u0103bit\u0103 sau un copy-paste dintr-o configura\u021bie care vizeaz\u0103 o versiune OpenSSL diferit\u0103.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p><strong>Repara\u021bie:<\/strong> Folose\u0219te o politic\u0103 de suit\u0103 de cifrare rezonabil\u0103 pentru TLS 1.2 \u0219i permite implicitele TLS 1.3. Pentru Nginx, configureaz\u0103 cifrurile TLS 1.2 \u0219i prefer\u0103 cifrurile serverului:<\/p>\n<p><!-- \/wp:code --><\/p>\n<pre class=\"wp-block-code\"><code>ssl_protocols TLSv1.2 TLSv1.3;\nssl_ciphers HIGH:!aNULL:!MD5;\nssl_prefer_server_ciphers on;<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Apoi valideaz\u0103 \u0219i re\u00eencarc\u0103:<\/p>\n<p><!-- \/wp:code --><\/p>\n<pre class=\"wp-block-code\"><code>nginx -t &amp;&amp; systemctl reload nginx<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Pentru Apache, asigur\u0103-te c\u0103 SSLCipherSuite nu este excesiv de restrictiv\u0103 \u0219i c\u0103 nu ai dezactivat toate cifrurile RSA \u00een timp ce folose\u0219ti un certificat RSA, sau ai dezactivat toate op\u021biunile ECDSA \u00een timp ce folose\u0219ti un certificat doar ECDSA.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h3>Cauza 4: Nepotrivire SNI sau vhost (certificat \u0219i politic\u0103 gre\u0219ite)<\/h3>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Acest lucru apare c\u00e2nd exemplu.com func\u021bioneaz\u0103 dar www.exemplu.com e\u0219ueaz\u0103, sau c\u00e2nd domeniul e\u0219ueaz\u0103 doar pe un IP \u00een spatele unui load balancer. F\u0103r\u0103 o mapare Server Name Indication (SNI) corect\u0103, serverul prezint\u0103 un vhost implicit. Acel vhost implicit poate avea TLS \u00eenvechit, fi\u0219iere de certificat lips\u0103 sau o politic\u0103 de cifrare diferit\u0103.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p><strong>Repara\u021bie:<\/strong> Confirm\u0103 c\u0103 vhost-ul TLS include server_name corect \u0219i c\u0103ile certificatului pentru fiecare hostname pe care \u00eel serve\u0219ti, inclusiv www, api \u0219i orice subdomenii. Apoi testeaz\u0103 cu SNI explicit:<\/p>\n<p><!-- \/wp:code --><\/p>\n<pre class=\"wp-block-code\"><code>openssl s_client -connect domeniultau.com:443 -servername www.domeniultau.com -tls1_2<\/code><\/pre>\n<p><!-- \/wp:code --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Insight opera\u021bional: c\u00e2nd echipele adaug\u0103 rapid un subdomeniu nou, uit\u0103 uneori s\u0103 emit\u0103 sau s\u0103 ata\u0219eze un certificat acelui vhost. Serverul apoi revine la un bloc TLS implicit \u0219i browserul raporteaz\u0103 o nepotrivire sau e\u0219ec de handshake.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h3>Cauza 5: Proxy invers \u0219i backend-ul nu sunt de acord asupra a\u0219tept\u0103rilor TLS<\/h3>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 termini TLS pe un proxy invers (Nginx, HAProxy, sau un edge gestionat) \u0219i trimi\u021bi mai departe c\u0103tre un backend, backend-ul nu mai gestioneaz\u0103 TLS pentru traficul public. Dar echipele \u00eenc\u0103 schimb\u0103 configura\u021biile TLS backend \u0219i se a\u0219teapt\u0103 ca comportamentul public s\u0103 se schimbe. Proxy-ul invers r\u0103m\u00e2ne endpoint-ul TLS real \u0219i p\u0103streaz\u0103 politica veche.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p><strong>Repara\u021bie:<\/strong> Aplic\u0103 schimb\u0103rile de protocol \u0219i cifru TLS pe proxy-ul care ascult\u0103 pe 443. Apoi verific\u0103 cu openssl s_client de pe o ma\u0219in\u0103 extern\u0103. De asemenea asigur\u0103-te c\u0103 proxy-ul se conecteaz\u0103 corect la backend. Dac\u0103 proxy-ul folose\u0219te HTTPS c\u0103tre backend, trebuie s\u0103 aliniezi set\u0103rile TLS la ambele capete.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h3>Cauza 6: Stiva cripto a OS-ului t\u0103u este prea veche pentru configura\u021bia ta<\/h3>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Chiar dac\u0103 configura\u021bia serverului t\u0103u web arat\u0103 corect, implementarea TLS subiacent\u0103 conteaz\u0103. Nginx \u0219i Apache se bazeaz\u0103 pe OpenSSL (sau biblioteca TLS a platformei). Dac\u0103 distro-ul t\u0103u livreaz\u0103 un build OpenSSL vechi, s-ar putea s\u0103 nu prime\u0219ti suport TLS 1.3, cifruri moderne sau curbe moderne.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p><strong>Repara\u021bie:<\/strong> <a href=\"https:\/\/www.serverspan.ro\/blog\/update-vs-upgrade-de-server-care-este-diferenta-si-de-ce-este-importanta\/\">Actualizeaz\u0103 pachetele OS<\/a>, sau migreaz\u0103 sarcina de lucru pe o versiune OS curent\u0103. Dac\u0103 rulezi sarcini critice de afaceri, nu trata actualiz\u0103rile OS ca fiind op\u021bionale. Suportul TLS \u00eenvechit devine o \u00eentrerupere vizibil\u0103 pentru clien\u021bi, nu doar o \u00eengrijorare de securitate.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h2>Checklist rapid pentru un incident de produc\u021bie<\/h2>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 site-ul t\u0103u este picat pentru vizitatori cu ERR_SSL_VERSION_OR_CIPHER_MISMATCH, folose\u0219te acest flux de incident. Este conceput s\u0103 minimizeze ghicitul.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:list {\"ordered\":true} --><\/p>\n<ol>\n<li><strong>Confirm\u0103 aria de acoperire:<\/strong> E\u0219ueaz\u0103 pe multiple dispozitive \u0219i re\u021bele?<\/li>\n<li><strong>Confirm\u0103 c\u0103 DNS indic\u0103 c\u0103tre serverul a\u0219teptat:<\/strong> Indicarea gre\u0219it\u0103 trimite adesea clien\u021bii c\u0103tre o cutie veche cu TLS mo\u0219tenit.<\/li>\n<li><strong>Identific\u0103 endpoint-ul TLS:<\/strong> Server direct, proxy invers, load balancer sau platform\u0103 de g\u0103zduire.<\/li>\n<li><strong>Ruleaz\u0103 teste openssl con\u0219tiente de SNI:<\/strong> tls1_2 \u0219i tls1_3, \u00eenregistreaz\u0103 Protocol \u0219i Cipher.<\/li>\n<li><strong>Verific\u0103 jurnalele de eroare ale serverului web:<\/strong> Caut\u0103 e\u0219ecuri de handshake \u0219i erori de \u00eenc\u0103rcare certificat.<\/li>\n<li><strong>Valideaz\u0103 sintaxa configura\u021biei:<\/strong> nginx -t sau apachectl configtest \u00eenainte de re\u00eenc\u0103rcare.<\/li>\n<li><strong>Revino dac\u0103 este necesar:<\/strong> Dac\u0103 o schimbare de \u00eent\u0103rire a cauzat \u00eentreruperea, revino la ultima politic\u0103 TLS bun\u0103 cunoscut\u0103, apoi \u00eent\u0103re\u0219te din nou mai atent.<\/li>\n<\/ol>\n<p><!-- \/wp:list --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Insight opera\u021bional: p\u0103streaz\u0103 un fragment TLS &#8220;ultim bun cunoscut&#8221; \u00een controlul versiunii. C\u00e2nd cineva face o schimbare agresiv\u0103 de cifru la 2 AM, vrei o cale de revenire curat\u0103.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h2>Cum previne ServerSpan de obicei acest lucru<\/h2>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Pe platformele de g\u0103zduire gestionat\u0103, aceast\u0103 clas\u0103 de \u00eentrerupere TLS vine de obicei din edit\u0103ri manuale ad-hoc \u0219i \u0219abloane inconsistente. Pe g\u0103zduirea web ServerSpan, platforma include Auto-SSL \u0219i o stiv\u0103 standardizat\u0103 astfel \u00eenc\u00e2t nu ajungi cu un vhost pe TLS modern \u0219i altul blocat pe set\u0103ri mo\u0219tenite. Acea consisten\u021b\u0103 este ceea ce previne situa\u021biile &#8220;func\u021bioneaz\u0103 pe un subdomeniu dar nu pe cel\u0103lalt&#8221; c\u00e2nd g\u0103zduie\u0219ti site-uri multiple.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 rulezi propriul VPS \u0219i vrei aceea\u0219i consisten\u021b\u0103, trateaz\u0103 TLS ca parte a \u00eent\u0103ririi tale de baz\u0103. Folose\u0219te o politic\u0103 Nginx sau Apache predictibil\u0103, testeaz\u0103 dup\u0103 fiecare schimbare \u0219i p\u0103streaz\u0103 configura\u021biile sub controlul versiunii. Dac\u0103 vrei o echip\u0103 practic\u0103 s\u0103 auditeze \u0219i s\u0103 repare \u00eentregul lan\u021b (politic\u0103 TLS, implementare certificat, terminare proxy \u0219i re\u00eennoiri), exploreaz\u0103 <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">serviciile de administrare Linux<\/a> sau mut\u0103 site-urile de produc\u021bie pe <a href=\"https:\/\/www.serverspan.ro\/webhosting\">g\u0103zduire web gestionat\u0103<\/a> unde platforma se ocup\u0103 de p\u0103r\u021bile repetitive \u0219i tu te concentrezi pe afacerea ta.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 planifici momentan o migrare, revizuie\u0219te de asemenea <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">serverele virtuale<\/a> pentru sarcini de lucru care necesit\u0103 control root complet dar beneficiaz\u0103 totu\u0219i de infrastructur\u0103 stabil\u0103 \u0219i re\u021belistic\u0103 predictibil\u0103.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:heading --><\/p>\n<h2>Punct de decizie: p\u0103strezi compatibilitatea sau mergi pe strict<\/h2>\n<p><!-- \/wp:heading --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dup\u0103 ce repari \u00eentreruperea, decide c\u00e2t de strict vrei s\u0103 fii. Politicile TLS stricte reduc suprafa\u021ba de atac, dar renun\u021b\u0103 \u0219i la suportul pentru clien\u021bi mo\u0219teni\u021bi. Pentru website-uri publice, o baz\u0103 practic\u0103 este TLS 1.2 \u0219i TLS 1.3 cu cifruri puternice. Pentru aplica\u021bii enterprise interne, po\u021bi merge mai strict dac\u0103 controlezi clien\u021bii. Pentru API-uri folosite de ter\u021bi, planific\u0103 pentru compatibilitate maxim\u0103 \u00een timp ce r\u0103m\u00e2i sigur.<\/p>\n<p><!-- \/wp:paragraph --><\/p>\n<p><!-- wp:paragraph --><\/p>\n<p>Dac\u0103 nu e\u0219ti sigur ce clien\u021bi depind \u00eenc\u0103 de TLS mai vechi, colecteaz\u0103 dovezi \u00eenainte de a-i t\u0103ia. Revizuie\u0219te jurnalele de acces, distribu\u021bia user-agent \u0219i versiunile client API. Apoi ajusteaz\u0103 politica TLS inten\u021bionat \u00een loc s\u0103 descoperi cerin\u021bele de compatibilitate prin \u00eentreruperi.<\/p>\n<p><!-- \/wp:paragraph --><\/p>","protected":false},"excerpt":{"rendered":"<p>ERR_SSL_VERSION_OR_CIPHER_MISMATCH \u00eenseamn\u0103 c\u0103 browserul \u0219i serverul nu au putut conveni asupra unei versiuni TLS compatibile \u0219i a unei suite de cifrare \u00een timpul str\u00e2ngerii de m\u00e2n\u0103 SSL\/TLS (handshake), astfel c\u0103 browserul refuz\u0103 s\u0103 stabileasc\u0103 o conexiune HTTPS. \u00cen termeni practici, fie dispozitivul t\u0103u este prea vechi pentru set\u0103rile TLS ale site-ului, fie configura\u021bia TLS a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2293,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[13584,13610,13550,13573,13586,13579,13606,13585,13599,13600,13588,13604,13603,13582,13581,13589,13592,13601,13602,13609,13596,13551,13558,13593,13594,13590,13611,13591,13597,13580,13583,13595,13605,13608,13598,13607,13587],"class_list":["post-2296","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-activare-tls-1-2-si-tls-1-3","tag-ajutor-configuratie-ssl-vps","tag-apache-sslprotocol-tls1-2","tag-apachectl-configtest-ssl","tag-bune-practici-nginx-ssl_ciphers","tag-ce-este-err_ssl_version_or_cipher_mismatch","tag-compatibilitate-tls-pentru-clienti-api","tag-configuratie-apache-sslciphersuite","tag-configuratie-ssl-vhost-gresita","tag-configuratie-suite-cifrare-moderne","tag-depanare-handshake-ssl","tag-depanare-reinnoire-autossl","tag-depanare-ssl-directadmin","tag-eroare-nepotrivire-cifru","tag-eroare-nepotrivire-versiune-ssl","tag-eroare-website-nu-incarca-https","tag-golire-stare-ssl-windows","tag-lista-verificare-incident-tls-productie","tag-lista-verificare-intarire-tls","tag-monitorizare-ssl-pentru-website-uri","tag-nepotrivire-tls-load-balancer","tag-nginx-ssl_protocols-tlsv1-2-tlsv1-3","tag-openssl-s_client-servername-sni","tag-problema-handshake-ssl-vpn","tag-problema-scanare-https-antivirus","tag-problema-tls-browser-mostenit","tag-repara-configuratie-ssl-pe-server","tag-repara-eroare-conexiune-https","tag-reparatie-configurare-gresita-sni","tag-reparatie-err_ssl_version_or_cipher_mismatch","tag-reparatie-esec-handshake-tls","tag-reparatie-server-tls-invechit","tag-ssl-gazduire-web-sigura","tag-suport-ssl-linux-gestionat","tag-terminare-tls-proxy-invers","tag-test-config-reincarcare-nginx","tag-test-tls-openssl-s_client"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2296","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=2296"}],"version-history":[{"count":2,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2296\/revisions"}],"predecessor-version":[{"id":2298,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2296\/revisions\/2298"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2293"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}