Knowledgebase | VPSGrid
English
EnglishBeta EspañolPortuguês (Brasil)Coming soonFrançaisComing soonDeutschComing soon
Client Area

WordPress VPS — Setup, Management & Troubleshooting

0 found helpful

Getting started with your VPSGrid WordPress VPS

VPSGrid WordPress VPS plans (WP Starter through WP Max) run on Ubuntu 24.04 LTS with a one-click stack: Nginx, PHP, MariaDB, and WordPress core. After the VPS is online, the installer finishes automatically. You complete the WordPress setup wizard in the browser, then manage the site in wp-admin and the server over SSH.

What happens after your order is activated

  1. You receive a provisioning started confirmation email.
  2. Open Client Area → Services → My Services → your WordPress VPS.
  3. Watch the WordPress status panel on the service page (Creating → Preparing → Installing → WordPress is ready). First-time install often takes several minutes after the VPS is online; contact support if there is no progress after about 30 minutes.
  4. When the panel shows WordPress is ready, use View your website and WordPress dashboard to finish setup.

Find your WordPress details

ItemWhere to find it
Public site URLClient Area status panel → View your website (typically http://YOUR-IP/)
wp-admin URLClient Area status panel → WordPress dashboard (typically http://YOUR-IP/wp-admin/)
WordPress admin username / passwordYou create these in the WordPress setup wizard (not emailed by VPSGrid)

They are not the same page. Until you finish the wizard, the site may show the installer instead of your finished homepage.

Log in to WordPress

  1. Open View your website or WordPress dashboard from the service page.
  2. Complete the setup wizard: language, site title, admin username, password, and email.
  3. Click Install WordPress, then sign in at /wp-admin/.

Store the WordPress admin password securely. VPSGrid does not store or reset WordPress application passwords — use “Lost your password?†in wp-admin (if outbound email works) or recover via SSH/WP-CLI if you have server access.

Access your VPS with SSH

Server (SSH) credentials are separate from WordPress wp-admin credentials.

Server itemWhere to find it
Primary IPClient Area → service details
SSH usernameService details (typically root)
SSH passwordService details / service password (use Change Password to set a new one)

Connect with SSH to administer the server, files under /var/www/html/, and MariaDB. Database connection details created at install are also written to /root/vpsgrid-wordpress.txt on the VPS (SSH required). See How to Connect via SSH to Your VPSGrid Linux VPS and How to Enable SSH Key Authentication.

Important: The browser noVNC / VNC console is not available on WordPress VPS plans. Use SSH for server access and wp-admin for the application.

Manage your VPS from the Client Area

On WordPress VPS products, these controls are available:

  • Start / Stop / Reboot — power controls for the VPS
  • Change Password — sets a new server / SSH password (Cloud-Init + reboot on Linux). This does not change your WordPress wp-admin password. See How to Reset Your VPS Password.

Not available on WordPress VPS:

  • Browser console (noVNC / SPICE / xterm.js)
  • Self-service OS reinstall
  • Live Client Area resource graphs
  • Client Area hostname change

If a clean OS reinstall is required as a last resort, open a support ticket and follow How to Reinstall or Recover Your VPS Operating System.

Connect your domain

Ordering a WordPress VPS does not automatically point a domain at the server. Cloudflare is optional, not required.

  1. At your DNS provider, create A records for @ and www pointing to your VPS primary IP.
  2. Wait for DNS to resolve (often minutes; sometimes longer).
  3. In WordPress: Settings → General — set WordPress Address and Site Address to your domain (use https:// only after SSL is working).

Guides: How to Point a Domain to Your VPS IP, Pointing Your Domain to Your VPS.

SSL / HTTPS

The one-click installer serves WordPress over HTTP (port 80). SSL is not issued automatically at provision time.

  • Point DNS to the VPS IP first and confirm the site loads by domain over HTTP.
  • Then install TLS yourself (for example with Certbot on Ubuntu, or a trusted WordPress SSL plugin).
  • Do not expect HTTPS to work before DNS resolves correctly.

For general Ubuntu WordPress/LEMP SSL context, see How to Deploy WordPress on Ubuntu VPS (manual reference — your stack is already installed).

WordPress updates and basic maintenance

  • Keep WordPress core, plugins, and themes updated from Dashboard → Updates.
  • Use a strong unique wp-admin password; remove unused plugins.
  • Back up content before major plugin or theme changes (plugin backup, off-site copy, or a purchased backup add-on if you have one). VPSGrid does not automatically back up the VPS disk unless you have an active backup product.
  • Outbound port 25 is restricted — use an SMTP plugin (port 587/465) for reliable WordPress email.

What to do if WordPress is not reachable

  1. Confirm the service is Active / running in the Client Area. Use Start if it is stopped.
  2. If you use a custom domain, verify DNS A records point to the current VPS IP.
  3. Try the direct IP links from the status panel (http://YOUR-IP/ and /wp-admin/).
  4. If the site fails but the VPS should be up, try SSH. Check disk space (df -h) and services (systemctl status nginx php*-fpm mariadb).
  5. Reboot from the Client Area only if the VPS appears stuck or a service will not start.
  6. Do not look for noVNC on WordPress VPS. Do not treat OS reinstall as normal troubleshooting.

Common application issues

  • Error establishing database connection: MariaDB may be down — reboot or start MariaDB over SSH. Compare wp-config.php with /root/vpsgrid-wordpress.txt.
  • 502 / blank page: Check Nginx/PHP-FPM status and free disk space.
  • Cannot log in to wp-admin: Use the WordPress admin user from the setup wizard — not the SSH root password. See also How to Reset Your VPS Password for server password changes only.
  • White screen: Temporarily enable WP_DEBUG, disable plugins via SSH if needed, check /var/log/nginx/error.log.

Contact VPSGrid support

Open a support ticket for provisioning stuck beyond ~30 minutes, unreachable VPS after reboot, billing, or network issues on the platform. Include service ID, primary IP, and steps already tried. See How to Open a Support Ticket for VPS Issues and Security Responsibilities on Unmanaged VPS.

Plugin/theme bugs and content work are outside standard unmanaged VPS support unless you have a separate managed arrangement.

Related articles

Was this answer helpful?

Related Articles

« Back Browse all articles