Start with the installer's reported error or the checks shown in the console. Keep private claim links, API keys, passwords and recovery material out of support reports.
The installer or alpha channel is unavailable
Check whether the server can reach the release host and container registry. Open the current alpha release information and check that the matching release and required files appear in AppSweet releases. If a required file is unavailable or signature verification fails, keep the installation state and retry later. Report a persistent failure with the release tag and error message. Do not substitute files from another release or disable verification.
The console does not appear
On Dokploy, open the console hostname you entered in Environment. The Compose launcher does not print a private claim link: enter your saved installation key on the claim screen. Check Deployments and the launcher container logs, DNS, ports 80 and 443, and the proxy/network requirements in Install on Dokploy. The second deployment starts automatically. Keep the generated definition and volumes when retrying.
For the standalone server installer, the private claim link is printed only after deployment completion and verified HTTPS. Fix the reported problem and rerun the same installer command, keeping its installation directory and volumes. Missing SMTP settings do not prevent initial console access in either flow.
Dokploy refuses the selected service
Use a dedicated Compose service with its original App Name and the published
launcher pasted unchanged. No appsweet- prefix is required. AppSweet refuses foreign definitions and
resources. Do not clear an existing application's service to get past this check.
Check that APPSWEET_DOKPLOY_SERVICE_URL is the https:// address of this
Compose service's own page in Dokploy, and that APPSWEET_DOKPLOY_API_KEY is a
valid key of a Dokploy user who can manage this service. Leave Domains empty
and add no File Mounts.
Before authenticated admission, correct mistaken inputs in Dokploy and Deploy again in the same service. After admission, restore the original values if they were changed. Follow the retry instructions when a handoff was interrupted; never paste the launcher over the generated console.
Claim access expired or the installation is already claimed
If already claimed, sign in with the console administrator account. The installation key cannot claim it again. A lost installation key or expired unclaimed Compose installation requires operator recovery; keep its state.
Only for the standalone server installer, add --renew-claim to the original
installer command and run it as root, retaining the installation directory and
binding. This option does not reset an existing administrator.
Saved settings are not active
Saving creates a draft. Open the console's review page, run the checks and apply the revision. A failed check or apply leaves the previous applied configuration in place. Correct DNS, SMTP or storage settings in the console and retry there. Do not edit generated Compose files or environment variables to bypass the checks.
Updates
Configure backups in the console and obtain a recent verified backup for this installation's running release. Verification of an old capture does not make it fresh. With deferred or stale backups, update actions remain unavailable. The update executor also verifies release compatibility and backup authenticity.
Bundled file storage can use an independent external backup target; you do not need to replace file storage merely to enable backups. Automatic alpha delivery also requires explicit enrollment for this installation.
A server installed before AppSweet had built-in sign-in cannot be updated. Install AppSweet fresh and invite your people again; backups from before cannot be restored into the new installation.
Recovering after server loss
Retain access to the backup bucket, the private backup identity and the installation's backup verification material outside the lost server. A successful recovery also requires a complete verified backup and the supported storage configuration; a running container or a saved backup schedule alone is not proof of recoverability.
Clean-target restore currently requires external S3 with object versioning enabled on the uploads bucket. The included file store does not provide that versioning. Use the recovery instructions for the exact installed release, and rehearse recovery before depending on it.
The image will not pull
Check that Docker is running, its disk has free space, and the server can reach the registry named by the release. Images are public; a registry login is not required. Check proxy, firewall and DNS errors before retrying. On Dokploy, follow the retained-deployment retry steps above; for the standalone installer, rerun the same command. Keep installation state and volumes.