Get support

Collect the right information with /ng bugreport and /ng diagnostics, remove private data, and contact support.

On this page

When something goes wrong, a good report gets you a fix much faster. This page shows what to check first, how to create a report with one command, and what to include when you contact support.

Check these first

  1. Read Known issues. Direct-IP joins, BungeeCord-only plugins and Linux-only features cause most questions.
  2. Run /ng diagnostics (or ng diagnostics in the console). It shows your build version, installed Velocity plugins and any default modules you switched off.
  3. If a real player was blocked, follow the steps under "If a real player is blocked" on Anti-bot and anti-exploit.

Create a bug report

Run this command in the console or in game, with a short description of the problem:

ng bugreport players get kicked when joining from Bedrock

NusaGate saves a file named logs/nusagate-bugreport-<time>.md in the proxy folder and prints its location. The report contains:

  • your NusaGate version, release channel and Velocity base version;
  • the list of installed Velocity plugins;
  • modules that are on by default but that you switched off;
  • protection statistics;
  • the last part of logs/latest.log, with known secret formats hidden.

What to include

InformationWhere to find it
NusaGate and Velocity versionThe version line in /ng stats or /ng diagnostics
Java version and operating systemjava -version and your host's panel
What sits in front of the proxyDirect connection, or a frontend such as HAProxy
Installed plugins with versions/ng diagnostics or the bug report
Type of problemReal players blocked, an attack getting through, a plugin conflict, or CPU, memory or ping problems
When it happenedDate and time, with your time zone
Was attack mode active?/ng stats or /ng attack
Player clientJava or Bedrock, the game version and the client brand if known
Disconnect messageThe exact text on the player's screen
LogsThe bug report file, or at least 30 to 50 relevant lines of logs/latest.log

Remove private data before sharing

The bug report hides known secret formats, but always read it yourself before you send it. Make sure none of these appear:

  • your PRO license key or the contents of nusa-license.properties;
  • Anti-VPN provider API keys;
  • your Discord webhook address;
  • dashboard tokens or other passwords.

Never post these in a public channel. If one leaks, replace it at the service that issued it.

Where to get help

Contact Formatra Studio through the NusaGate page on BuiltByBit. The page also links to the Formatra Studio Discord for questions. Include your version line, your plugin list and a reviewed /ng bugreport file.

Next steps

Nusa product documentation · NusaGateFree & PRO editions

Loading the index…