Getting support

Where to ask, where to report a bug, how to report a security issue privately, and what to attach so the answer comes faster.

Last updated Aug 17, 2026View as Markdown

Overview

There is no support desk behind Nasnet Panel. It is a community project, and the people who can answer are the ones who read the issue tracker and the Telegram group. Which of those you pick matters less than what you bring with you. A diagnostics report attached to the first message usually saves a day of back-and-forth.

Before you ask

Work through these first. They resolve most of what gets reported.

  1. Check Troubleshooting for the error you are seeing, since the common failures are listed with their causes.
  2. Run a report from Diagnostics. It checks system info, interfaces, WiFi, routing, DNS, VPN, connectivity and recent log errors in one pass, and saves a file you can attach.
  3. Confirm your setup against System requirements, particularly free RAM and device-mode for router-hosted installs.
  4. Check whether it is already fixed by reading the Changelog and, if you are on an old tag, try the current release.

Where to go

Channel Use it for Where
Telegram Questions, setup help, “is this normal?” t.me/joinnasnet
GitHub issues Reproducible bugs and feature requests nasnet-panel/issues
Security advisories Anything with a security impact, and never a public issue Report privately

Reporting a bug

Open an issue and include:

  • What you did, what happened, what you expected. In that order, in plain sentences.
  • The version, given as the release tag, commit SHA, or container digest.
  • The RouterOS version of the router involved, and the board model.
  • How the panel is deployed, whether that is Docker on a server, a RouterOS container, or a build from source.
  • The diagnostics report, and the container logs if it fails to start.

Screenshots help for interface problems and are no substitute for logs when something fails to connect.

Reporting a security problem

Do not open a public issue. Use GitHub’s private vulnerability reporting on the repository. The advisory form is the intended route. Include reproduction steps, the version you tested, and the RouterOS version of any device involved.

What to expect: acknowledgement within about seven days on a best-effort basis, a fix in the next patch release once the severity is confirmed, and a disclosure date agreed with you before anything is published. Only the latest 0.x release gets security fixes; older tags are not backported.

Helping back

The same channels take contributions. Bug reports with a clean reproduction are genuinely valuable, and so is a pull request. The repository’s contributing guide covers setup, branch conventions, and what reviewers look for.