AppLaunch Docs
Return to AppLaunch

Troubleshoot a WordPress site

Diagnose provisioning, DNS, critical errors, sign-in, database, redirect, update, and storage problems.

2 min read • Updated 29 July 2026

Site is still provisioning

Wait for the active operation to finish. Do not submit another site creation request. If the service node is offline, node-dependent controls remain unavailable until it returns.

Domain does not load

Confirm ownership under the service Domains tab, then confirm the exact A record shown by the WordPress site flow. Remove conflicting A or AAAA records and set Cloudflare to DNS only during verification. See Troubleshoot domains and DNS.

WordPress reports a critical error

  1. Open Logs and find the first error at the failure time.
  2. If it names a recently changed plugin, stop the site if needed and rename that plugin's folder under textwp-content/plugins using Files.
  3. If it names the active theme, recover using a known-good theme only after creating a backup.
  4. Start or reload the site and test again.

Do not delete the entire textwp-content directory or reinstall WordPress over the live site as a first response.

Cannot sign in to WP Admin

Confirm you are using the WordPress administrator credential, not the AppLaunch or MySQL credential. Open the exact text/wp-admin URL from Database → WordPress Access. Clear only the site's cookies or use a private window to rule out a stale session.

Database connection error

Open Database and confirm the managed database and password operation completed. Avoid manually changing generated credentials in textwp-config.php. If you deliberately rotated the built-in password, wait for completion and retest both the public site and WP Admin.

Redirect loop or wrong hostname

Check that DNS points directly to AppLaunch and that WordPress texthome and textsiteurl match the intended HTTPS hostname. Disable conflicting redirects or upstream proxy rules. A domain change does not automatically rewrite every stored absolute URL.

Updates or uploads fail

Check storage usage, file access, and Logs. Confirm external file tools did not change ownership or structure. Create a backup before manually replacing a plugin or theme.

Get help

Create a support ticket with the service and site names, hostname, exact error, UTC time, recent change, and relevant log lines. Remove passwords, keys, cookies, and personal data.