GoAdmio
GoAdmio Documentation

WordPress

From the GoAdmio knowledge base.

WordPress

This page explains the WordPress one-click installer in GoAdmio. It lets you install a complete WordPress site on a domain in a single step — no manual file upload, no database setup, no configuration.

Location: Admin Panel → Scripts → WordPress
Location (User Panel): Scripts → WordPress (if enabled for the account)


Overview

WordPress is the world's most popular content management system — powering over 40% of all websites. GoAdmio's one-click installer handles the entire setup:

  • Downloads the latest WordPress release
  • Creates the database and database user
  • Configures wp-config.php with the correct credentials
  • Installs WordPress in the chosen directory
  • Runs the installation wizard (site title, admin user, admin password)
The result is a fully working WordPress site, ready for content.

> Note: The one-click installer is for new installations. For migrating an existing WordPress site, use Backup Wizard or Migrate from cPanel. For changing an existing WordPress admin password, use Change WordPress Password.


What the Page Shows

| Field | Description |
|---|---|
| Domain | The domain to install WordPress on (e.g., emamazoz.com) |
| Directory | The installation path (e.g., /home/emamazoz.com/www) |
| Version | The WordPress version to install (e.g., Latest Version (English)) |
| Database Name | The database to use — prefixed with the account username |
| Database Username | The database user — prefixed with the account username |
| Database Password | The password for the database user — you must enter a new password for a new database |
| Install | Run the installation |

> Important: The Database Password field does not auto-generate. You must enter a new password for the new database. Choose a strong password and store it securely — you will need it if you ever manage the database directly.


Prerequisites

Before installing WordPress:

  1. A domain is set up on the account — see Create New Account or Addon Domains.
  2. DNS points to the server — the domain resolves to the GoAdmio server. See DNS Manager and Track DNS.
  3. The document root exists — usually www/<domain> — see Change Document Root.
  4. The domain is not suspended — see Suspend Account.
  5. The account has disk space and database limits — see Show Accounts Over Quota and Add/Modify Packages.
  6. PHP and MySQL are running — see Service Status.
> Tip: If DNS does not point to the server yet, the installation will complete but the site will not load in a browser until DNS propagates. Install anyway — it will be ready when DNS resolves.

How to Install WordPress

Step 1 — Open the installer

  1. Log in to the GoAdmio Admin Panel (or User Panel).
  2. Navigate to Scripts → WordPress.

Step 2 — Select the domain

  1. Choose the Domain from the dropdown (e.g., emamazoz.com).
  2. The Directory field auto-fills with the account's document root (e.g., /home/emamazoz.com/www).
  3. Adjust the directory if you want WordPress in a subdirectory (e.g., /home/emamazoz.com/www/blog).

Step 3 — Choose the version

  1. Select the Version — usually Latest Version (English).
  2. If other versions or languages are available, choose the one you need.
> Tip: Always use the latest version — it includes security fixes and performance improvements. Older versions may be available for compatibility, but they are not recommended for new sites.

Step 4 — Configure the database

  1. The Database Name and Database Username are pre-filled with the account's username prefix (e.g., emamazoz_).
  2. Add a suffix if you want a specific name (e.g., emamazoz_wp), or leave the default.
  3. Enter a new password in the Database Password field.
- Use a strong password — the installer does not generate one. - Store the password in a password manager. - You will need it if you ever manage the database directly.

> Warning: The database password is not auto-generated. If you leave it blank or use a weak password, the database is at risk. Use a strong password and save it immediately.

Step 5 — Install

  1. Click Install.
  2. GoAdmio downloads WordPress, creates the database, configures wp-config.php, and installs the files.
  3. The installation may take a minute or two, depending on the server.
  4. When complete, GoAdmio shows the WordPress installation wizard or a link to it.

Step 6 — Complete the WordPress setup

  1. Open the installation wizard at https://<domain>/wp-admin/install.php (or the URL shown).
  2. Fill in:
- Site Title - Username for the WordPress admin - Password for the WordPress admin (use a strong one) - Email for the admin
  1. Click Install WordPress.
  2. Log in at https://<domain>/wp-admin/ with the credentials you set.
> Tip: The WordPress admin username is not the same as the hosting account username. Choose a distinct, non-obvious admin username (e.g., not admin) to reduce brute-force risk.

What the Installer Creates

| Item | Created? | Notes |
|---|---|---|
| WordPress files | ✅ Yes | In the chosen directory |
| Database | ✅ Yes | With the account's username prefix |
| Database user | ✅ Yes | With the account's username prefix |
| wp-config.php | ✅ Yes | With the database credentials |
| WordPress admin user | ⚠️ Via the wizard | You set it in step 6 |
| Site title | ⚠️ Via the wizard | You set it in step 6 |
| SSL certificate | ❌ No | Install separately — see Install Free SSL Certificate |
| Caching plugin | ❌ No | Install a plugin (e.g., WP Super Cache, W3 Total Cache) if desired |
| Security plugin | ❌ No | Recommended: Wordfence, iThemes Security |

> Note: The installer creates a working site, but a production WordPress site also benefits from:
> - SSL — see Install Free SSL Certificate
> - Caching — for performance — see Cache Website
> - Security plugins — for hardening
> - Backups — see Backup Wizard


After Installing

| Task | Why |
|---|---|
| Complete the WordPress wizard | Set site title, admin user, and admin email |
| Log in to the WordPress admin | Confirm the site works — /wp-admin/ |
| Install an SSL certificate | HTTPS is essential — see Install Free SSL Certificate |
| Redirect HTTP to HTTPS | See Redirect HTTP to HTTPS |
| Set the WordPress site URL | Ensure it uses https:// — see the WordPress settings |
| Install a security plugin | Harden the site against attacks |
| Install a caching plugin | Improve performance |
| Set up backups | WordPress sites need regular backups — see Backup Wizard |
| Update WordPress, themes, and plugins | Security and performance |
| Configure permalinks | Use a SEO-friendly structure — WordPress → Settings → Permalinks |
| Create a child theme if customizing | Prevents theme updates from overwriting changes |


Common Scenarios

"The installation succeeded but the site does not load"

  1. Check DNS — does the domain resolve to the server? See Track DNS.
  2. Check the document root — is WordPress in the right directory? See File Manager.
  3. Check the web server — is it running? See Service Status.
  4. Check the SSL certificate — if HTTPS is enforced but no certificate, the site will not load.

"The installation fails with a database error"

  1. Check the database password — it must be filled in.
  2. Check the database limit — the account may have reached its database quota. See Add/Modify Packages.
  3. Check MySQL — is it running? See Service Status.
  4. Check disk space — the account may be over quota. See Show Accounts Over Quota.

"WordPress is in the wrong directory"

If you installed WordPress in the wrong directory:

  1. Delete the installation via File Manager.
  2. Reinstall in the correct directory.
> Warning: Do not try to move WordPress files manually without updating the database and wp-config.php — the site will break. Reinstall is usually faster.

"I want WordPress in a subdirectory (e.g., /blog)"

  1. In the Directory field, append /blog to the document root (e.g., /home/emamazoz.com/www/blog).
  2. Complete the installation.
  3. The site is now at https://emamazoz.com/blog/.
> Tip: You can also install WordPress at the root and use it as the main site, or install it in a subdirectory and link to it from the main site.

"The customer's WordPress site was compromised"

  1. Reset the WordPress admin password — see Change WordPress Password.
  2. Review the WordPress users list for unauthorized admins.
  3. Scan for malware — see ClamAV Antivirus.
  4. Update WordPress, themes, and plugins — the most common compromise vector.
  5. Check wp-config.php for injected code.
  6. Review logs — see FTP Logs and Apache Status.
  7. Consider restoring from a clean backup — see Restore Full Backup.

Security Recommendations

| Practice | Why |
|---|---|
| Use a strong admin username | admin is the most targeted username |
| Use a strong admin password | Admin accounts are brute-force targets |
| Enable 2FA on WordPress | Adds a layer beyond the password |
| Keep WordPress updated | Outdated versions are the top compromise vector |
| Keep plugins and themes updated | Same reason |
| Remove unused plugins and themes | Every plugin is a potential vulnerability |
| Use a security plugin | Wordfence, iThemes Security, etc. |
| Install SSL | HTTPS protects login credentials |
| Back up regularly | WordPress sites are frequent targets — see Backup Wizard |
| Limit admin users | Fewer admins means fewer targets |
| Use file permissions | See Fix Permissions |

> Warning: A newly installed WordPress site is not automatically secure. Default settings, the admin username, and outdated plugins are common compromise vectors. Follow the recommendations above to harden the site.


Related Commands

| Command | Purpose |
|---|---|
| wp | WP-CLI — manage WordPress from the shell (if installed) |
| /go/conf | Rebuild web server config |
| /go/ssl domain.com | Install SSL for the site |
| /go/repair | Repair the WordPress database if needed |

See Command Reference for the full CLI list.


Related Pages

Troubleshooting

| Problem | Likely cause | Solution |
|---|---|---|
| Installation fails with "database error" | Wrong password, database limit reached, or MySQL down | Verify the password; check limits; check Service Status |
| Site does not load after install | DNS not pointing to the server, or wrong document root | Check Track DNS; verify the directory |
| "Error establishing a database connection" | Wrong credentials in wp-config.php | Verify in MySQL Databases; update wp-config.php |
| WordPress wizard does not appear | Installation incomplete, or wrong URL | Check the install log; try https://domain/wp-admin/install.php |
| Cannot log in to /wp-admin/ | Wrong credentials, or the user was not created | Use Change WordPress Password to reset |
| Site shows a blank page | PHP error suppressed | Enable display_errors temporarily in PHP Configuration; check the error log |
| Site shows "too many redirects" | HTTPS redirect misconfigured, or WordPress site URL wrong | Check Redirect HTTP to HTTPS; update the WordPress site URL in the database |
| Plugins cannot be installed | File permissions, or PHP memory limit | Check Fix Permissions and PHP Configuration |
| Site is slow | No caching, or PHP version too old | Install a caching plugin; use PHP 8.x — see MultiPHP Manager |
| WordPress is in the wrong directory | Installation path was set incorrectly | Delete and reinstall in the correct directory |


Best Practices

| Practice | Why |
|---|---|
| Use the latest WordPress version | Security and performance |
| Install SSL immediately | Protect login credentials |
| Use a non-default admin username | admin is the most targeted |
| Use a strong admin password | Brute-force protection |
| Enable 2FA on WordPress | Adds a layer beyond the password |
| Install a security plugin | Harden the site |
| Install a caching plugin | Improve performance |
| Set up regular backups | WordPress sites are frequent targets |
| Keep everything updated | Outdated plugins and themes are the top compromise vector |
| Remove unused plugins and themes | Every plugin is a potential vulnerability |
| Configure permalinks early | Changing them later breaks existing links |
| Use a child theme for customizations | Prevents theme updates from overwriting changes |
| Store the database password securely | You will need it for direct database access |
| Monitor the site | Use a security plugin or external monitoring |


Last updated: 2026-11-08

↑