Skip to main content

The connection is not working.

  1. Open Services → Remnawave.
  2. Select the connection.
  3. Open the tab Diagnostics.
  4. Check the URL, status, and message of the latest test.
Authorization errors usually mean that the token is withdrawn or does not have the necessary rights.Remove the connection and create it again with the new token.

The synchronization ended in an error.

Open the tab Journal Connection and find the last operation. After fixing the cause, press Synchronize again.

Runtime has not been detected.

Select the connection and open the status tab. In the card Remnawave, check the text of the latest error.
  • For a variant of Server Axottle check that Remnawave is really running on the host panel, Docker is available panels and Compose project has a PostgreSQL container.
  • For Separate server Make sure the agent is online, and if the one-time installation command expires, create a new command and run it again.
  • For Together with RemnaNode, make sure that a node with an agent already installed on the same host is selected.
After fixing the cause, press Find the stack again. Until PostgreSQL is found, logs and backups are not available.

No metrics or logs.

Metrics appear after the artist’s first heartbeat. If the agent is offline, reconnect with the panel and wait for the next heartbeat. In the log list, only the containers of the found Compose project are visible. Repeat detection if the container was renamed, recreated or added after the previous search.

Backup won’t start.

Go to the Backups tab. Check the runtime status found by PostgreSQL, profile, storage location, and last run message. For S3, also check the bucket, access key, and secret key with permission to write.

Escalation

Attach a screenshot of the tab Diagnostic, error time and events from the tab Journal.