Skip to content
AquadactylAquadactyl

Common Issues

Find the right Aquadactyl or Manta troubleshooting steps before contacting support.

Start with the symptom you can see, check the matching component, and make one change at a time. Most checks in these guides inspect the current state; repairs are explained separately.

If you use someone else's panel, start with the browser checks and collect the error for your panel administrator. Host commands are for the operator of that installation.

Find your issue

What you seeStart here
Panel shows a 500 error, 502, or a blank pagePanel errors and logs
Login loops, 419 errors, or settings redirect to HTTPHTTPS, proxies and cookies
Installer fails, PHP is too old, or database login is deniedInstallation and database checks
Update rejects names such as |mcmods in the Blueprint auditSelect the fixed Installer
Blueprint reapplication rejects external paths and leaves maintenance enabledRecover the interrupted update
Schedules, emails or queued jobs do not runQueues and scheduler
An extension fails, or the interface looks outdatedBlueprint and frontend assets
The Egg Library says every egg is no longer availableEgg Library API update
Passkeys, OAuth or two-factor authentication failAccount access
Manta stops with the page-number HTTP 422 errorKnown pagination startup error
Clone fails, manta is missing, or its service cannot be foundCheckout and service recovery
Servers show unavailable, or console and quick actions failPanel, browser and node connectivity
Manta cannot connect to Docker, or a port is already in useDocker and listeners
Files appear missing, SFTP fails, or uploads are rejectedFiles and SFTP, upload limits
A game exits with code 137, or a Mac cannot access server filesServer exits, macOS mounts

For an addon page with a missing API route, see addon backend installation. For Manta displaying Wings release notes, see daemon update products.

First checks

  1. Record the exact error, action and time, including your timezone. Reproduce once so you can find the matching log entry.
  2. Check the scope: one account, one server, one node, or the whole panel. A working panel page does not establish that the browser can reach a node.
  3. Check the installed versions against current releases. Panel, Manta and Installer versions are separate. An installer version argument does not update an older checkout of the installer itself.
  4. Note what changed immediately before the problem: update, extension, domain, proxy, credentials, storage path or service configuration.
  5. Follow the matching guide and retry after a specific correction. Keep a backup before changing configuration or running an update.

Preserve the panel's application key, database, node configuration and server volumes. Deleting them, regenerating an existing application key, making files world-writable, or bypassing certificate checks can cause data loss or expose the installation. They are not general troubleshooting steps.

Collect useful evidence

Use a short excerpt around the failure, rather than an entire log directory. Panel log previews and Manta diagnostics are described in the component guides. Keep APP_DEBUG=false on a public panel, even when temporarily collecting debug logs.

Review evidence before sharing it. Remove passwords, application keys, node/API tokens, OAuth client secrets, Discord webhook URLs, session cookies and bearer credentials. Browser network exports and WebSocket URLs can contain tokens too. Automatic redaction still needs a human review. Never attach a complete .env or node config.yml to a public report.

If the relevant checks do not resolve it, use this template for your administrator or a report in the Panel or Manta repository:

Component and installed version:
Deployment: native Linux / Docker / Dokploy / macOS
Host OS and architecture, if relevant:
Scope: one user / one server / one node / all users
Action and exact error or HTTP status:
Time and timezone:
Steps to reproduce:
Expected result and actual result:
Recent changes:
Checks performed and their results:
Relevant, reviewed and redacted log excerpt:

Suspected compromise, exposed credentials, or potential data corruption should be escalated privately. Preserve logs and backups before further changes.