{"id":2568,"date":"2026-03-02T23:33:07","date_gmt":"2026-03-02T23:33:07","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2568"},"modified":"2026-03-02T23:37:52","modified_gmt":"2026-03-02T23:37:52","slug":"directadmin-1-695-breaking-change-unificarea-private_html-cu-public_html-si-ce-inseamna-asta-pentru-site-urile-tale","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/directadmin-1-695-breaking-change-unificarea-private_html-cu-public_html-si-ce-inseamna-asta-pentru-site-urile-tale\/","title":{"rendered":"DirectAdmin 1.695 Breaking Change: Unificarea private_html cu public_html \u0219i ce \u00eenseamn\u0103 asta pentru site-urile tale"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">DirectAdmin 1.695, lansat pe 18 februarie 2026, modific\u0103 toate \u0219abloanele de configurare ale serverului web pentru a folosi <code>public_html<\/code> ca document root pentru fiecare virtual host. \u00cenainte de acest release, conexiunile HTTPS erau servite din <code>private_html<\/code>. Dac\u0103 serverul t\u0103u \u00eenc\u0103 are domenii cu un director <code>private_html<\/code> separat \u00een loc de un symlink c\u0103tre <code>public_html<\/code>, acele site-uri se vor strica dup\u0103 update. Rezolvarea este simpl\u0103, dar trebuie s\u0103 ac\u021bionezi \u00eenainte ca update-ul s\u0103 ajung\u0103 pe serverul t\u0103u sau imediat dup\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest articol explic\u0103 ce s-a schimbat, de ce s-a \u00eent\u00e2mplat asta, care site-uri sunt afectate, cum s\u0103 rulezi taskul de mentenan\u021b\u0103 integrat \u0219i cum s\u0103 verifici totul manual din SSH.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce a schimbat de fapt DirectAdmin \u00een 1.695<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DirectAdmin livreaz\u0103 un set de \u0219abloane de configurare pentru serverul web care genereaz\u0103 fi\u0219ierele efective de virtual host Apache, Nginx sau OpenLiteSpeed pentru fiecare domeniu de pe server. \u00cenainte de versiunea 1.695, \u0219abloanele cu TLS activat setau document rootul pe <code>private_html<\/code>. \u0218abloanele non-TLS indicau spre <code>public_html<\/code>. Asta \u00eensemna c\u0103 HTTP \u0219i HTTPS puteau, din punct de vedere tehnic, s\u0103 serveasc\u0103 con\u021binut diferit din directoare diferite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen practic\u0103, aproape nimeni nu folosea aceast\u0103 func\u021bionalitate. Webul s-a mutat pe HTTPS-everywhere cu ani \u00een urm\u0103, iar servirea de con\u021binut diferit pe HTTP fa\u021b\u0103 de HTTPS creeaz\u0103 mai multe probleme dec\u00e2t rezolv\u0103. DirectAdmin a recunoscut acest lucru \u00eenc\u0103 din versiunea 1.649 (mai 2023), c\u00e2nd a depreciat op\u021biunea pentru directorul <code>private_html<\/code> din skinul Evolution \u0219i a \u00eenceput s\u0103 creeze domenii noi cu un symlink <code>private_html -&gt; public_html<\/code> implicit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Versiunea 1.695 finalizeaz\u0103 treaba. Urm\u0103toarele fi\u0219iere \u0219ablon referen\u021biaz\u0103 acum <code>public_html<\/code> \u00een loc de <code>private_html<\/code>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>data\/templates\/nginx_server_secure.conf<\/code><\/li>\n\n\n\n<li><code>data\/templates\/nginx_server_secure_sub.conf<\/code><\/li>\n\n\n\n<li><code>data\/templates\/openlitespeed_vhost.conf<\/code><\/li>\n\n\n\n<li><code>data\/templates\/virtual_host2_secure.conf<\/code><\/li>\n\n\n\n<li><code>data\/templates\/virtual_host2_secure_sub.conf<\/code><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 acest update, c\u00e2nd un vizitator se conecteaz\u0103 la site-ul t\u0103u prin HTTPS, serverul web caut\u0103 \u00een <code>public_html<\/code>. Dac\u0103 aveai un director <code>private_html<\/code> separat cu fi\u0219ierele reale ale site-ului (nu un symlink), acele fi\u0219iere sunt acum inaccesibile. Vizitatorul prime\u0219te o eroare 403 Forbidden sau vede o list\u0103 de directoare goal\u0103, \u00een func\u021bie de configura\u021bia ta.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cine este afectat<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Majoritatea serverelor nu sunt afectate. \u00cencep\u00e2nd cu DirectAdmin 1.52.0, domeniile noi au fost create cu <code>private_html<\/code> ca symlink care indic\u0103 spre <code>public_html<\/code> \u00een mod implicit. Dac\u0103 serverul t\u0103u a fost instalat \u00een ultimii cinci-\u0219ase ani \u0219i nu ai creat niciodat\u0103 manual directoare <code>private_html<\/code> separate, e\u0219ti \u00een siguran\u021b\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">E\u0219ti la risc dac\u0103 se aplic\u0103 oricare dintre urm\u0103toarele situa\u021bii:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Serverul t\u0103u a fost instalat ini\u021bial \u00eenainte de DirectAdmin 1.52.0 \u0219i domeniile nu au fost niciodat\u0103 migrate la modelul cu symlink.<\/li>\n\n\n\n<li>Tu (sau un administrator anterior) a\u021bi setat <code>default_private_html_link=0<\/code> \u00een <code>\/usr\/local\/directadmin\/conf\/directadmin.conf<\/code> la un moment dat.<\/li>\n\n\n\n<li>Ai migrat conturi de pe alt server sau alt panou de control, iar procesul de migrare a creat directoare <code>private_html<\/code> reale \u00een loc de symlinkuri.<\/li>\n\n\n\n<li>Un utilizator a \u0219ters manual symlinkul \u0219i a creat un director prin skinul Enhanced sau prin SSH.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Din experien\u021ba noastr\u0103 \u00een administrarea serverelor DirectAdmin pentru clien\u021bii de <a href=\"https:\/\/www.serverspan.ro\/webhosting\">web hosting<\/a>, cel mai comun scenariu este cel al conturilor vechi (legacy) care au fost migrate \u00eentre servere cu ani \u00een urm\u0103. Procesul de migrare a p\u0103strat structura original\u0103 a directoarelor, \u0219i nimeni nu a observat, deoarece diferen\u021ba dintre symlink \u0219i director a fost invizibil\u0103 pentru utilizatorul final p\u00e2n\u0103 acum.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cum s\u0103 \u00ee\u021bi verifici serverul \u00eenainte de update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">DirectAdmin ofer\u0103 un task de mentenan\u021b\u0103 integrat special pentru aceast\u0103 situa\u021bie. A fost introdus \u00een versiunea 1.649 \u0219i este accesibil la nivel de Admin \u00een skinul Evolution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Autentific\u0103-te \u00een DirectAdmin ca administrator. Navigheaz\u0103 la <strong>Admin Tools &gt; Maintenance Tasks<\/strong>. Caut\u0103 taskul numit <strong>Ensure all domains private document roots link to public<\/strong>. Ruleaz\u0103-l. Taskul scaneaz\u0103 fiecare cont de utilizator de pe server \u0219i raporteaz\u0103 care domenii \u00eenc\u0103 au un director <code>private_html<\/code> separat \u00een loc de un symlink.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 taskul raporteaz\u0103 zero domenii afectate, po\u021bi face update la 1.695 f\u0103r\u0103 griji. Dac\u0103 raporteaz\u0103 domenii afectate, trebuie s\u0103 rezolvi fiecare cont \u00een parte \u00eenainte de update.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Rezolvarea domeniilor afectate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rezolvarea depinde de faptul dac\u0103 directoarele <code>private_html<\/code> \u0219i <code>public_html<\/code> con\u021bin acelea\u0219i fi\u0219iere sau fi\u0219iere diferite.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenariul 1: private_html are fi\u0219ierele site-ului, public_html este gol sau \u00eenvechit<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Acesta este cel mai frecvent scenariu pe conturile legacy. Site-ul a fost instalat \u00een <code>private_html<\/code> deoarece HTTPS era metoda principal\u0103 de acces, iar <code>public_html<\/code> era fie gol, fie con\u021binea fi\u0219iere \u00eenvechite de la instalarea ini\u021bial\u0103. Rezolvarea este s\u0103 mu\u021bi fi\u0219ierele din <code>private_html<\/code> \u00een <code>public_html<\/code>, s\u0103 \u0219tergi directorul vechi \u0219i s\u0103 creezi symlinkul.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Din SSH, logat ca root sau ca proprietar al domeniului:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cd \/home\/USERNAME\/domains\/DOMAIN.COM\n\n# F\u0103 un backup mai \u00eent\u00e2i\ncp -a private_html private_html.bak\n\n# Mut\u0103 fi\u0219ierele din private_html \u00een public_html\nrsync -av private_html\/ public_html\/\n\n# Verific\u0103 dac\u0103 fi\u0219ierele sunt \u00een public_html\nls -la public_html\/\n\n# \u0218terge directorul vechi\nrm -rf private_html\n\n# Creeaz\u0103 symlinkul\nln -s public_html private_html\n\n# Verific\u0103\nls -la private_html<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Outputul <code>ls -la<\/code> ar trebui s\u0103 arate <code>private_html -&gt; public_html<\/code>. Dac\u0103 este a\u0219a, domeniul va servi acela\u0219i con\u021binut at\u00e2t prin HTTP, c\u00e2t \u0219i prin HTTPS dup\u0103 update.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenariul 2: Ambele directoare con\u021bin con\u021binut diferit<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru este rar, dar posibil. Dac\u0103 cineva a servit \u00een mod inten\u021bionat con\u021binut diferit pe HTTP \u0219i HTTPS, trebuie s\u0103 decizi ce versiune p\u0103strezi. \u00cen aproape toate cazurile pe care le-am \u00eent\u00e2lnit, versiunea din <code>private_html<\/code> este cea de actualitate (deoarece majoritatea traficului este HTTPS), iar <code>public_html<\/code> este dep\u0103\u0219it\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compar\u0103 directoarele:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>diff -rq \/home\/USERNAME\/domains\/DOMAIN.COM\/public_html \\\n         \/home\/USERNAME\/domains\/DOMAIN.COM\/private_html<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Analizeaz\u0103 diferen\u021bele. F\u0103 backup la ambele directoare. Apoi urmeaz\u0103 acela\u0219i proces de rsync, \u0219tergere \u0219i creare de symlink din Scenariul 1, folosind ca surs\u0103 directorul care con\u021bine fi\u0219ierele corecte.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Scenariul 3: Sute de domenii de reparat<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 administrezi un server de reseller cu multe conturi legacy, repararea domeniilor unul c\u00e2te unul nu este practic\u0103. Iat\u0103 un script care identific\u0103 toate directoarele <code>private_html<\/code> reale (nu symlinkuri) \u0219i le converte\u0219te automat. Ruleaz\u0103 acest script ca root. Cite\u0219te scriptul \u00eenainte de a-l executa. F\u0103 backup mai \u00eent\u00e2i.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>#!\/bin\/bash\n# G\u0103se\u0219te toate directoarele private_html care NU sunt symlinkuri\nfind \/home\/*\/domains\/*\/private_html -maxdepth 0 -type d 2&gt;\/dev\/null | while read dir; do\n    domain_dir=$(dirname \"$dir\")\n    public_dir=\"$domain_dir\/public_html\"\n    private_dir=\"$domain_dir\/private_html\"\n\n    echo \"Procesez: $domain_dir\"\n\n    # Verific\u0103 dac\u0103 public_html exist\u0103\n    if &#91; ! -d \"$public_dir\" ]; then\n        echo \"  AVERTISMENT: Niciun public_html g\u0103sit, omit\"\n        continue\n    fi\n\n    # Sincronizeaz\u0103 con\u021binutul din private_html \u00een public_html (p\u0103str\u00e2nd fi\u0219ierele existente \u00een public_html)\n    rsync -a \"$private_dir\/\" \"$public_dir\/\"\n\n    # Redenume\u0219te private_html pentru backup\n    mv \"$private_dir\" \"${private_dir}.bak.$(date +%Y%m%d)\"\n\n    # Creeaz\u0103 symlinkul\n    ln -s public_html \"$private_dir\"\n\n    echo \"  FINALIZAT: Convertit \u00een symlink\"\ndone<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 rularea scriptului, ruleaz\u0103 din nou taskul de mentenan\u021b\u0103 DirectAdmin pentru a confirma c\u0103 au r\u0103mas zero domenii afectate. Dac\u0103 e\u0219ti un furnizor de <a href=\"https:\/\/www.serverspan.ro\/webreseller\">g\u0103zduire reseller<\/a> care administreaz\u0103 conturi de clien\u021bi, coordoneaz\u0103-te cu clien\u021bii t\u0103i \u00eenainte de a \u0219terge directoarele <code>.bak<\/code> pentru ca ace\u0219tia s\u0103 poat\u0103 verifica dac\u0103 site-urile lor func\u021bioneaz\u0103 corect.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A doua modificare pe care nu ar trebui s\u0103 o ignori: Migrarea Secure Access Group<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Release-ul DirectAdmin 1.695 include o alt\u0103 modificare care prime\u0219te mai pu\u021bin\u0103 aten\u021bie, dar care poate cauza probleme de permisiuni pe serverele mai vechi. Update-ul activeaz\u0103 automat op\u021biunea <code>secure_access_group<\/code> \u0219i for\u021beaz\u0103 numele grupului la <code>access<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Grupul de acces securizat face ca serviciile web, de email \u0219i FTP s\u0103 \u00eempart\u0103 grupul UNIX <code>access<\/code>. Aceasta a fost setarea implicit\u0103 pentru instal\u0103rile noi \u00eenc\u0103 de la DirectAdmin 1.33.3, lansat \u00een aprilie 2009. Totu\u0219i, serverele anterioare acestei versiuni, sau serverele unde un administrator a schimbat numele grupului \u00een altceva dec\u00e2t <code>access<\/code>, vor fi afectate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 serverul t\u0103u folose\u0219te un nume personalizat pentru grupul de acces securizat, update-ul 1.695 \u00eel va redenumi \u00een <code>access<\/code>. Acest lucru poate strica configura\u021biile de permisiuni pentru fi\u0219iere care referen\u021biaz\u0103 numele vechi al grupului \u00een ACL-uri, joburi cron sau scripturi personalizate. Verific\u0103-\u021bi configura\u021bia curent\u0103 \u00eenainte de a face update:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>grep secure_access_group \/usr\/local\/directadmin\/conf\/directadmin.conf<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 outputul arat\u0103 <code>secure_access_group=access<\/code> sau op\u021biunea nu este prezent\u0103 (ceea ce \u00eenseamn\u0103 c\u0103 setarea implicit\u0103 este deja \u00een vigoare), nu ai de ce s\u0103 \u00ee\u021bi faci griji. Dac\u0103 arat\u0103 un nume de grup diferit, auditeaz\u0103-\u021bi sistemul pentru orice referin\u021be la acel grup \u00eenainte de a permite instalarea update-ului.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Accesul API OPcache: O repara\u021bie silen\u021bioas\u0103, dar util\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Lansarea 1.695 actualizeaz\u0103, de asemenea, fi\u0219ierul de configurare implicit OPcache (<code>custombuild\/configure\/opcache\/opcache.ini<\/code>) pentru a nu mai bloca accesul la API-ul OPcache. \u00cen versiunile anterioare, configura\u021bia implicit\u0103 seta <code>opcache.restrict_api<\/code> la o valoare care \u00eempiedica scripturile PHP s\u0103 apeleze func\u021bii OPcache precum <code>opcache_reset()<\/code> \u0219i <code>opcache_get_status()<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest lucru conteaz\u0103 dac\u0103 folose\u0219ti instrumente de deployment sau pluginuri WordPress care golesc OPcache-ul dup\u0103 modific\u0103ri de cod. \u00cenainte de aceast\u0103 repara\u021bie, acele instrumente e\u0219uau silen\u021bios sau aruncau erori \u00een func\u021bie de nivelul t\u0103u de raportare a erorilor din PHP. Dac\u0103 ai repornit manual PHP-FPM dup\u0103 deploymenturi deoarece OPcache nu se golea automat, acest update ar putea rezolva acea problem\u0103 de workflow. Pentru o \u00een\u021belegere mai profund\u0103 a modului \u00een care OPcache se integreaz\u0103 \u00een strategia ta general\u0103 de caching, consult\u0103 ghidul nostru despre <a href=\"https:\/\/www.serverspan.com\/en\/blog\/full-page-cache-vs-object-cache-vs-opcode-cache-when-to-use-each\/\">full page cache vs object cache vs opcode cache<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Checklist de verificare post-update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 actualizarea la DirectAdmin 1.695, parcurge aceste verific\u0103ri pentru a confirma c\u0103 nu s-a stricat nimic:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Verific\u0103 dac\u0103 symlinkurile sunt la locul lor.<\/strong> Ruleaz\u0103 aceast\u0103 comand\u0103 ca root pentru a g\u0103si eventualele directoare <code>private_html<\/code> reale r\u0103mase:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>find \/home\/*\/domains\/*\/private_html -maxdepth 0 -type d 2&gt;\/dev\/null | wc -l<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Outputul ar trebui s\u0103 fie <code>0<\/code>. Orice num\u0103r mai mare de zero \u00eenseamn\u0103 c\u0103 \u00eenc\u0103 ai domenii care necesit\u0103 aten\u021bie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. Testeaz\u0103 HTTPS pe un e\u0219antion de domenii.<\/strong> Folose\u0219te <code>curl<\/code> pentru a verifica dac\u0103 HTTPS returneaz\u0103 con\u021binutul a\u0219teptat:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -sI https:\/\/domeniultau.ro | head -20<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caut\u0103 un cod de status <code>200 OK<\/code>. Un <code>403 Forbidden<\/code> sau <code>404 Not Found<\/code> pe un site care func\u021biona \u00eenainte de update indic\u0103 probabil un director <code>private_html<\/code> care nu a fost migrat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. Verific\u0103 grupul de acces securizat.<\/strong> Verific\u0103 dac\u0103 grupul exist\u0103 \u0219i dac\u0103 procesele web sunt membre:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>getent group access<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>4. Rescrie configura\u021bia serverului web.<\/strong> Dac\u0103 ai rezolvat probleme cu <code>private_html<\/code> abia dup\u0103 update, for\u021beaz\u0103 DirectAdmin s\u0103 regenereze toate configura\u021biile de virtual host:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>echo \"action=rewrite&amp;value=httpd\" &gt;&gt; \/usr\/local\/directadmin\/data\/task.queue\necho \"action=rewrite&amp;value=nginx\" &gt;&gt; \/usr\/local\/directadmin\/data\/task.queue<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A\u0219teapt\u0103 c\u00e2teva secunde ca task queue-ul s\u0103 proceseze coada de a\u0219teptare, apoi verific\u0103 din nou site-urile.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>5. Verific\u0103 re\u00eennoirile Let&#8217;s Encrypt.<\/strong> Un build anterior de 1.695 a avut o problem\u0103 \u00een care calea challenge-ului HTTP <code>.well-known<\/code> e\u0219ua c\u00e2nd era redirec\u021bionat\u0103 c\u0103tre HTTPS. Un build ulterior a rezolvat acest lucru. Asigur\u0103-te c\u0103 instan\u021ba ta DirectAdmin este pe cel mai recent build de 1.695 rul\u00e2nd <code>\/usr\/local\/directadmin\/directadmin v<\/code> \u0219i verific\u00e2nd data exact\u0103 a buildului.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De ce a f\u0103cut DirectAdmin aceast\u0103 schimbare acum<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Directorul <code>private_html<\/code> dateaz\u0103 dintr-o perioad\u0103 \u00een care certificatele SSL erau scumpe \u0219i majoritatea traficului era necriptat. Servirea de con\u021binut diferit pe HTTP \u0219i HTTPS avea un caz de utilizare legitim (de\u0219i limitat). Acea er\u0103 s-a \u00eencheiat cu ani \u00een urm\u0103. Certificatele gratuite de la Let&#8217;s Encrypt, avertismentele browserelor pe paginile non-HTTPS \u0219i factorii de ranking ai motoarelor de c\u0103utare au \u00eempins webul c\u0103tre TLS universal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DirectAdmin a \u00eenceput deprecierea \u00een versiunea 1.649 (mai 2023) prin eliminarea comutatorului <code>private_html<\/code> din skinul Evolution. Versiunea 1.650 a f\u0103cut din symlink op\u021biunea implicit\u0103 pentru toate domeniile noi, indiferent de setarea <code>default_private_html_link<\/code> din <code>directadmin.conf<\/code>. Versiunea 1.695 finalizeaz\u0103 procesul prin eliminarea complet\u0103 a referin\u021belor la <code>private_html<\/code> din \u0219abloanele serverului web.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Echipa DirectAdmin a ales s\u0103 nu execute o migrare for\u021bat\u0103 deoarece \u00eembinarea directoarelor cu con\u021binut diferit ar putea cauza pierderi de date. \u00cen schimb, ofer\u0103 taskul de mentenan\u021b\u0103 \u0219i las\u0103 decizia privind momentul execut\u0103rii la latitudinea administratorilor de server. Aceasta este abordarea corect\u0103 pentru o modificare major\u0103 (breaking change): documenteaz\u0103 clar, ofer\u0103 instrumentele necesare \u0219i las\u0103 persoanele care cunosc serverul s\u0103 ia decizia final\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce trebuie s\u0103 fac\u0103 clien\u021bii ServerSpan<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti pe unul dintre planurile noastre de <a href=\"https:\/\/www.serverspan.ro\/webhosting\">g\u0103zduire web<\/a>, ne-am ocupat deja de acest lucru. Infrastructura noastr\u0103 de g\u0103zduire partajat\u0103 ruleaz\u0103 DirectAdmin folosind modelul de symlink pentru toate conturile. Update-ul la 1.695 nu a stricat niciun site deoarece am migrat conturile legacy \u00een timpul unui ciclu anterior de mentenan\u021b\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai un VPS cu DirectAdmin \u0219i \u00eel administrezi singur, acest articol \u00ee\u021bi ofer\u0103 tot ce ai nevoie pentru a-\u021bi verifica \u0219i repara setupul. Dac\u0103 preferi s\u0103 nu te ba\u021bi la cap cu asta, serviciul nostru de <a href=\"https:\/\/www.serverspan.ro\/directadmin-management\">administrare DirectAdmin<\/a> acoper\u0103 exact acest tip de revizuire, audit pre-update, migrare \u0219i verificare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru conturile de reseller care administreaz\u0103 mai mul\u021bi clien\u021bi, acesta este genul de schimbare care separ\u0103 furnizorii proactivi de cei reactivi. Ruleaz\u0103 acum taskul de mentenan\u021b\u0103, repar\u0103 domeniile afectate \u0219i comunic\u0103 schimbarea clien\u021bilor t\u0103i \u00eenainte ca ace\u0219tia s\u0103 o descopere printr-un site c\u0103zut. Dac\u0103 ai nevoie de o platform\u0103 de hosting unde aceste update-uri ale panoului de control sunt gestionate pentru tine, arunc\u0103 o privire la pachetele noastre de <a href=\"https:\/\/www.serverspan.ro\/webreseller\">g\u0103zduire reseller<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 ce rezolvi unificarea <code>private_html<\/code>, ia \u00een considerare revizuirea \u00eentregului pipeline de livrare a site-ului t\u0103u. \u00cembinarea unui setup DirectAdmin configurat corect cu Cloudflare poate elimina o \u00eentreag\u0103 clas\u0103 de probleme de performan\u021b\u0103. Ghidul nostru despre <a href=\"https:\/\/www.serverspan.com\/en\/blog\/how-to-max-out-your-free-cloudflare-plan-the-ultimate-guide-to-rocket-speed-your-website\/\">cum s\u0103 \u00ee\u021bi optimizezi planul Cloudflare gratuit<\/a> detaliaz\u0103 set\u0103rile care conteaz\u0103 cel mai mult. Iar dac\u0103 pui \u00een balan\u021b\u0103 DirectAdmin cu alte panouri pentru urm\u0103torul t\u0103u server, compara\u021bia noastr\u0103 <a href=\"https:\/\/www.serverspan.com\/en\/blog\/directadmin-vs-cpanel-choosing-the-right-hosting-control-panel\/\">DirectAdmin vs cPanel<\/a> explic\u0103 diferen\u021bele practice.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>DirectAdmin 1.695, lansat pe 18 februarie 2026, modific\u0103 toate \u0219abloanele de configurare ale serverului web pentru a folosi public_html ca document root pentru fiecare virtual host. \u00cenainte de acest release, conexiunile HTTPS erau servite din private_html. Dac\u0103 serverul t\u0103u \u00eenc\u0103 are domenii cu un director private_html separat \u00een loc de un symlink c\u0103tre public_html, acele [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2566,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[14335,14340,14346,14342,14343,14344,14347,14345,14339,14338,14336,14337,14348,14341,14349],"class_list":["post-2568","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-hosting","tag-breaking-change-directadmin","tag-document-root-https-directadmin","tag-eroare-403-private_html","tag-fix-opcache-directadmin","tag-gazduire-directadmin-managed","tag-grup-acces-securizat-directadmin","tag-mentenanta-directadmin-evolution","tag-sabloane-server-web-directadmin","tag-symlink-private_html-directadmin","tag-task-de-mentenanta-directadmin","tag-unificare-private_html-public_html","tag-update-directadmin-1-695","tag-update-reseller-directadmin","tag-update-server-directadmin","tag-web-hosting-managed-directadmin"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2568","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=2568"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2568\/revisions"}],"predecessor-version":[{"id":2569,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2568\/revisions\/2569"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2566"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2568"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2568"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2568"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}