troubleshooting

Fix: OpenClaw Dashboard Open Nahi Ho Raha

OpenClaw dashboard load na hone par step-by-step diagnosis aur fix. Isme SSH tunnels, Gateway binding, aur firewall issues cover kiye gaye hain.

Read in English

Symptom

Aap apne browser mein dashboard open karne ki koshish karte hain, lekin aapko ERR_CONNECTION_REFUSED ya ek blank screen milti hai.

Severity

medium

Affected Area

dashboard

On this page

Proceed with caution Is issue ko fix karne ke liye apna firewall disable mat karein ya port ko expose mat karein. Neeche diye gaye safe diagnostic flow ko follow karein.

Recommended access: SSH Tunnel / Tailscale

Symptom

Aap apne browser mein http://localhost:18789 ya apne server ka IP type karte hain, aur aapko dikhta hai:

ERR_CONNECTION_REFUSED
This site can't be reached
Ek timeout ya infinitely spinning loading wheel

Quick diagnosis flow

Problem ko isolate karne ke liye in checks ko order mein follow karein.

Check 1: Kya Gateway sach mein chal raha hai?

Dashboard ko OpenClaw Gateway serve karta hai. Agar Gateway crashed ya stopped hai, toh dashboard load nahi hoga.

Apne VPS par yeh run karein:

bash

sudo ss -tulpn | grep 18789

Good output (Gateway chal raha hai):

tcp   LISTEN   0   511   127.0.0.1:18789   0.0.0.0:*   users:(("node",pid=1234,fd=18))

Empty output (Gateway NAHI chal raha hai): Agar command kuch bhi return nahi karti, toh Gateway nahi chal raha hai. Crash ko fix karne ke liye Gateway Not Running guide par jayein, aur fir wapas yahan aayein.

Check 2: Kya aap sahi IP use kar rahe hain?

Aap dashboard kahan se access karne ki koshish kar rahe hain?

Scenario A: Apne laptop se SSH tunnel use karke (Recommended) Agar aap http://localhost:18789 type kar rahe hain, toh aapke laptop par ek separate terminal mein SSH tunnel chalna zaroori hai.

Apne laptop par run karne wali command: ssh -L 18789:localhost:18789 clawuser@your_server_ip
Agar aapne SSH tunnel chalane wale terminal ko close kar diya, toh connection drop ho jata hai. Command ko dobara run karein aur window ko open rakhein.

Scenario B: Tailscale ke through access karna Agar aap http://100.x.y.z:18789 type kar rahe hain, toh verify karein ki:

Tailscale aapke laptop par chal raha hai.
Tailscale VPS par chal raha hai.
Gateway ko Tailscale IP par bind karne ke liye configure kiya gaya hai (apne .env mein OPENCLAW_HOST=100.x.y.z check karein).

Scenario C: Public VPS IP ke through access karna (Dangerous) Agar aap http://your_vps_public_ip:18789 type kar rahe hain, toh connection shayad aapke firewall (UFW ya provider firewall) dwara block kiya ja raha hai.

⚠ DANGER — Firewall ko bypass mat karein

Connection refused error ka aksar yeh matlab hota hai ki aapka firewall aapko protect kar raha hai. sudo ufw allow 18789 run karna ya UFW ko disable karna aapke internal dashboard, logs, aur connected AI models ko internet par kisi ke liye bhi expose kar dega. Iske bajaye SSH tunnel use karein — yeh correct fix hai.

Check 3: Kya Gateway properly bound hai?

Check 1 ke output ko dobara dekhein. Local Address column par dhyan dein.

Agar yeh 127.0.0.1:18789 kahta hai: Gateway sirf local connections ke liye listen kar raha hai. Aapko ek SSH tunnel use karna hoga.

Agar yeh 0.0.0.0:18789 ya *:18789 kahta hai: Gateway sabhi interfaces par listen kar raha hai. Yeh bahut insecure hai jab tak ki aap ek strict reverse proxy ke peeche na hon. Apna .env file open karein, OPENCLAW_HOST=127.0.0.1 set karein, aur Gateway ko restart karein.

Agar yeh ::1:18789 kahta hai: Gateway IPv4 localhost ke bajaye IPv6 localhost par bind ho gaya hai. Yeh kuch SSH tunnel configurations ko break kar sakta hai. Fix: Apne .env mein explicitly IPv4 host define karein:

bash

echo 'OPENCLAW_HOST=127.0.0.1' >> .env

Fir Gateway ko restart karein.

Check 4: Browser cache aur DNS

Kabhi-kabhi browser khud confuse ho jata hai, khaskar agar aapne recently tunnels restart kiye hon.

localhost ke bajaye http://127.0.0.1:18789 open karne ki koshish karein.
Ek incognito / private browsing window try karein.
Ensure karein ki aap http:// use kar rahe hain aur https:// nahi (jab tak ki aapne TLS ke saath reverse proxy explicitly configure na kiya ho).

Provider firewall panel warning

Agar aap completely sure hain ki aapne TLS aur authentication ke saath ek reverse proxy configure kiya hai, aur aap dashboard ko outside se securely access karne ki koshish kar rahe hain, lekin yeh abhi bhi time out ho raha hai: apne VPS provider ka web-based firewall check karein.

AWS Lightsail, DigitalOcean, aur Hetzner jaise providers ke paas cloud firewalls hote hain jo aapke server ke UFW ke baahar exist karte hain. Agar web panel mein port 443 (aapke proxy ke liye) allowed nahi hai, toh traffic kabhi UFW tak nahi pahuchega.

Kharab fixes jinse bachna chahiye

sudo ufw allow 18789 ko run mat karein — yeh aapke Gateway ko internet par expose kar deta hai.
OpenClaw config ko --host 0.0.0.0 mein change mat karein — same reason.
UFW ko disable mat karein — yeh aapke pure server ke liye sabhi firewall protections disable kar deta hai.

Prevention checklist

Main dashboard access karne ke liye SSH tunnel ya Tailscale use kar raha hu.
Mera Gateway 127.0.0.1 (ya Tailscale IP) par bound hai.
Mera SSH tunnel terminal tab tak open rahta hai jab tak main browse karta hu.
Gateway process chal raha hai (ss ya pm2 se verify kiya gaya).

Madad kab maangein

Agar Gateway chal raha hai, SSH tunnel active hai, aur dashboard abhi bhi load hone se mana kar raha hai, toh koi obscure networking issue ho sakta hai.

Community mein ya Setup Help ke through assistance request karein. Redaction Warning: Apne terminal ya ss output ke screenshots share karne se pahle, apne public IP address aur command history mein dikhne wale kisi bhi tokens ko blur kar dein. Apna root password ya unredacted .env files kisi ke saath share mat karein.

ClawReady.in is an independent educational resource and setup service. It is not affiliated with, endorsed by, or operated by OpenClaw.