What is remnawave-troubleshooting?

A troubleshooting guide for Remnawave installation and runtime problems. It covers container logs, environment changes, reverse proxies, Nodes, API documentation, firewalls, and subscription delivery.

Use it to inspect Docker status and logs, recreate containers after changing .env, check Node firewall access, verify API or subscription settings, and investigate missing admin access.

It narrows failures to the relevant layer and highlights issues such as unrecreated containers, blocked Node ports, or disabled documentation.

remnawave-troubleshooting — Skill for Codex by JonesPitkin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add JonesPitkin/remnawave-skills --skill remnawave-troubleshooting

Clone the repo

git clone --depth 1 https://github.com/JonesPitkin/remnawave-skills

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting/github.svg)](https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting)

Your own site

<a href="https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting"><img src="https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting"><img src="https://agentmods.dev/badge/skills/jonespitkin/remnawave-skills/remnawave-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 590 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00590
Opus 5	$0.00020	$0.00295
Sonnet 5	$0.00008	$0.00118
Haiku 4.5	$0.00004	$0.00059

Measured 12d ago against content hash a2b35600b3bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

remnawave-troubleshooting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

remnawave-troubleshooting/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Remnawave Troubleshooting

Назначение

Этот skill покрывает типовые install/runtime проблемы Remnawave: неправильная публикация Panel, env changes without recreate, node/firewall issues, logs, missing docs, subscription-page miswiring.

Теория

Официальные материалы заранее предупреждают о нескольких классах проблем:

сервисы нельзя публиковать напрямую в интернет;
reverse proxy обязателен;
sub-path не поддерживается;
env changes требуют recreate containers;
NODE_PORT нужно ограничивать firewall;
node logs без logrotate могут заполнить диск;
docs/API routes могут быть выключены через IS_DOCS_ENABLED.

Практика

Определить слой сбоя:
- install
- reverse proxy
- env
- API/docs
- node connectivity
- subscription delivery
Проверить базовые команды:
- docker compose ps
- docker compose logs -f -t
Если менялся .env, выполнить recreate:
- docker compose down && docker compose up -d
Для Node:
- проверить docker compose logs -f -t
- проверить firewall для NODE_PORT
Для subscription:
- проверить SUB_PUBLIC_DOMAIN
- проверить REMNAWAVE_API_TOKEN
Для forgotten admin access:
- использовать Rescue CLI:
  - docker exec -it remnawave remnawave

Типовые сценарии

Panel не открывается по домену.
После правки .env изменения не применились.
Node не появляется рабочим после добавления.
Subscription Page не может связаться с Panel.
Встроенная API docs не открывается.

Ошибки

Искать причину в UI, когда .env не был применен через recreate.
Оставлять NODE_PORT open to world.
Использовать sub-path routing в reverse proxy.
Включить logs на node без rotation.

Проверка результата

Выявлен правильный failure domain.
Устранение опирается на официальные docs warning/steps.
После исправления сервис либо открывается, либо явно локализован следующий слой сбоя.

Ссылки

Read the full file on GitHub · 75 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 75 lines · 40 tokens per session scan A a2b35600b3bd

Subscribe to this mod's changes

remnawave-troubleshooting is a skill published in the GitHub repository JonesPitkin/remnawave-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 590 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging DevOps and cloud

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens