requires access to the panel server console to run. Use
sudo axottle.Doctor’s launch
Open the interactive menu:↑and↓or mouse wheel – scroll the list;Page UpandPage Down– go to the page;HomeandEnd: Beginning and End of ResultsEscis a return to the Doctor menu.
Find the problem checker and read the lines Found, Why and Next: it indicates what is discovered, why it is important and what can be done.
Safe recovery
Attempt safe recovery is suitable for typical failures when a database, dashboard, background services or web server has stopped. The Doctor will try to start or restart the desired service, update the already configured certificate if necessary, and then repeat all the checks. Before starting, consider the following:- Active connections to the restarted service may be interrupted for a short time.
- Doctor does not change database passwords or edit DNS records.
- If the action fails, it will remain on the list marked
failedand explained. - After recovery, the performed actions and the results of the re-check are shown on the screen.
Place on the disk
A full drive isn’t slow, it’s a stop: PostgreSQL can’t write checkpoint, panics, and goes into a restart cycle that writes even more to the journal, and by this point, the API is no longer available, so you have to sort it out locally. Screen. Place on the disk menusudo axottle It categorizes the space and divides it into two groups: what can be cleaned and what is protected. Database volumes are never touched.
Actions on Enter: clear everything, clear what is older than 7 days, older than 30 days, or show where it lies (catalogues and largest files). Before deletion, you show how much will be released and how many files are affected, and the deletion itself requires an explicit y. After cleaning, the disk is recalculated.
Logs of working containers are reset in place, not deleted: Docker keeps them open, and deleting the file would not return space before restarting the container.
The installer and the update check the vacant space before the start of work. It’s critical for the upgrade: it removes the base dump, and the dump that didn’t have enough space is a cropped dump, from which they will roll back. The local backup for the same reason does not start without stock: you need a maximum of 1 GB and double the size of the previous archive.
/etc/docker/daemon.json and in journald, so Remnawave logs and proxy no longer eat the disk in a week.
Support bundle
A support bundle is an archive with audit results and logs that can be attached to a support call.Choose a period.
In Log period, pressEnter until the appropriate period appears:
- 1 hour;
- 6 hours;
- 24 hours;
- 7 days;
- 30 days;
- All the available history.
Collect and verify the archive
- Select Collect support bundle.
- Wait until the collection is complete. Don’t close the terminal while you’re creating the archive.
- Select Send bundle to support.
- Before submitting, select Show archive contents to see brief information about the archive.
- For a full check, select Save locally, open the saved archive and browse
manifest.json. - Return to Send bundle to support and select Send to support.
How to choose an action
Recommended rules
Backups are serviced separately - see Backups of the panel. The order of updating is described on the page Update panel.
Verification
After the diagnosis, make sure that:- There are no unexplained
Failedin the summary. - Each
Warninghas an understandable following action. - after safe recovery, the problem services have been re-checked;
- The created support bundle is opened, and its manifesto corresponds to the selected period and the expected sources.
Rollback
Normal diagnostics don’t change anything. The locally saved support bundle can be deleted like a regular file. Safe Recovery can restart services or update an existing certificate. If the situation worsens after it, do not repeat the action blindly: save the bundle, check the activity log and restore the service according to its standard instructions. For emergency order, use the Incident Response page.Doctors can't check the database
Doctors can't check the database
Make sure the command is running on the panel server. Select Attempt safe recovery. If the base does not rise, check the status of the PostgreSQL container or the
postgresql service, then collect bundle - it will get the available database and installer logs.Sending the archive failed.
Sending the archive failed.
Select Save bundle locally and attach the saved file manually, and check also the DNS, outbound connection and support server address.
The results are many Skipped or Unknown.
The results are many Skipped or Unknown.
Skipped usually means that the component is not used in this installation.Unknown means that the Doctor was unable to retrieve the data - often due to insufficient rights or an inaccessible service.Run sudo axottle and repeat the check.