{"id":2800,"date":"2026-04-16T10:29:00","date_gmt":"2026-04-16T10:29:00","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-04-16T10:29:01","modified_gmt":"2026-04-16T10:29:01","slug":"cum-activezi-ssh-pe-un-vps-si-te-conectezi-cu-putty-ghid-complet-pentru-toate-familiile-linux-si-bsd","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/cum-activezi-ssh-pe-un-vps-si-te-conectezi-cu-putty-ghid-complet-pentru-toate-familiile-linux-si-bsd\/","title":{"rendered":"SSH pe VPS: activare \u0219i conectare cu PuTTY \u00een 5 minute (Linux \u0219i BSD)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">C\u00e2nd prime\u0219ti un VPS nou, singurul acces disponibil este prin consola NoVNC sau Serial din panoul de control ServerSpan. SSH-ul nu este \u00eentotdeauna activ din start, iar pe majoritatea imaginilor moderne de sistem de operare, autentificarea ca root cu parol\u0103 este dezactivat\u0103 explicit \u00een mod implicit. Ghidul acesta te duce pas cu pas \u2014 de la consol\u0103 p\u00e2n\u0103 la prima sesiune SSH func\u021bional\u0103 \u2014 pentru toate distribu\u021biile majore Linux \u0219i BSD, ca s\u0103 po\u021bi folosi PuTTY, Windows Terminal sau orice alt client SSH f\u0103r\u0103 s\u0103 mai deschizi un ticket de suport.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce este SSH \u0219i de ce ai nevoie de el<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SSH (Secure Shell) este un protocol de re\u021bea criptat care \u00ee\u021bi permite s\u0103 controlezi serverul de la distan\u021b\u0103, de pe orice calculator din lume. \u00cen loc s\u0103 lucrezi prin consola web din panoul de control, deschizi un terminal pe calculatorul t\u0103u \u0219i ai acces imediat la VPS, ca \u0219i cum ai fi \u00een fa\u021ba lui fizic. Consola NoVNC \u0219i Serial din panoul ServerSpan este rezerva ta de urgen\u021b\u0103 \u2014 SSH este modul \u00een care lucrezi efectiv zi de zi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Componenta care ascult\u0103 conexiunile SSH pe server se nume\u0219te <strong>OpenSSH Server<\/strong>, iar procesul care ruleaz\u0103 \u00een fundal se nume\u0219te <code>sshd<\/code>. Calculatorul t\u0103u local folose\u0219te un <em>client<\/em> SSH \u2014 PuTTY pe Windows sau comanda <code>ssh<\/code> inclus\u0103 nativ \u00een Linux \u0219i macOS \u2014 pentru a se conecta la el. Portul implicit al OpenSSH este <strong>22<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 1 \u2014 Deschide consola VPS-ului t\u0103u<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Autentific\u0103-te \u00een <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">panoul de control ServerSpan<\/a>, navigheaz\u0103 la VPS-ul t\u0103u \u0219i deschide fila <strong>Consol\u0103<\/strong> (NoVNC sau Serial). Vei vedea un ecran negru de terminal. Dac\u0103 pare gol, apas\u0103 <kbd>Enter<\/kbd> o dat\u0103 ca s\u0103 apar\u0103 promptul de autentificare. Tasteaz\u0103 <code>root<\/code> \u0219i apas\u0103 <kbd>Enter<\/kbd>, apoi tasteaz\u0103 parola de root. Pe ecran nu apare nimic \u00een timp ce tastezi \u2014 acesta este comportamentul normal \u00een Linux \u0219i BSD, nu o problem\u0103 de tastatur\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu ai setat niciodat\u0103 o parol\u0103 de root sau ai uitat-o, folose\u0219te func\u021bia <strong>Resetare parol\u0103<\/strong> din panoul de control \u00eenainte de a continua. Odat\u0103 autentificat, promptul arat\u0103 astfel:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>root@hostname:~#<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Fiecare comand\u0103 din acest ghid se tasteaz\u0103 aici, \u00een aceast\u0103 fereastr\u0103 de consol\u0103. Nu o \u00eenchide p\u00e2n\u0103 nu confirmi c\u0103 SSH func\u021bioneaz\u0103 de pe calculatorul t\u0103u.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2 \u2014 Identific\u0103 familia sistemului t\u0103u de operare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Managerul de pachete, managerul de servicii \u0219i unele detalii de configurare difer\u0103 \u00eentre distribu\u021bii. Dac\u0103 nu e\u0219ti sigur ce sistem ruleaz\u0103 pe VPS-ul t\u0103u, execut\u0103 aceast\u0103 comand\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cat \/etc\/os-release<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">C\u00e2mpurile <code>NAME<\/code> \u0219i <code>ID_LIKE<\/code> \u00ee\u021bi spun exact cu ce lucrezi. Folose\u0219te tabelul de mai jos ca s\u0103 g\u0103se\u0219ti sec\u021biunea potrivit\u0103:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Distribu\u021bie<\/th><th>Familie<\/th><th>Manager pachete<\/th><th>Nume serviciu<\/th><\/tr><\/thead><tbody><tr><td>Debian, Ubuntu, Linux Mint<\/td><td>Debian\/Ubuntu<\/td><td>apt<\/td><td>ssh<\/td><\/tr><tr><td>Rocky Linux, AlmaLinux, CentOS Stream, RHEL, Fedora<\/td><td>RHEL<\/td><td>dnf<\/td><td>sshd<\/td><\/tr><tr><td>openSUSE Leap, openSUSE Tumbleweed, SLES<\/td><td>SUSE<\/td><td>zypper<\/td><td>sshd<\/td><\/tr><tr><td>Arch Linux, Manjaro, EndeavourOS<\/td><td>Arch<\/td><td>pacman<\/td><td>sshd<\/td><\/tr><tr><td>Alpine Linux<\/td><td>Alpine<\/td><td>apk<\/td><td>sshd<\/td><\/tr><tr><td>FreeBSD, TrueNAS CORE<\/td><td>BSD<\/td><td>pkg<\/td><td>sshd (rc.d)<\/td><\/tr><tr><td>OpenBSD<\/td><td>BSD<\/td><td>pkg_add<\/td><td>sshd (rc.d)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 3 \u2014 Instaleaz\u0103 OpenSSH Server<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 mai \u00eent\u00e2i dac\u0103 serverul SSH este deja instalat \u0219i ruleaz\u0103. Execut\u0103 comanda de verificare corespunz\u0103toare familiei tale:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Debian \/ Ubuntu\nsystemctl status ssh\n\n# RHEL \/ SUSE \/ Arch\nsystemctl status sshd\n\n# Alpine Linux\nrc-status | grep sshd\n\n# FreeBSD \/ OpenBSD\nservice sshd status<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 rezultatul arat\u0103 <code>Active: active (running)<\/code> (Linux) sau <code>sshd is running<\/code> (BSD), serviciul ruleaz\u0103 deja \u0219i po\u021bi trece direct la Pasul 4. Dac\u0103 serviciul nu este g\u0103sit sau nu ruleaz\u0103, instaleaz\u0103-l folosind instruc\u021biunile de mai jos pentru familia ta.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Debian \u0219i Ubuntu<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apt update\napt install openssh-server -y<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Debian \u0219i Ubuntu, serviciul se nume\u0219te <code>ssh<\/code>, nu <code>sshd<\/code>. Instalarea pachetului porne\u0219te \u0219i activeaz\u0103 automat serviciul.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Rocky Linux, AlmaLinux, CentOS Stream, RHEL, Fedora<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dnf install openssh-server -y\nsystemctl enable --now sshd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">OpenSSH vine adesea preinstalat pe imaginile din familia RHEL, dar nu ruleaz\u0103 \u00eentotdeauna automat. Op\u021biunea <code>--now<\/code> porne\u0219te serviciul imediat \u0219i \u00eel marcheaz\u0103 s\u0103 porneasc\u0103 la fiecare repornire a serverului.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">openSUSE Leap \u0219i Tumbleweed \/ SLES<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>zypper install openssh-server -y\nsystemctl enable --now sshd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe openSUSE, fi\u0219ierul de configurare sshd se afl\u0103 la <code>\/etc\/ssh\/sshd_config<\/code>, la fel ca pe orice alt\u0103 familie Linux. Pe Tumbleweed exist\u0103 \u00eens\u0103 \u0219i un fi\u0219ier implicit furnizat de vendor la <code>\/usr\/etc\/ssh\/sshd_config<\/code>. Dac\u0103 dup\u0103 instalare <code>\/etc\/ssh\/sshd_config<\/code> nu exist\u0103, copiaz\u0103 mai \u00eent\u00e2i fi\u0219ierul vendor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cp \/usr\/etc\/ssh\/sshd_config \/etc\/ssh\/sshd_config<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">De acum \u00eenainte, editeaz\u0103 doar <code>\/etc\/ssh\/sshd_config<\/code> a\u0219a cum este descris la Pasul 5. Nu edita niciodat\u0103 fi\u0219ierul din <code>\/usr\/etc\/<\/code> \u2014 este suprascris la actualiz\u0103rile de pachete.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Arch Linux, Manjaro, EndeavourOS<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>pacman -Sy openssh\nsystemctl enable --now sshd<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Imaginile minimale de Arch vin de obicei f\u0103r\u0103 OpenSSH. Pachetul se nume\u0219te <code>openssh<\/code> \u0219i instaleaz\u0103 at\u00e2t clientul c\u00e2t \u0219i serverul dintr-o singur\u0103 comand\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Alpine Linux<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>apk update\napk add openssh-server\nrc-update add sshd\nrc-service sshd start<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Alpine folose\u0219te OpenRC \u00een loc de systemd, deci <code>systemctl<\/code> nu exist\u0103 aici. Comanda <code>rc-update add sshd<\/code> marcheaz\u0103 serviciul s\u0103 porneasc\u0103 la boot; <code>rc-service sshd start<\/code> \u00eel porne\u0219te imediat \u00een sesiunea curent\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">FreeBSD<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">OpenSSH vine preinstalat pe FreeBSD. Tot ce trebuie s\u0103 faci este s\u0103 activezi serviciul. Metoda corect\u0103 este prin <code>sysrc<\/code>, care scrie direct \u00een <code>\/etc\/rc.conf<\/code> cu sintax\u0103 valid\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sysrc sshd_enable=\"YES\"\nservice sshd start<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 preferi s\u0103 editezi manual, deschide <code>\/etc\/rc.conf<\/code> cu editorul <code>ee<\/code> \u2014 disponibil \u00eentotdeauna pe FreeBSD, spre deosebire de nano sau vim \u2014 \u0219i adaug\u0103 linia:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sshd_enable=\"YES\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi porne\u0219te serviciul:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/etc\/rc.d\/sshd start<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">OpenBSD<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">OpenSSH a fost creat de proiectul OpenBSD \u0219i face parte din sistemul de baz\u0103. Nu necesit\u0103 instalare separat\u0103. Activeaz\u0103-l \u0219i porne\u0219te-l cu:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rcctl enable sshd\nrcctl start sshd<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Containere LXC f\u0103r\u0103 systemd<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti pe un container LXC \u0219i <code>systemctl<\/code> returneaz\u0103 mesajul <em>\u201eFailed to connect to bus: No such file or directory&#8221;<\/em>, containerul a fost ini\u021bializat f\u0103r\u0103 systemd. Folose\u0219te \u00een schimb comanda clasic\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>service ssh start      # Debian \/ Ubuntu pe LXC\nservice sshd start     # RHEL, SUSE, Arch pe LXC<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 4 \u2014 Seteaz\u0103 o parol\u0103 pentru root<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pe imaginile de cloud \u0219i VPS, contul root nu are adesea nicio parol\u0103 sau este blocat implicit. Ruleaz\u0103 aceast\u0103 comand\u0103 pentru a seta una:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>passwd root<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Vei fi \u00eentrebat s\u0103 tastezi o parol\u0103 nou\u0103 de dou\u0103 ori. Pe ecran nu apare nimic \u00een timp ce tastezi. Alege ceva puternic \u2014 cel pu\u021bin 12 caractere, cu litere mari, litere mici, cifre \u0219i simboluri. Mesajul de confirmare <code>passwd: password updated successfully<\/code> (sau <code>password changed<\/code> pe BSD) confirm\u0103 c\u0103 opera\u021biunea a reu\u0219it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 5 \u2014 Permite autentificarea root cu parol\u0103 \u00een sshd_config<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Acesta este pasul pe care majoritatea ghidurilor \u00eel trateaz\u0103 superficial \u0219i principala cauz\u0103 pentru care SSH este instalat \u0219i ruleaz\u0103, dar tot refuz\u0103 conexiunea. Distribu\u021biile moderne fie blocheaz\u0103 complet autentificarea ca root, fie o permit numai prin perechi de chei SSH, nu prin parol\u0103. Trebuie s\u0103 modifici dou\u0103 directive \u00een fi\u0219ierul de configurare al daemonului SSH.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe orice distribu\u021bie Linux, fi\u0219ierul principal de configurare se afl\u0103 la:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/etc\/ssh\/sshd_config<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe FreeBSD \u0219i OpenBSD calea este identic\u0103: <code>\/etc\/ssh\/sshd_config<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deschide fi\u0219ierul cu editorul disponibil pe sistemul t\u0103u:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nano \/etc\/ssh\/sshd_config    # Debian, Ubuntu, Rocky, SUSE, Arch\nee \/etc\/ssh\/sshd_config      # FreeBSD (ee este \u00eentotdeauna prezent)\nvi \/etc\/ssh\/sshd_config      # Alpine, OpenBSD, sau orice sistem f\u0103r\u0103 nano<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caut\u0103 linia care con\u021bine <code>PermitRootLogin<\/code>. Pe diferite distribu\u021bii arat\u0103 astfel:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>#PermitRootLogin prohibit-password\nPermitRootLogin prohibit-password\nPermitRootLogin no\n#PermitRootLogin yes<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Modific\u0103-o \u2014 sau adaug-o dac\u0103 lipse\u0219te \u2014 astfel \u00eenc\u00e2t s\u0103 arate exact:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PermitRootLogin yes<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Elimin\u0103 <code>#<\/code> de la \u00eenceputul liniei dac\u0103 exist\u0103. Liniile care \u00eencep cu <code>#<\/code> sunt comentarii \u0219i nu au niciun efect, indiferent de con\u021binut.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acum caut\u0103 linia care con\u021bine <code>PasswordAuthentication<\/code> \u0219i f\u0103-o s\u0103 arate:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PasswordAuthentication yes<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Salveaz\u0103 fi\u0219ierul. \u00cen nano: <kbd>Ctrl+X<\/kbd>, apoi <kbd>Y<\/kbd>, apoi <kbd>Enter<\/kbd>. \u00cen <code>ee<\/code>: <kbd>Esc<\/kbd>, apoi alege <strong>a) leave editor, saving changes<\/strong>. \u00cen <code>vi<\/code>: apas\u0103 <kbd>Esc<\/kbd>, tasteaz\u0103 <code>:wq<\/code>, apas\u0103 <kbd>Enter<\/kbd>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ubuntu 22.04 \u0219i Ubuntu 24.04 \u2014 directorul de configur\u0103ri suplimentare<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ubuntu 22.04 \u0219i versiunile ulterioare au un director de suprasciere la <code>\/etc\/ssh\/sshd_config.d\/<\/code>. Fi\u0219ierele din acest director au prioritate fa\u021b\u0103 de <code>sshd_config<\/code> principal, ceea ce \u00eenseamn\u0103 c\u0103 modific\u0103rile tale de mai sus pot fi ignorate \u00een t\u0103cere dac\u0103 exist\u0103 o setare conflictual\u0103 \u00eentr-un fi\u0219ier drop-in. Verific\u0103 ce se afl\u0103 acolo:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls \/etc\/ssh\/sshd_config.d\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">De obicei vei g\u0103si un fi\u0219ier numit <code>50-cloud-init.conf<\/code>. Deschide-l:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nano \/etc\/ssh\/sshd_config.d\/50-cloud-init.conf<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 con\u021bine <code>PasswordAuthentication no<\/code>, schimb\u0103-l \u00een <code>PasswordAuthentication yes<\/code> \u0219i salveaz\u0103. Acesta este motivul cel mai frecvent pentru care autentificarea cu parol\u0103 pare s\u0103 nu func\u021bioneze pe Ubuntu, chiar dup\u0103 ce fi\u0219ierul principal a fost editat corect.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">openSUSE \u2014 fi\u0219ierul de configurare vendor<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Tumbleweed, dac\u0103 ai s\u0103rit pasul de copiere din Pasul 3 \u0219i <code>\/etc\/ssh\/sshd_config<\/code> nu exist\u0103, daemonul cite\u0219te din <code>\/usr\/etc\/ssh\/sshd_config<\/code>. Nu edita niciodat\u0103 fi\u0219ierul de sub <code>\/usr\/etc\/<\/code> \u2014 este suprascris la actualiz\u0103rile de pachete. Copiaz\u0103-l mai \u00eent\u00e2i conform instruc\u021biunilor din Pasul 3, apoi editeaz\u0103 copia din <code>\/etc\/ssh\/<\/code>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 6 \u2014 Reporne\u0219te serviciul SSH<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Modific\u0103rile din <code>sshd_config<\/code> intr\u0103 \u00een vigoare numai dup\u0103 repornirea daemonului. Folose\u0219te comanda potrivit\u0103 sistemului t\u0103u:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Debian \/ Ubuntu\nsystemctl restart ssh\n\n# Rocky Linux, AlmaLinux, CentOS, RHEL, Fedora, SUSE, Arch\nsystemctl restart sshd\n\n# Alpine Linux\nrc-service sshd restart\n\n# FreeBSD\nservice sshd restart\n\n# OpenBSD\nrcctl restart sshd\n\n# Containere LXC f\u0103r\u0103 systemd (Debian\/Ubuntu)\nservice ssh restart\n\n# Containere LXC f\u0103r\u0103 systemd (RHEL\/SUSE\/Arch)\nservice sshd restart<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 repornire, verific\u0103 c\u0103 serviciul a revenit corect:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Linux cu systemd\nsystemctl status ssh      # sau sshd\n\n# Alpine\nrc-service sshd status\n\n# FreeBSD \/ OpenBSD\nservice sshd status<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de a reporni, po\u021bi verifica dac\u0103 fi\u0219ierul de configurare are erori de sintax\u0103 \u2014 acest lucru evit\u0103 situa\u021bia \u00een care daemonul refuz\u0103 s\u0103 porneasc\u0103 din cauza unei gre\u0219eli de scriere:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sshd -t<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 aceast\u0103 comand\u0103 nu returneaz\u0103 nimic, sintaxa este valid\u0103. Dac\u0103 afi\u0219eaz\u0103 o eroare, \u00ee\u021bi va indica exact ce linie din fi\u0219ier este gre\u0219it\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 7 \u2014 G\u0103se\u0219te adresa IP a VPS-ului t\u0103u<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Adresa IP a VPS-ului este afi\u0219at\u0103 \u00een panoul de control ServerSpan, pe pagina de prezentare a VPS-ului. O po\u021bi afla \u0219i direct din consol\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Linux\nip a\n\n# FreeBSD \/ OpenBSD\nifconfig<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Caut\u0103 o adres\u0103 care nu este <code>127.0.0.1<\/code> (loopback) \u0219i nu este din intervalele private <code>10.x.x.x<\/code> sau <code>172.x.x.x<\/code>, dac\u0103 VPS-ul nu este \u00een spatele unui NAT. Adresa ta IPv4 public\u0103 va ar\u0103ta de obicei ca <code>185.x.x.x<\/code> sau <code>45.x.x.x<\/code> \u00een func\u021bie de loca\u021bia centrului de date.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 8 \u2014 Conectare din Windows cu PuTTY<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PuTTY este un client SSH gratuit pentru Windows. Descarc\u0103-l de pe site-ul oficial <strong>putty.org<\/strong> \u0219i instaleaz\u0103-l. Deschide PuTTY \u0219i completeaz\u0103 fereastra de configurare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u00cen c\u00e2mpul <strong>Host Name (or IP address)<\/strong>, tasteaz\u0103 adresa IP a VPS-ului t\u0103u<\/li>\n\n\n\n<li>Confirm\u0103 c\u0103 <strong>Port<\/strong> este setat la <code>22<\/code><\/li>\n\n\n\n<li>Confirm\u0103 c\u0103 <strong>Connection type<\/strong> este setat la <strong>SSH<\/strong><\/li>\n\n\n\n<li>Apas\u0103 <strong>Open<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">La prima conectare la un server nou, PuTTY afi\u0219eaz\u0103 un avertisment de securitate: <em>\u201eThe host key is not cached for this server.&#8221;<\/em> Acesta este comportamentul a\u0219teptat pe un server pe care tocmai l-ai configurat. Apas\u0103 <strong>Accept<\/strong>. PuTTY salveaz\u0103 amprenta serverului pentru a te putea avertiza dac\u0103 se schimb\u0103 \u00een viitor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Se deschide o fereastr\u0103 de terminal cu promptul <code>login as:<\/code>. Tasteaz\u0103 <code>root<\/code> \u0219i apas\u0103 <kbd>Enter<\/kbd>. Tasteaz\u0103 parola de root \u0219i apas\u0103 <kbd>Enter<\/kbd>. Parola nu apare pe ecran \u00een timp ce tastezi \u2014 este o decizie de proiectare deliberat\u0103, nu o defec\u021biune. Dac\u0103 datele sunt corecte, vei ajunge la:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>root@hostname:~#<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">E\u0219ti conectat. Po\u021bi \u00eenchide acum consola NoVNC din panoul de control \u0219i lucra exclusiv prin PuTTY.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 9 \u2014 Conectare din Linux sau macOS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deschide un terminal \u0219i tasteaz\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh root@IP_VPS_TAU<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">La prima conectare vei vedea un avertisment despre amprenta serverului. Tasteaz\u0103 <code>yes<\/code> \u0219i apas\u0103 <kbd>Enter<\/kbd> pentru a o accepta. Introdu parola de root c\u00e2nd \u021bi se cere. Pe ecran nu apare nimic \u00een timp ce tastezi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Probleme frecvente \u0219i cum le rezolvi<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Connection refused pe portul 22<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Serviciul SSH nu ruleaz\u0103 sau un firewall blocheaz\u0103 portul. \u00centoarce-te la consola NoVNC, verific\u0103 statusul serviciului \u0219i apoi verific\u0103 dac\u0103 un firewall de gazd\u0103 este activ. Pe Debian\/Ubuntu cu UFW:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw allow 22\/tcp &amp;&amp; ufw reload<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Rocky Linux \/ AlmaLinux \/ RHEL cu firewalld:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>firewall-cmd --permanent --add-service=ssh &amp;&amp; firewall-cmd --reload<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe openSUSE cu firewalld, comanda este identic\u0103. Pe Arch Linux niciun firewall nu este activ implicit, deci o conexiune refuzat\u0103 indic\u0103 de obicei c\u0103 serviciul nu ruleaz\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe FreeBSD, dac\u0103 <code>pf<\/code> este activat, adaug\u0103 o regul\u0103 de permisiune pentru portul 22 \u00een <code>\/etc\/pf.conf<\/code> \u0219i ruleaz\u0103 <code>pfctl -f \/etc\/pf.conf<\/code>. Pe OpenBSD, <code>pf<\/code> este activ implicit \u2014 editeaz\u0103 <code>\/etc\/pf.conf<\/code> \u0219i adaug\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pass in on egress proto tcp from any to any port 22<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aplic\u0103 regula: <code>pfctl -f \/etc\/pf.conf<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Permission denied, please try again<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">SSH func\u021bioneaz\u0103, dar datele de autentificare sunt respinse. Cele mai frecvente trei cauze: parola introdus\u0103 este gre\u0219it\u0103, <code>PermitRootLogin<\/code> nu este \u00eenc\u0103 setat la <code>yes<\/code>, sau <code>PasswordAuthentication<\/code> este \u00een continuare <code>no<\/code> \u00eentr-un fi\u0219ier de suprasciere. Verific\u0103 configura\u021bia activ\u0103 pe care daemonul o folose\u0219te efectiv la rulare, f\u0103r\u0103 a-l reporni:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sshd -T | grep -E \"permitrootlogin|passwordauthentication\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 oricare dintre linii arat\u0103 o valoare restrictiv\u0103, modificarea nu a fost aplicat\u0103. \u00centoarce-te la Pasul 5, verific\u0103 fi\u0219ierul principal \u0219i orice fi\u0219ier drop-in din <code>\/etc\/ssh\/sshd_config.d\/<\/code> pe Ubuntu, apoi reporne\u0219te serviciul.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pe ecran nu apare nimic c\u00e2nd tastez parola<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Nu este o problem\u0103. Terminalele Linux \u0219i BSD nu afi\u0219eaz\u0103 parolele \u00een timp ce le tastezi \u2014 nici caractere, nici asteriscuri, nimic. Tasteaz\u0103 parola \u0219i apas\u0103 <kbd>Enter<\/kbd>. Dac\u0103 e\u0219ueaz\u0103, po\u021bi \u00eencerca din nou. Dup\u0103 mai multe e\u0219ecuri consecutive serverul \u00ee\u021bi poate bloca temporar adresa IP. A\u0219teapt\u0103 dou\u0103 minute \u00eenainte de a re\u00eencerca.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Apare c\u00e2nd ai reinstalat sistemul de operare pe VPS \u0219i \u00eencerci s\u0103 te reconectezi de pe un calculator care are salvat\u0103 amprenta veche a serverului. Deoarece reinstalarea a fost f\u0103cut\u0103 de tine, este sigur s\u0103 \u0219tergi intrarea veche. Pe Linux \u0219i macOS:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh-keygen -R IP_VPS_TAU<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen PuTTY pe Windows, mergi la <strong>Registry Editor \u2192 HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\SshHostKeys<\/strong> \u0219i \u0219terge intrarea corespunz\u0103toare adresei IP, apoi reconecteaz\u0103-te \u0219i accept\u0103 noua amprent\u0103.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">SSH porne\u0219te dar se opre\u0219te imediat pe Alpine sau pe containere minimale<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Daemonul SSH are nevoie de chei de gazd\u0103 generate \u00eenainte s\u0103 poat\u0103 porni. Dac\u0103 ai instalat OpenSSH pe o imagine de container f\u0103r\u0103 ele, genereaz\u0103-le manual:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh-keygen -A<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Porne\u0219te din nou serviciul dup\u0103 aceea.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce faci mai departe<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Autentificarea ca root cu parol\u0103 este cel mai rapid mod de a \u00eencepe, dar odat\u0103 ce te-ai obi\u0219nuit cu serverul, ar trebui s\u0103 faci doi pa\u0219i suplimentari: treci la autentificarea cu perechi de chei SSH \u0219i dezactivezi autentificarea prin parol\u0103, apoi mu\u021bi SSH de pe portul implicit 22 pe un port non-standard. Ambii pa\u0219i elimin\u0103 cov\u00e2r\u0219itoarea majoritate a atacurilor automate de tip brute-force pe care orice server expus pe internet le prime\u0219te \u00een c\u00e2teva minute de la provisioning. Ghidul nostru <a href=\"https:\/\/www.serverspan.ro\/blog\/ghid-practic-pentru-securizarea-vps-15-pasi-esentiali-de-securitate-pentru-servere-linux\/\">practic de securizare VPS cu 15 pa\u0219i esen\u021biali<\/a> acoper\u0103 ambele \u00een detaliu, \u00eempreun\u0103 cu fail2ban, actualiz\u0103ri automate \u0219i reguli de firewall.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 acesta este primul t\u0103u VPS \u0219i nu \u0219tii \u00eenc\u0103 ce s\u0103 instalezi pe el dincolo de SSH, <a href=\"https:\/\/www.serverspan.ro\/blog\/ghid-complet-de-configurare-vps-linux-pentru-incepatori\/\">ghidul complet de configurare VPS Linux pentru \u00eencep\u0103tori<\/a> acoper\u0103 configurarea hostname-ului \u0219i a fusului orar, gestionarea utilizatorilor, instalarea unui server web \u0219i configurarea monitoriz\u0103rii de baz\u0103. Pentru ajutor direct cu oricare pas de configurare, <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">serviciul de administrare Linux administrat al ServerSpan<\/a> este disponibil pentru asisten\u021b\u0103 tehnic\u0103 punctual\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Toate <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">planurile VPS ServerSpan<\/a> \u2014 KVM \u0219i LXC \u2014 vin cu acces root complet \u0219i consol\u0103 NoVNC\/Serial disponibil\u0103 din prima zi. Dac\u0103 SSH tot nu func\u021bioneaz\u0103 dup\u0103 ce ai urmat acest ghid, deschide un ticket de suport \u0219i include <strong>mesajul exact de eroare<\/strong> afi\u0219at \u00een PuTTY sau \u00een terminal. \u201eNu m\u0103 pot conecta prin SSH&#8221; dureaz\u0103 mult mai mult de diagnosticat dec\u00e2t \u201ev\u0103d <code>Permission denied (publickey,gssapi-keyex,gssapi-with-mic)<\/code>&#8221; sau \u201eConnection refused pe portul 22.&#8221; Mesajul de eroare ne spune exact unde \u00een lan\u021b se afl\u0103 problema.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>C\u00e2nd prime\u0219ti un VPS nou, singurul acces disponibil este prin consola NoVNC sau Serial din panoul de control ServerSpan. SSH-ul nu este \u00eentotdeauna activ din start, iar pe majoritatea imaginilor moderne de sistem de operare, autentificarea ca root cu parol\u0103 este dezactivat\u0103 explicit \u00een mod implicit. Ghidul acesta te duce pas cu pas \u2014 de [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2798,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,12],"tags":[15688,15689,15694,15691,15684,15685,15686,15682,15697,15670,15692,15702,15681,15701,15690,15683,15696,15678,15673,15699,15662,15687,15676,15700,15695,15693,15703,15663,15674,15698,15672],"class_list":["post-2800","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","category-virtual-servers","tag-activare-ssh-alpine-linux","tag-activare-ssh-arch-linux","tag-activare-ssh-freebsd","tag-activare-ssh-openbsd","tag-activare-ssh-opensuse","tag-activare-ssh-rocky-linux-almalinux","tag-activare-ssh-root-login-debian","tag-activare-ssh-root-login-ubuntu","tag-activare-sshd-rocky-linux-almalinux-rhel","tag-apk-add-openssh-alpine","tag-conectare-vps-putty-tutorial","tag-container-lxc-systemd-ssh-failed-connect-bus","tag-cum-activezi-ssh-pe-vps","tag-cum-folosesti-putty-ssh-incepatori","tag-ghid-configurare-ssh-vps-incepatori","tag-instalare-openssh-server-linux","tag-instalare-openssh-server-ubuntu-debian","tag-opensuse-usr-etc-ssh-sshd_config-vendor","tag-pacman-install-openssh-arch","tag-parola-ssh-nu-apare-terminal-normal","tag-passwordauthentication-yes-sshd_config","tag-permite-autentificare-root-ssh-parola","tag-rcctl-enable-sshd-openbsd","tag-remote-host-identification-changed-rezolvare-ssh-keygen","tag-ssh-connection-refused-port-22-remediere","tag-ssh-permission-denied-parola-remediere","tag-sshd-t-verificare-configuratie-ssh-activa","tag-sshd_config-permitrootlogin-yes","tag-sysrc-sshd_enable-freebsd","tag-ubuntu-sshd_config-d-suprasciere-50-cloud-init","tag-zypper-install-openssh-server-opensuse"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2800","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=2800"}],"version-history":[{"count":1,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2800\/revisions"}],"predecessor-version":[{"id":2801,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2800\/revisions\/2801"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2798"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2800"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2800"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}