... Containers
OpenClaw Online
7 Sites Live
@Nexuskraken_bot
... Disk
--:--:--
nexusonline40@gmail.com
๐Ÿ“Š Dashboard
๐Ÿฆ€ OpenClaw
๐Ÿณ Containers
๐Ÿค– AI Terminal
๐Ÿ“ File Manager
๐ŸŸข Diagnostics
Containers
Loading...
SSL Certs
35
Let's Encrypt
Websites Live
7
HTTP 200
Telegram Bots
Active
RAM Used
of 47GB
Disk Used
of 484GB
LLM Models
13
nexus-code, oracle, prime +10
OpenClaw
ON
@Nexuskraken_bot
๐Ÿ–ฅ๏ธ N8N VPS โ€” 89.117.22.242 (Primary)
โš™๏ธ Core Services
Manage in Portainer โ†’
ServicePortStatusURLAction
Caddy (SSL/Proxy)80/443UPโ€”
n8n Automation5678UPOpen
Open WebUI8080UPOpen
Portainer9000UPOpen
Uptime Kuma3001UPOpen
Vaultwarden8181UPOpen
Dozzle Logs8888UPOpen
Plausible Analytics8000UPOpen
Nexus API Proxy8100UPโ€”
Dashboard Backend8888UPโ€”
Sodapaper Botโ€”UPTelegram
๐Ÿฆ€ OpenClaw VPS โ€” 66.94.124.143 (US West)
IP
66.94.124.143
Gateway
Running
Telegram
@Nexuskraken_bot
dmScope
per-peer
๐Ÿ“Š Netdata
๐ŸŒ Domain Network โ€” All HTTPS
DomainPurposeSSLStatus
nexusgrouplabs.comCorporate HQValid200
nexusgrouplabs.storeE-CommerceValid200
creativeora.comCreative ServicesValid200
nexusorbit.cloudCloud PlatformValid200
nexusechat.onlineChat PlatformValid200
nexplex.spaceTech BrandValid200
glowingorb.orgClimate TechValid200
cmd.nexusgrouplabs.comCommand CenterValid200
๐Ÿ“ˆ Resource Usage โ€” Live
Updating...
RAM...
Disk...
๐Ÿฆ€
OpenClaw Gateway โ€” @Nexuskraken_bot
AI agent gateway via Telegram ยท VPS: 66.94.124.143 ยท Service: openclaw-gateway.service
โ— ONLINE
Bot Handle
@Nexuskraken_bot
Gateway Port
18789 (loopback)
Version
2026.4.24
dmScope
per-peer
Channel
Telegram โœ“
Auth Mode
token
Tools Profile
coding
VPS IP
66.94.124.143
โœ… Whitelisted Telegram IDs (allowFrom)
4 IDs Active
8603899998Primary userWhitelisted
8106417066User 2Whitelisted
8711677850User 3Whitelisted
8107270093User 4Whitelisted
Config file: /root/.openclaw/credentials/telegram-default-allowFrom.json
dmScope: per-peer โ€” Each whitelisted user gets their own session context
To add a new ID: Edit the allowFrom file and restart the gateway
โš™๏ธ OpenClaw Configuration
SettingValueNotes
Gateway ModelocalRuns on VPS, loopback only
Gateway Port18789Loopback only (secure)
Telegram Bot Token8739502751:AAHuโ€ฆCJMM@Nexuskraken_bot
dmScopeper-peerEach user gets own session
Tools ProfilecodingCode-focused tool set
Workspace/root/.openclaw/workspaceAgent workspace root
TailscaleoffNot using Tailscale
Serviceenabled + runningAuto-starts on reboot
๐Ÿ”— How to Pair a New Telegram Account
๐Ÿ“ฑ Pairing Steps
1
Open Telegram and message @Nexuskraken_bot
2
The bot will send you a pairing code (e.g. XXXXXXXX)
3
SSH into OpenClaw VPS and run: openclaw pairing approve telegram YOURCODE
4
Or list pending requests: openclaw pairing list telegram
5
To add a Telegram ID to whitelist: nano /root/.openclaw/credentials/telegram-default-allowFrom.json
6
Restart gateway after changes: systemctl --user restart openclaw-gateway.service
๐Ÿ“‚ OpenClaw Workspace Files
FilePathPurpose
SOUL.md/root/.openclaw/workspace/SOUL.mdAgent core identity
USER.md/root/.openclaw/workspace/USER.mdUser profile (fill in)
IDENTITY.md/root/.openclaw/workspace/IDENTITY.mdAgent identity (fill in)
TOOLS.md/root/.openclaw/workspace/TOOLS.mdAvailable tools
AGENTS.md/root/.openclaw/workspace/AGENTS.mdAgent directory
openclaw.json/root/.openclaw/openclaw.jsonMain config
allowFrom.json/root/.openclaw/credentials/telegram-default-allowFrom.jsonTelegram whitelist

๐Ÿณ Docker Containers โ€” Live Status

Loading containers...
Model: Mode: โ— Ready
โ•”โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•—
โ•‘ NEXUS AI TERMINAL v3 โ€” Ollama + OpenAI + Gemini โ•‘
โ•šโ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•
VPS: 89.117.22.242 | API Proxy: port 8100 | Ollama: port 11434
Models: llama3.2:1B ยท llama3.2:3B ยท nexus-code ยท nexus-oracle ยท nexus-prime ยท nexus-insight ยท mistral:7B ยท qwen2.5:7B ยท GPT-4.1-mini ยท Gemini 2.5 Flash
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€
Type a prompt and press Enter or click Send.
 
๐Ÿ“ค Upload & View Files
DOCX, PDF, MD, TXT, JSON, PY, JS, ZIP supported
๐Ÿ“

Click to upload or drag and drop files here

DOCX โ€ข PDF โ€ข MD โ€ข TXT โ€ข JSON โ€ข PY โ€ข JS โ€ข ZIP โ€ข PNG โ€ข JPG

๐Ÿ“„ Document Viewer / Editor
Drop a file above to view its contents here...
๐Ÿ—‚๏ธ VPS Quick Paths

๐Ÿ”ด Issues, Fixes & Guides

โœ…
Plausible Analytics โ€” FIXED
Container: plausible-plausible-1 | Status: running
FIXED
Root cause: plausible_db (PostgreSQL) container had been removed from the Docker network. Fixed by running docker compose down && docker compose up -d from /opt/nexuslabs/plausible. All 3 containers (plausible, plausible_db, plausible_events_db) are now healthy.
๐Ÿ”ง Fix Steps:
1
Edit env: nano /opt/nexuslabs/plausible/.env
2
Ensure: BASE_URL=https://analytics.nexusgrouplabs.com
3
Restart: docker compose restart plausible
โœ…
Mysterium Node โ€” FIXED
Container: mysterium | Status: running
FIXED
Root cause: Container was running without required arguments (service --agreed-terms-and-conditions). Fixed by recreating the container with correct args, NET_ADMIN cap, and host networking. Container is now up and stable.
๐Ÿ”ง Fix Steps:
1
Check logs: docker logs mysterium --tail 30
2
Force restart: docker restart mysterium
3
If persistent: rebuild mysterium
๐Ÿณ
Docker Caddy โ€” RESOLVED
Root cause: Docker bridge network had no DNS access
FIXED
Caddy now runs on the host OS (not in Docker), eliminating all DNS/network issues. 35 SSL certs issued via Let's Encrypt.
โœ… Current Setup:
1
Caddy v2.11.2 on Ubuntu 24.04 host
2
35 SSL certs โ€” all domains HTTPS
3
Check: systemctl status caddy
๐Ÿค–
Bot Offline โ€” Recovery Guide
Generic guide for any Telegram bot going offline
GUIDE
If any Telegram bot stops responding, follow these steps. Most failures are: container crash, API token conflict, or Python import errors.
๐Ÿ”ง Recovery Steps:
1
Check logs: docker logs [BOT_NAME] --tail 20
2
Restart: docker restart [BOT_NAME]
3
Syntax check: syntax check
4
Nuclear: rebuild
๐Ÿฆ€
OpenClaw โ€” Telegram Pairing Guide
@Nexuskraken_bot on 66.94.124.143
CONFIGURED
OpenClaw gateway is running. 4 Telegram IDs are whitelisted. dmScope is set to per-peer. If a user can't connect, check allowFrom file and restart gateway.
๐Ÿ”ง OpenClaw Fix Steps:
1
Check status: openclaw status
2
Check allowFrom: cat allowFrom.json
3
List pending pairings: openclaw pairing list telegram
4
Approve pairing: openclaw pairing approve telegram CODE
5
Restart gateway: restart gateway
๐Ÿ”
SSL Certificate Not Issuing
Caddy ACME challenge failure
GUIDE
If SSL cert is not issuing, the domain's A record must point to 89.117.22.242 before Caddy can complete the HTTP-01 ACME challenge.
๐Ÿ”ง SSL Fix Steps:
1
Verify DNS: dig +short [DOMAIN] A โ†’ must return 89.117.22.242
2
Check Caddy logs: journalctl -u caddy -n 50
3
Force renewal: systemctl reload caddy