{"id":2716,"date":"2026-03-26T20:18:45","date_gmt":"2026-03-26T20:18:45","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-03-26T20:38:09","modified_gmt":"2026-03-26T20:38:09","slug":"cum-sa-instalezi-si-configurezi-openclaw-pe-vps-ul-tau-serverspan-linux-runbook-complet-2026-cu-qwen-oauth-1-000-de-cereri-gratuite-pe-zi","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/cum-sa-instalezi-si-configurezi-openclaw-pe-vps-ul-tau-serverspan-linux-runbook-complet-2026-cu-qwen-oauth-1-000-de-cereri-gratuite-pe-zi\/","title":{"rendered":"Cum s\u0103 instalezi \u0219i configurezi OpenClaw pe VPS-ul t\u0103u ServerSpan Linux: Runbook complet 2026 cu Qwen OAuth (1.000 de cereri gratuite pe zi)"},"content":{"rendered":"\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei s\u0103 \u00ee\u021bi g\u0103zduie\u0219ti singur Clawdbot, ast\u0103zi redenumit OpenClaw, pe un VPS Linux, r\u0103spunsul corect \u00een 2026 este s\u0103 \u00eel instalezi pe un server Debian sau RHEL curat, s\u0103 \u00eel rulezi sub un utilizator Linux dedicat, s\u0103 \u021bii Node pe o cale de sistem predictibil\u0103, s\u0103 folose\u0219ti fluxul oficial de onboarding \u0219i s\u0103 tratezi Qwen cu cap. Vechea integrare OAuth nativ\u0103 din OpenClaw pentru Qwen Portal nu mai exist\u0103. Varianta practic\u0103 pentru nivelul gratuit este acum Qwen Code OAuth pe acela\u0219i VPS, urmat de onboarding \u00een OpenClaw \u0219i verificarea efectiv\u0103 a autentific\u0103rii. Dac\u0103 importul nu se face curat pe versiunea ta, treci pe Model Studio \u0219i mergi mai departe. Nu pierde ore \u00eentregi \u00eencerc\u00e2nd s\u0103 re\u00eenvii un provider care a fost scos.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Distinc\u021bia asta conteaz\u0103 mult, pentru c\u0103 o parte dintre tutorialele ap\u0103rute deja \u00een 2026 sunt \u00eenvechite. Multe descriu \u00eenc\u0103 vechea denumire Clawdbot, vechi fluxuri de autentificare sau instal\u0103ri \u201eone-click\u201d care nu spun nimic despre unde ajung creden\u021bialele, ce serviciu r\u0103m\u00e2ne pornit dup\u0103 logout, pe ce port ascult\u0103 gateway-ul sau cum sunt legate Telegram \u0219i providerul de model. Pe un VPS, exact detaliile acestea fac diferen\u021ba dintre \u201es-a instalat\u201d \u0219i \u201e\u00eenc\u0103 func\u021bioneaz\u0103 \u0219i s\u0103pt\u0103m\u00e2na viitoare\u201d.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acest runbook \u00ee\u021bi d\u0103 traseul de instalare care chiar are sens pe un VPS Linux ServerSpan: alegerea corect\u0103 a runtime-ului, instalare curat\u0103 a daemonului, un bootstrap realist cu Qwen Code OAuth, configurare Telegram, c\u0103i de config, loca\u021bii de loguri \u0219i modurile obi\u0219nuite \u00een care lucrurile se stric\u0103 atunci c\u00e2nd sari peste partea plictisitoare. Dac\u0103 ai nevoie de un loc curat unde s\u0103 \u00eel rulezi, \u00eencepe cu <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">Serverele Virtuale ServerSpan<\/a>. Dac\u0103 vrei aplica\u021bia, dar nu \u0219i munca Linux din jurul ei, aici <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">Administrarea Linux ServerSpan<\/a> \u00eencepe s\u0103 fie alegerea ra\u021bional\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ce s-a schimbat \u00een 2026 \u0219i de ce trebuie s\u0103 \u021bii cont de asta \u00eenainte s\u0103 \u00eencepi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Exist\u0103 trei lucruri importante pe care trebuie s\u0103 le \u00een\u021belegi \u00eenainte s\u0103 tastezi prima comand\u0103.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clawdbot se nume\u0219te acum OpenClaw. Dac\u0103 cau\u021bi ambele nume, vei g\u0103si ghiduri care se suprapun, dar nu mai spun exact acela\u0219i lucru.<\/li>\n<li>Documenta\u021bia curent\u0103 OpenClaw pentru Qwen spune clar c\u0103 vechiul flux <code>qwen-portal<\/code> OAuth a fost eliminat.<\/li>\n<li>Qwen Code continu\u0103 s\u0103 promoveze Qwen OAuth cu 1.000 de cereri gratuite pe zi, iar de aici porne\u0219te ideea de a-l folosi ca bootstrap pe un VPS OpenClaw.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Din combina\u021bia asta rezult\u0103 singura abordare s\u0103n\u0103toas\u0103 \u00een 2026. Folose\u0219ti fluxul actual de instalare \u0219i gateway din OpenClaw, dar tratezi Qwen Code OAuth ca pe o metod\u0103 de pornire, nu ca pe o integrare veche pe care o po\u021bi resuscita la infinit. \u00cen practic\u0103, asta \u00eenseamn\u0103 c\u0103 instalezi mai \u00eent\u00e2i Qwen Code, te autentifici o dat\u0103, apoi instalezi \u0219i configurezi OpenClaw \u0219i verifici explicit dac\u0103 importul de creden\u021biale s-a f\u0103cut. Dac\u0103 nu s-a f\u0103cut, nu \u00eencepi s\u0103 improvizezi pe baza unor tutoriale moarte. Treci pe varianta suportat\u0103 oficial \u0219i p\u0103strezi deployment-ul administrabil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">De aici vine \u0219i alt\u0103 concluzie important\u0103: ghidurile de tip \u201einstaleaz\u0103 cu un singur click\u201d sunt aproape inutile dac\u0103 nu \u00ee\u021bi arat\u0103 c\u0103ile reale, fi\u0219ierele \u0219i logurile relevante. O instalare pe VPS nu este terminat\u0103 c\u00e2nd botul r\u0103spunde o dat\u0103. Este terminat\u0103 c\u00e2nd gateway-ul supravie\u021buie\u0219te dup\u0103 logout, autentificarea este salvat\u0103 unde te a\u0219tep\u021bi, Telegram func\u021bioneaz\u0103 stabil \u0219i \u0219tii exact unde te ui\u021bi c\u00e2nd ceva cedeaz\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">LXC sau KVM: pe ce tip de VPS ar trebui s\u0103 rulezi OpenClaw<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">OpenClaw nu este o aplica\u021bie deosebit de grea, dar are nevoie de un runtime curat \u0219i de un comportament predictibil la nivel de re\u021bea \u0219i procese. Din motivul acesta, este un workload potrivit at\u00e2t pentru un LXC generos, c\u00e2t \u0219i pentru un KVM mic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un LXC generos este, de obicei, suficient atunci c\u00e2nd:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>vrei overhead mai mic<\/li>\n<li>e\u0219ti confortabil cu utilizatori Linux, systemd \u0219i utilitare CLI persistente<\/li>\n<li>nu construie\u0219ti peste el un stack ciudat cu Docker peste Docker sau alte nesting-uri inutile<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Un KVM mic este, de regul\u0103, alegerea mai bun\u0103 atunci c\u00e2nd:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>vrei o grani\u021b\u0103 de izolare mai curat\u0103<\/li>\n<li>te a\u0219tep\u021bi s\u0103 adaugi reverse proxy, monitorizare, agen\u021bi de backup sau alte servicii auxiliare<\/li>\n<li>vrei c\u00e2t mai pu\u021bine cazuri-limit\u0103 legate de namespaces \u0219i comportamentul runtime-ului<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru un punct de pornire practic, 2 vCPU \u0219i 4 GB RAM reprezint\u0103 un minim s\u0103n\u0103tos. Dac\u0103 \u00eencepi s\u0103 adaugi \u0219i alte unelte, joburi mai lungi sau mai multe canale de chat, 6 GB RAM \u00ee\u021bi ofer\u0103 mai mult spa\u021biu de manevr\u0103. OpenClaw \u00een sine nu este problema. Tot ce pui pe l\u00e2ng\u0103 el este ceea ce consum\u0103 resursele prima dat\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei pu\u021bin context intern \u00eenainte de deployment, cele mai potrivite articole ServerSpan sunt <a href=\"https:\/\/www.serverspan.ro\/blog\/ghid-complet-de-configurare-vps-linux-pentru-incepatori\/\">Ghid complet de configurare VPS Linux pentru \u00eencep\u0103tori<\/a>, <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-securizezi-un-vps-proaspat-un-ghid-cuprinzator-pentru-incepatori-in-linux\/\">Cum s\u0103 securizezi un VPS proasp\u0103t<\/a> \u0219i <a href=\"https:\/\/www.serverspan.ro\/blog\/gestionarea-docker-si-a-containerelor-pe-un-vps-cele-mai-bune-practici-pentru-stabilitate-si-performanta\/\">Gestionarea Docker \u0219i a containerelor pe un VPS<\/a>. Chiar dac\u0103 aici nu rulezi neap\u0103rat Docker, disciplina opera\u021bional\u0103 r\u0103m\u00e2ne aceea\u0219i.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 1: preg\u0103te\u0219te VPS-ul Linux cum trebuie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Nu instala OpenClaw ca root \u0219i nu declara victoria. Folose\u0219te un utilizator Linux dedicat, astfel \u00eenc\u00e2t gateway-ul, configura\u021bia, creden\u021bialele \u0219i unitatea systemd de utilizator s\u0103 ajung\u0103 \u00eentr-un loc previzibil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Debian sau Ubuntu:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apt update\napt upgrade -y\napt install -y curl ca-certificates git jq tmux sudo\n\nadduser openclaw\nusermod -aG sudo openclaw\n\nloginctl enable-linger openclaw<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe RHEL, AlmaLinux, Rocky Linux sau sisteme compatibile:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dnf update -y\ndnf install -y curl ca-certificates git jq tmux sudo\n\nuseradd -m -s \/bin\/bash openclaw\npasswd openclaw\nusermod -aG wheel openclaw\n\nloginctl enable-linger openclaw<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pasul cu <code>loginctl enable-linger<\/code> nu este decorativ. OpenClaw folose\u0219te pe Linux o unitate systemd de utilizator. Dac\u0103 sari peste linger, creezi exact problema clasic\u0103: totul merge c\u00e2t timp e\u0219ti logat, apoi moare frumos dup\u0103 logout.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 aceea, intr\u0103 pe utilizatorul nou \u0219i f\u0103 toat\u0103 instalarea sub acel cont:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>su - openclaw\nmkdir -p ~\/.openclaw\nchmod 700 ~\/.openclaw<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 2: instaleaz\u0103 mai \u00eent\u00e2i Qwen Code dac\u0103 vrei \u00een mod explicit ruta gratuit\u0103 prin OAuth<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aici mul\u021bi procedeaz\u0103 exact invers. Dac\u0103 obiectivul t\u0103u este Qwen Code OAuth, instalezi \u0219i autentifici mai \u00eent\u00e2i Qwen Code, apoi faci onboarding \u00een OpenClaw. Asta \u00eei ofer\u0103 lui OpenClaw ceva concret de importat, dac\u0103 versiunea ta \u00eenc\u0103 sincronizeaz\u0103 creden\u021bialele locale ale CLI-ului.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>bash -c \"$(curl -fsSL https:\/\/qwen-code-assets.oss-cn-hangzhou.aliyuncs.com\/installation\/install-qwen.sh)\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi redeschide shell-ul sau re\u00eencarc\u0103 profilul, dac\u0103 este nevoie, \u0219i porne\u0219te Qwen Code:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>qwen<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen sesiunea interactiv\u0103, ruleaz\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/auth<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Finalizeaz\u0103 autentificarea \u00een browser cu contul t\u0103u Qwen. Dac\u0103 totul merge corect, Qwen Code va salva local creden\u021bialele OAuth \u00een directorul utilizatorului. Pe Linux, fi\u0219ierul care conteaz\u0103 este:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>~\/.qwen\/oauth_creds.json<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 explicit c\u0103 exist\u0103 \u00eenainte s\u0103 mergi mai departe:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -lah ~\/.qwen\njq . ~\/.qwen\/oauth_creds.json | head<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 fi\u0219ierul acesta nu exist\u0103, opre\u0219te-te aici. OpenClaw nu poate importa creden\u021biale care nu sunt prezente pe server. Nu continua presupun\u00e2nd c\u0103 \u201ese rezolv\u0103 pe parcurs\u201d.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 3: instaleaz\u0103 OpenClaw pe calea suportat\u0103 oficial<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Documenta\u021bia actual\u0103 OpenClaw este clar\u0103: pe Linux, pentru un gateway stabil, mai ales dac\u0103 vrei Telegram, folose\u0219ti Node, nu Bun. Cea mai rapid\u0103 cale suportat\u0103 este scriptul oficial de instalare.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsSL https:\/\/openclaw.ai\/install.sh | bash<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei instalarea f\u0103r\u0103 s\u0103 intre imediat \u00een onboarding, folose\u0219te:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>curl -fsSL https:\/\/openclaw.ai\/install.sh | bash -s -- --no-onboard<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi verific\u0103 faptul c\u0103 CLI-ul exist\u0103 cu adev\u0103rat:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw --version\nnode --version<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 preferi o instalare explicit\u0103 prin npm \u00een locul scriptului:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>npm install -g openclaw@latest\nopenclaw onboard --install-daemon<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pe un VPS, scriptul oficial este \u00een general varianta mai curat\u0103, pentru c\u0103 \u00ee\u021bi rezolv\u0103 inclusiv partea de Node, dac\u0103 este nevoie, \u0219i te \u021bine mai aproape de calea suportat\u0103 de proiect.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 4: ruleaz\u0103 onboarding-ul \u0219i trateaz\u0103 Qwen \u00een mod realist<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Acum po\u021bi lansa onboarding-ul propriu-zis:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw onboard --install-daemon<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aici trebuie s\u0103 iei decizia corect\u0103 pentru 2026.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dac\u0103 vrei ruta Qwen suportat\u0103 oficial de OpenClaw, alegi Model Studio c\u00e2nd \u021bi se cere providerul.<\/li>\n<li>Dac\u0103 vrei ruta gratuit\u0103 prin Qwen Code OAuth, continui numai dac\u0103 ai autentificat deja Qwen Code pe acest VPS \u0219i e\u0219ti preg\u0103tit s\u0103 verifici explicit dac\u0103 importul s-a f\u0103cut.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 onboarding, verific\u0103 dac\u0103 OpenClaw a importat creden\u021bialele Qwen:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ls -lah ~\/.openclaw\nls -lah ~\/.openclaw\/agents\/main\/agent\njq . ~\/.openclaw\/agents\/main\/agent\/auth-profiles.json | head -50<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Fi\u0219ierele-cheie pe care trebuie s\u0103 le \u00een\u021belegi sunt:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>~\/.openclaw\/openclaw.json<\/code> pentru configura\u021bia principal\u0103<\/li>\n<li><code>~\/.openclaw\/agents\/main\/agent\/auth-profiles.json<\/code> pentru profilurile de autentificare<\/li>\n<li><code>~\/.qwen\/oauth_creds.json<\/code> pentru autentificarea local\u0103 a lui Qwen Code<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 mecanismul de import a func\u021bionat, ar trebui s\u0103 vezi un profil de autentificare \u00een stocarea intern\u0103 a agentului OpenClaw. Dac\u0103 nu a func\u021bionat, nu \u00eencepe s\u0103 injectezi manual configura\u021bii vechi de tip Qwen Portal. Treci pe ruta suportat\u0103 \u0219i p\u0103streaz\u0103 deployment-ul curat \u0219i men\u021binabil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Acesta este \u0219i momentul \u00een care verifici explicit starea providerului \u0219i a modelelor, nu doar presupui c\u0103 totul este \u00een regul\u0103:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw models status\nopenclaw models list\nopenclaw status --deep<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 autentificarea exist\u0103, dar gateway-ul tot spune c\u0103 providerul nu este disponibil, nu ai un model func\u021bional. Ai doar o poveste incomplet\u0103 despre autentificare.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 5: configureaz\u0103 Telegram cum trebuie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Telegram este, de departe, cel mai rapid canal util pentru OpenClaw. Este \u0219i cea mai simpl\u0103 metod\u0103 de a face botul accesibil de pe telefon f\u0103r\u0103 s\u0103 deschizi de fiecare dat\u0103 dashboard-ul.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Mai \u00eent\u00e2i creezi tokenul botului prin BotFather. Apoi fie \u00eel introduci \u00een onboarding, fie \u00eel adaugi explicit ulterior.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw channels add --channel telegram --token \"$TELEGRAM_BOT_TOKEN\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei o configura\u021bie explicit\u0103 \u00een <code>~\/.openclaw\/openclaw.json<\/code>, un punct de pornire s\u0103n\u0103tos arat\u0103 a\u0219a:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  channels: {\n    telegram: {\n      enabled: true,\n      botToken: \"123456:inlocuieste-cu-tokenul-tau-real\",\n      dmPolicy: \"pairing\",\n      groups: {\n        \"*\": { requireMention: true }\n      }\n    }\n  }\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Configura\u021bia asta p\u0103streaz\u0103 mesajele private \u00een pairing mode \u0219i face comportamentul \u00een grupuri mai strict \u00een mod implicit. Asta este postura corect\u0103 pentru un bot public de chat care ruleaz\u0103 pe un VPS controlat de tine. Nu \u00eel expune ca pe o juc\u0103rie deschis\u0103 tuturor \u0219i nu te mira apoi c\u0103 \u00eencep oameni aleatori s\u0103-l abordeze.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 vrei s\u0103 \u00eel testezi din telefon, \u00eencepe cu mesaj direct c\u0103tre bot, nu cu grupuri. Adaugi grupuri abia dup\u0103 ce fluxul din DM este curat \u0219i previzibil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 6: verific\u0103 gateway-ul, interfa\u021ba de control \u0219i daemonul<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pe Linux, gateway-ul OpenClaw ascult\u0103 implicit pe loopback \u0219i folose\u0219te portul 18789. Asta este bine. Las\u0103-l a\u0219a, dac\u0103 nu ai un motiv real s\u0103 faci altceva.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw gateway status\nopenclaw status\nsystemctl --user status openclaw-gateway.service\njournalctl --user -u openclaw-gateway.service -f<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru un test rapid al dashboard-ului de pe sta\u021bia ta de lucru, folose\u0219te SSH port forwarding, nu expune portul direct \u00een internet:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ssh -L 18789:localhost:18789 openclaw@IP_UL_TAU_VPS<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apoi deschizi local:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>http:\/\/localhost:18789<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 preferi comanda dedicat\u0103 din CLI, po\u021bi folosi \u0219i:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openclaw dashboard<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ceea ce verifici aici nu este doar dac\u0103 se deschide UI-ul. Verifici dac\u0103 gateway-ul a supravie\u021buit instal\u0103rii daemonului, dac\u0103 serviciul de utilizator este viu \u0219i dac\u0103 configura\u021bia este suficient de s\u0103n\u0103toas\u0103 \u00eenc\u00e2t planul de control s\u0103 r\u0103spund\u0103 corect.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pasul 7: cele trei c\u0103i pe care trebuie s\u0103 le cuno\u0219ti din prima zi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 nu \u0219tii unde \u00ee\u0219i p\u0103streaz\u0103 OpenClaw starea \u0219i configura\u021bia, vei pierde timp inutil mai t\u00e2rziu. Acestea sunt primele c\u0103i care conteaz\u0103:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>~\/.openclaw\/openclaw.json<\/code> pentru configura\u021bie<\/li>\n<li><code>~\/.openclaw\/agents\/main\/agent\/auth-profiles.json<\/code> pentru autentificarea providerilor<\/li>\n<li><code>~\/.qwen\/oauth_creds.json<\/code> pentru autentificarea local\u0103 Qwen Code<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Asta nu este teorie. C\u00e2nd botul \u00eenceteaz\u0103 s\u0103 r\u0103spund\u0103, una dintre primele \u00eentreb\u0103ri la care trebuie s\u0103 r\u0103spunzi este dac\u0103 problema vine din:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>serviciul gateway<\/li>\n<li>tokenul canalului<\/li>\n<li>profilul de autentificare al providerului<\/li>\n<li>providerul \u00een sine<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">F\u0103r\u0103 aceste c\u0103i, depanezi aproape orb.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Modurile obi\u0219nuite \u00een care instal\u0103rile pe VPS se stric\u0103<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Ai folosit Bun.<\/strong> Opre\u0219te-te. Pentru un gateway stabil, mai ales cu Telegram, folose\u0219te Node.<\/li>\n<li><strong>Ai instalat totul ca root.<\/strong> Acum serviciul de utilizator, config-ul \u0219i mentenan\u021ba ulterioar\u0103 sunt mai ur\u00e2te dec\u00e2t trebuia.<\/li>\n<li><strong>Ai s\u0103rit peste <code>loginctl enable-linger<\/code>.<\/strong> Serviciul merge p\u00e2n\u0103 la logout, apoi moare \u00een t\u0103cere.<\/li>\n<li><strong>Te a\u0219teptai ca vechiul OAuth din Qwen Portal s\u0103 mai func\u021bioneze.<\/strong> Nu mai func\u021bioneaz\u0103. Acel drum a fost eliminat.<\/li>\n<li><strong>Ai autentificat Qwen Code pe alt\u0103 ma\u0219in\u0103.<\/strong> OpenClaw nu poate sincroniza un fi\u0219ier local de creden\u021biale care nu exist\u0103 pe acest VPS.<\/li>\n<li><strong>Folose\u0219ti nvm sau alt version manager pentru serviciu.<\/strong> Unit\u0103\u021bile systemd de utilizator \u0219i instal\u0103rile de Node gestionate din shell sunt o metod\u0103 excelent\u0103 de a crea probleme la restart \u0219i dup\u0103 upgrade.<\/li>\n<li><strong>Tokenul Telegram este bun, dar rutarea nu este corect\u0103.<\/strong> Verific\u0103 DM policy, requireMention \u0219i dac\u0103 ai legat canalul curat.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Un adev\u0103r opera\u021bional simplu este urm\u0103torul: cele mai frecvente probleme cu OpenClaw pe Linux nu sunt \u201emodelul AI este slab\u201d. Sunt probleme de layout opera\u021bional. Runtime gre\u0219it. Utilizator gre\u0219it. Loca\u021bie gre\u0219it\u0103 pentru creden\u021biale. Presupuneri gre\u0219ite despre persisten\u021b\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardening-ul minim care merit\u0103 f\u0103cut imediat<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">OpenClaw nu este o platform\u0103 gigantic\u0103, dar tot merit\u0103 tratat cu disciplin\u0103 normal\u0103 de VPS.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Nu expune public portul 18789 dac\u0103 nu ai un motiv clar pentru asta.<\/li>\n<li>Folose\u0219te SSH forwarding sau un reverse proxy controlat.<\/li>\n<li>\u021aine gateway-ul sub un utilizator Linux dedicat.<\/li>\n<li>F\u0103 backup la <code>~\/.openclaw\/<\/code> dac\u0103 configura\u021bia botului conteaz\u0103 pentru tine.<\/li>\n<li>Nu l\u0103sa alte secrete f\u0103r\u0103 leg\u0103tur\u0103 citibile sub acela\u0219i utilizator dac\u0103 nu vrei ca uneltele s\u0103 le g\u0103seasc\u0103.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Mai este \u0219i partea mai pu\u021bin comod\u0103: anumite build-uri actuale OpenClaw au fost observate sincroniz\u00e2nd creden\u021biale CLI externe \u00een timpul setup-ului. Asta este convenabil pentru bootstrap-ul prin Qwen Code, dar \u00eenseamn\u0103 \u0219i c\u0103 trebuie s\u0103 fii atent ce alte fi\u0219iere de autentificare exist\u0103 \u00een home-ul utilizatorului respectiv.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">C\u00e2nd este suficient un VPS ServerSpan \u0219i c\u00e2nd ajutorul administrat este alegerea mai bun\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru o instalare OpenClaw folosit\u0103 de un singur utilizator sau de un grup restr\u00e2ns, un VPS ServerSpan modest este suficient. Nu vorbim despre un workload GPU uria\u0219. Vorbim despre un runtime Linux, un gateway, un canal de chat \u0219i un provider de modele din amonte. Problema rar este puterea brut\u0103. Problema real\u0103 este dac\u0103 operatorul \u0219tie s\u0103 \u021bin\u0103 partea de Linux \u00een ordine.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 e\u0219ti confortabil cu SSH, systemd user services, fi\u0219iere de config \u0219i depanare de autentificare, OpenClaw pe un VPS este un workload rezonabil pentru self-hosting. Dac\u0103 nu e\u0219ti, aplica\u021bia \u00een sine nu este partea care te va \u00eencurca cel mai tare. Te vor \u00eencurca runtime-ul, autentificarea \u0219i persisten\u021ba serviciilor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">De aceea combina\u021bia <a href=\"https:\/\/www.serverspan.ro\/virtual-servers\">Servere Virtuale ServerSpan<\/a> plus <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">Administrare Linux<\/a> este, \u00een mod realist, pairing-ul corect pentru acest tip de utilizare. VPS-ul \u00ee\u021bi ofer\u0103 gazda curat\u0103 \u0219i mereu disponibil\u0103. Ajutorul administrat elimin\u0103 partea \u00een care un experiment de weekend se transform\u0103 \u00eentr-un bot pe jum\u0103tate func\u021bional, cu serviciu mort \u0219i tokenuri expirate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Concluzia practic\u0103<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Instalarea corect\u0103 OpenClaw \u00een 2026 pe un VPS Linux ServerSpan nu este cea \u00een care botul r\u0103spunde o singur\u0103 dat\u0103 \u00een Telegram. Este cea \u00een care ruleaz\u0103 sub utilizatorul potrivit, folose\u0219te Node de pe o cale de sistem stabil\u0103, r\u0103m\u00e2ne pornit ca serviciu de utilizator \u0219i dup\u0103 logout, \u00ee\u0219i p\u0103streaz\u0103 configura\u021bia \u0219i autentificarea exact unde te a\u0219tep\u021bi \u0219i trateaz\u0103 corect realitatea Qwen. Vechiul OAuth nativ OpenClaw pentru Qwen Portal a disp\u0103rut. Qwen Code OAuth exist\u0103 \u00een continuare. Dac\u0103 mecanismul de import func\u021bioneaz\u0103 pe versiunea ta, \u00eel folose\u0219ti \u0219i \u00eel verifici. Dac\u0103 nu func\u021bioneaz\u0103, nu \u00eel for\u021bezi. Treci pe providerul suportat \u0219i p\u0103strezi setup-ul curat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Asta este toat\u0103 ideea unui runbook serios pentru VPS. Mai pu\u021bine mituri. Mai pu\u021bine capturi copiate la \u00eent\u00e2mplare. Mai multe comenzi, c\u0103i \u0219i decizii care \u00eenc\u0103 au sens dup\u0103 prima zi.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Dac\u0103 vrei s\u0103 \u00ee\u021bi g\u0103zduie\u0219ti singur Clawdbot, ast\u0103zi redenumit OpenClaw, pe un VPS Linux, r\u0103spunsul corect \u00een 2026 este s\u0103 \u00eel instalezi pe un server Debian sau RHEL curat, s\u0103 \u00eel rulezi sub un utilizator Linux dedicat, s\u0103 \u021bii Node pe o cale de sistem predictibil\u0103, s\u0103 folose\u0219ti fluxul oficial de onboarding \u0219i s\u0103 tratezi [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2714,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,12],"tags":[14971,14973,14978,14972,14967,14976,14961,14964,14979,14955,14965,14963,14958,14956,14939,14948,14957,14959,14950,14930,14962,14923,14951,14936,14929,14942,14960,14966,14974,14928,14970,14968,14977,14969,14975],"class_list":["post-2716","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","category-virtual-servers","tag-administrare-linux-openclaw","tag-agent-ai-self-hosted-vps","tag-asistent-ai-privat-openclaw","tag-backup-automat-openclaw","tag-cheie-api-qwen-openclaw","tag-configurare-bot-telegram-openclaw","tag-configurare-openclaw-rhel","tag-daemon-systemd-openclaw","tag-executie-tool-uri-openclaw","tag-gazduire-openclaw-pe-vps","tag-ghid-openclaw-vps","tag-implementare-openclaw-productie","tag-instalare-openclaw-debian","tag-instalare-openclaw-pe-vps-2026","tag-openclaw-1-8-docker","tag-openclaw-24-7-vps","tag-openclaw-agent-ai-telegram","tag-openclaw-ai-self-hosted","tag-openclaw-ct-go","tag-openclaw-nginx-reverse-proxy","tag-openclaw-qwen-1000-cereri-gratuite","tag-openclaw-qwen-oauth","tag-openclaw-r-selfhosted","tag-openclaw-serverspan","tag-openclaw-vs-chatgpt-self-host","tag-openclaw-vs-moltbot","tag-runbook-openclaw-vps","tag-sarcini-batch-openclaw","tag-securizare-openclaw","tag-self-host-openclaw-2026","tag-servere-virtuale-openclaw","tag-tuning-resurse-openclaw","tag-vps-ieftin-openclaw","tag-vps-pentru-openclaw","tag-wizard-onboarding-openclaw"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2716","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=2716"}],"version-history":[{"count":3,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2716\/revisions"}],"predecessor-version":[{"id":2722,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2716\/revisions\/2722"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2714"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2716"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2716"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2716"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}