Run as root on the source server:

Or the simpler form:

Single account:

All accounts:

Prepare a fresh remote GoAdmio server (no websites yet), then run as root:

Example:

Web method: log in to GoAdmio on port 2020 → Backups → Restore a Full Backup. Upload the archive to:

CLI method (as root):

Switch to NGINX:

Switch to Apache:

If the issue persists:

Open one of:

Choose a client (Roundcube, SnappyMail, SquirrelMail), then log in with your full email address (lowercase) and password.

Or: GoAdmio → Home → Email → Undelivered Emails → Export as CSV → clean the list.

One domain:

All domains:

Delete the list entirely:

GoAdmio creates the Cloudflare zone and then writes every DNS record the domain needs to run a website and a full mail service — no manual record entry, no copy-pasting DKIM keys or building SPF strings by hand. One command and the domain is live for both web and mail.

Single domain:

All domains on the server:

Records created automatically:

• Web — A / AAAA records for the domain and www
• MX — mail routing to your server, so the domain can receive email
• SPF — sender policy that authorizes your server to send mail for the domain
• DKIM — signing key published in DNS so receivers can verify outgoing mail
• DMARC — policy record telling receivers how to treat mail that fails SPF/DKIM
• Autodiscover / autoconfig — so mail clients configure themselves from just the address and password

/go/index scans every MySQL / MariaDB database on the server, finds the columns that are used in queries but have no index, and adds the index for you — across all tables and all databases at once. No ALTER TABLE ... ADD INDEX by hand, table by table.

Missing indexes are one of the most common causes of a slow site: a query that scans a million rows instead of reading one becomes a page that takes seconds to load. Adding the index usually fixes it without changing any application code.

Run as root:

Run it twice, 5 minutes apart — the first pass adds the indexes, the second picks up anything the first pass skipped:

A Let's Encrypt validation triggers a burst of DNS lookups, and if the server's resolver is slow, rate-limited or misconfigured, everything that waits on DNS — page loads included — starts to lag. Resetting the resolver back to its defaults usually clears it.

Reset to the default resolver:

Or force a specific public resolver:

Removes custom records and recreates the standard set:

Example:

Connect via SSH, then: