Tencent Cloud Account with Balance Deploy WordPress on Tencent Cloud CVM Step by Step

Tencent Cloud / 2026-05-14 22:06:34

{ "description": "This step-by-step guide walks you through deploying WordPress on Tencent Cloud CVM, from planning your instance and network settings to installing Nginx, PHP, and MySQL. It covers creating security rules, preparing storage, configuring a domain with DNS, and obtaining an SSL certificate for HTTPS. You’ll also learn how to harden basic settings, optimize performance, and verify the site with a full checklist. Along the way, you’ll get practical command examples, common pitfalls, and quick troubleshooting so your WordPress launch feels less like a quest and more like a victory lap.", "content": "

Introduction: A WordPress Welcome Party on CVM

So you want to deploy WordPress on Tencent Cloud CVM. Excellent choice. WordPress is like a friendly golden retriever: extremely helpful, widely understood, and slightly chaotic until you set some boundaries. Tencent Cloud CVM is the capable owner holding the leash and providing snacks (also known as compute resources).

This guide is written for practical humans who prefer doing things rather than reading about doing things. We’ll go step by step: picking and launching a CVM instance, setting up networking and security, installing the web stack (Nginx + PHP + MySQL), configuring WordPress, wiring in a domain, enabling HTTPS, and doing basic sanity checks. If you follow along, you’ll have a working WordPress site and the confidence of someone who has successfully wrestled a server into behaving.

We’ll assume you’re using a common Linux distribution such as Ubuntu 20.04/22.04 or CentOS 7/8. Commands may vary slightly. If you get a command error, don’t panic—copy the error text into your brain (like a memory of pain), then adjust to your OS. The server will survive; you might even learn something.

\n\n

Step 0: Decide Your Setup (Before You Press the “Deploy” Button)

Before you create the instance, decide what kind of WordPress site you’re building. Small blog? Business site? WooCommerce store? The requirements differ, but here are reasonable starting points:

CPU/RAM: For a basic site and light traffic, 1 vCPU and 2 GB RAM is usually okay. For more traffic, scale up.
Storage: A typical starting disk size is 40 GB. WordPress itself isn’t huge, but backups, plugins, and database growth will happen.
Region: Pick the region closest to your users to reduce latency.

Also decide:

Will you use a domain name?
Will you need HTTPS (you do, unless you enjoy browser warnings)?
Do you want email sending? (That’s a separate can of worms; this guide focuses on the web stack.)

\n\n

Step 1: Create a Tencent Cloud CVM Instance

Log into Tencent Cloud Console, then find CVM (Cloud Virtual Machine). Create a new instance. During setup, you’ll typically choose:

Image/OS: Ubuntu or CentOS.
Instance Type: Standard general purpose.
Networking: Usually a VPC plus subnet.
Authentication: SSH key is preferable; passwords are okay but less fun to manage.

Tip: Use a strong SSH key and keep it safe. If someone else gets your private key, your server will become their personal blog. Which might be entertaining… for them.

\n\n

Step 2: Configure Security Group Rules (Firewall Before You Begin Cooking)

Security groups control inbound traffic. For WordPress you typically need:

HTTP: port 80
HTTPS: port 443
SSH: port 22 (temporarily from your IP, not from the whole internet)

In the Tencent Cloud console, locate the security group attached to your CVM. Add inbound rules like:

Allow TCP 80 from 0.0.0.0/0 (or better: limit if you want)
Allow TCP 443 from 0.0.0.0/0
Allow TCP 22 from your IP only

Tencent Cloud Account with Balance Don’t expose SSH to the whole world if you value your server’s peace of mind. Attackers love random ports; they also love open doors.

\n\n

Step 3: Connect to Your CVM via SSH

Once the instance is running, get its public IP. Then connect with SSH from your local machine.

Tencent Cloud Account with Balance Example (using a private key):

ssh -i /path/to/your-key.pem ubuntu@YOUR_PUBLIC_IP

If you’re using CentOS, it might be:

ssh -i /path/to/your-key.pem centos@YOUR_PUBLIC_IP

After connecting, update your package lists:

sudo apt-get update -y

Then upgrade packages:

sudo apt-get upgrade -y

(On CentOS, use yum or dnf equivalents.)

\n\n

Step 4: Set Up a Directory and Storage (Optional but Sensible)

WordPress can live under /var/www/html. But it’s also fine to create a dedicated directory like /var/www/wordpress for clarity.

Create a directory:

sudo mkdir -p /var/www/wordpress

Then set permissions (use the web server user later). For now you can ensure you have a consistent ownership base. On Ubuntu with Nginx, that often means www-data.

sudo chown -R www-data:www-data /var/www/wordpress

\n\n

Step 5: Install Nginx, PHP, and Required Extensions

Now we assemble the web stack. WordPress on modern Linux usually runs happily with Nginx + PHP-FPM + MySQL/MariaDB.

\n\n

5.1 Install Nginx

sudo apt-get install nginx -y

Start and enable it:

sudo systemctl enable nginx

sudo systemctl start nginx

Quick check: open your browser to http://YOUR_PUBLIC_IP. You should see the default Nginx page (or at least something less mysterious than a blank void).

\n\n

5.2 Install PHP and PHP-FPM

Install PHP packages. For Ubuntu, a typical set might include PHP 8.1. If your OS has an appropriate default version, you can use it; otherwise you might use a PPA. Keep it simple first.

Example for PHP 8.1:

sudo apt-get install php-fpm php-mysql php-xml php-curl php-gd php-mbstring php-zip php-intl -y

Enable and start PHP-FPM:

sudo systemctl enable php8.1-fpm

sudo systemctl start php8.1-fpm

If your PHP-FPM service name differs (like php-fpm), use:

systemctl list-unit-files | grep php

\n\n

5.3 Configure Nginx to Use PHP-FPM

We’ll later create a site configuration. For now, test that Nginx can pass PHP requests to PHP-FPM.

Create a test PHP file:

sudo tee /var/www/wordpress/info.php <<'EOF'\n<?php\nphpinfo();\nEOF

Now temporarily configure Nginx to serve it. We’ll do a proper configuration in a later step, but for immediate confidence:

Locate Nginx server blocks:

ls /etc/nginx/sites-available

On Ubuntu, a default file might exist. You can create a new one, for example wordpress.conf and then enable it.

\n\n

Step 6: Install MySQL (or MariaDB)

WordPress needs a database. Many people use MySQL or MariaDB. MariaDB is common on CentOS; MySQL packages vary by distribution.

\n\n

6.1 Install MySQL

On Ubuntu, commonly:

sudo apt-get install mysql-server -y

During installation, you’ll set a root authentication approach. On modern Ubuntu, the easiest is often socket-based auth for root and then creating WordPress users properly.

\n\n

6.2 Secure the Database (Recommended)

Run:

sudo mysql_secure_installation

Follow prompts. Choose a strong root password if asked (or use the recommended approach). Remove anonymous users and disallow remote root login unless you intentionally want that.

\n\n

6.3 Create WordPress Database and User

Log into MySQL:

sudo mysql

Create database (replace names as you like):

CREATE DATABASE wordpress_db CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

Create user and grant permissions:

CREATE USER 'wp_user'@'localhost' IDENTIFIED BY 'StrongPasswordHere!';

GRANT ALL PRIVILEGES ON wordpress_db.* TO 'wp_user'@'localhost';

FLUSH PRIVILEGES;

Exit:

exit

\n\n

Step 7: Download and Configure WordPress

Next, download WordPress, extract it, and set up the configuration file.

\n\n

7.1 Download WordPress

Tencent Cloud Account with Balance Move into your web root directory:

cd /var/www/wordpress

Download WordPress. You can use curl or wget. Example with wget:

sudo apt-get install wget -y

wget https://wordpress.org/latest.tar.gz

Extract:

sudo tar -xzf latest.tar.gz --strip-components=1

Remove the tarball:

sudo rm -f latest.tar.gz

\n\n

7.2 Configure wp-config.php

Copy the sample config:

sudo cp wp-config-sample.php wp-config.php

Edit wp-config.php and set database details.

Use nano for simplicity:

sudo nano wp-config.php

Find these lines and update:

define('DB_NAME', 'wordpress_db');
define('DB_USER', 'wp_user');
define('DB_PASSWORD', 'StrongPasswordHere!');
Set DB host usually localhost

Also set site URL and home URL later during WordPress setup if needed. But you can also set them here after domain is ready.

\n\n

7.3 Fix Permissions

WordPress needs correct ownership for updates and plugins.

sudo chown -R www-data:www-data /var/www/wordpress

\n\n

Step 8: Create Nginx Site Configuration for WordPress

Now we make Nginx behave like a responsible host, not a confusing museum guide.

\n\n

8.1 Create a Nginx Server Block

Create a file in /etc/nginx/sites-available called wordpress or wordpress.conf.

sudo nano /etc/nginx/sites-available/wordpress

Use a configuration like the following. Replace `YOUR_SERVER_NAME_OR_DOMAIN` and adjust PHP version if needed.

server {\n    listen 80;\n    listen [::]:80;\n    server_name YOUR_SERVER_NAME_OR_DOMAIN;\n\n    root /var/www/wordpress;\n    index index.php index.html;\n\n    client_max_body_size 20M;\n\n    location / {\n        try_files $uri $uri/ /index.php?$args;\n    }\n\n    location ~ \\.php$ {\n        include snippets/fastcgi-php.conf;\n        fastcgi_pass unix:/run/php/php8.1-fpm.sock;\n        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;\n        include fastcgi_params;\n    }\n\n    location ~* \\.(jpg|jpeg|png|gif|ico|css|js|woff|woff2|ttf|svg|eot)$ {\n        expires 30d;\n        access_log off;\n        log_not_found off;\n    }\n\n    location = /favicon.ico { access_log off; log_not_found off; }\n    location = /robots.txt  { access_log off; log_not_found off; }\n}\n

Notes:

Make sure the fastcgi_pass socket path matches your PHP-FPM version. Common Ubuntu path examples: /run/php/php8.1-fpm.sock or /run/php/php8.2-fpm.sock.
If your PHP-FPM socket differs, find it with:

ls /run/php/

\n\n

8.2 Enable the Site and Disable Default

sudo ln -s /etc/nginx/sites-available/wordpress /etc/nginx/sites-enabled/

Disable default if you want:

sudo rm -f /etc/nginx/sites-enabled/default

Test Nginx configuration:

sudo nginx -t

If it says “syntax is ok” and “test is successful,” reload Nginx:

sudo systemctl reload nginx

\n\n

Step 9: Install WordPress Through the Web UI

Now visit your server in a browser:

http://YOUR_PUBLIC_IP (for first testing)
or http://YOUR_DOMAIN (once DNS is ready)

You should see the WordPress setup page. It will ask for:

Site title
Admin username
Admin password
Admin email

WordPress will then connect to the database using wp-config.php. If it can’t connect, don’t assume you did nothing wrong. Servers enjoy being helpful by being wrong in very specific ways.

\n\n

Step 10: Add Domain DNS Records

To use a custom domain, update DNS at your domain registrar or DNS provider.

Commonly you’ll add an A record pointing to your CVM public IP:

Type: A
Host: @ (or your root domain)
Value: Your CVM public IP
TTL: default or 300

Optionally add:

CNAME for www to your root domain

Wait for DNS propagation. It might take a few minutes, or it might take longer. DNS propagation is like coffee: sometimes it’s immediate, sometimes it’s a lifestyle choice.

\n\n

Step 11: Enable HTTPS with SSL (Let’s Encrypt)

HTTPS is non-negotiable in 2026 unless your goal is to collect browser warnings like trading cards.

\n\n

11.1 Install Certbot

Install Certbot and Nginx plugin:

sudo apt-get install certbot python3-certbot-nginx -y

\n\n

11.2 Obtain an SSL Certificate

Run:

sudo certbot --nginx -d YOUR_DOMAIN -d www.YOUR_DOMAIN

Certbot will detect Nginx server blocks, request certificates, and update configs automatically.

If it asks to redirect HTTP to HTTPS, enable redirection. If it asks about email for urgent notices, give it a valid email because certificates do expire even when you look away.

\n\n

11.3 Auto-Renewal Check

Certbot typically installs a systemd timer for renewal. Verify:

systemctl list-timers | grep certbot

Tencent Cloud Account with Balance You can also do a dry run:

sudo certbot renew --dry-run

\n\n

Step 12: WordPress Hardening (Small Tweaks, Big Peace)

Now that WordPress is running, let’s tighten the bolts. Not paranoid-security-level, just sensible improvements.

\n\n

12.1 Update WordPress and Plugins

In the WordPress dashboard, check for updates. Core updates and plugin updates close security gaps. Outdated software is like leaving a window open in a thunderstorm.

\n\n

12.2 Configure wp-cron Properly (Optional)

Tencent Cloud Account with Balance WordPress uses wp-cron for scheduled tasks. Sometimes people disable it and use system cron. If you want the simple default, you can keep it.

If you use system cron, you can set:

crontab -e

Add a line like:

* * * * * curl -s https://YOUR_DOMAIN/wp-cron.php?doing_wp_cron >/dev/null 2>&1

Be sure the URL uses HTTPS and your domain is correct.

\n\n

12.3 Disable File Editing in Dashboard

To prevent editing theme/plugin files from the admin panel, add this to wp-config.php:

define('DISALLOW_FILE_EDIT', true);

\n\n

12.4 Set Reasonable File Permissions

Make sure directories and files aren’t writable by the world. WordPress typically needs write permissions to certain folders (like wp-content).

You can start with:

sudo find /var/www/wordpress -type d -exec chmod 755 {} \\\;

sudo find /var/www/wordpress -type f -exec chmod 644 {} \\\;

Then ensure wp-content is writable by Nginx/PHP:

sudo chown -R www-data:www-data /var/www/wordpress/wp-content

Be careful with permissions; if you make them too strict, updates and uploads may fail. If you make them too lax, security suffers. We want “safe and functional,” not “all-powerful and risky.”

\n\n

Step 13: Performance and Reliability Tips

You don’t need perfection on day one, but a few tweaks help WordPress feel snappy.

\n\n

13.1 Enable Gzip Compression

Edit Nginx configuration (often in /etc/nginx/nginx.conf), and ensure gzip is enabled. Example:

gzip on;\ngzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript image/svg+xml;\n

Then test and reload:

sudo nginx -t

sudo systemctl reload nginx

\n\n

13.2 Consider Caching Plugins

WordPress caching plugins can improve speed significantly. Options include page caching and object caching. However, start with one caching plugin and test. Running three caching plugins is like giving a dog three leashes and asking it to fetch reliably.

\n\n

13.3 Use a Reasonable PHP Version

Newer PHP versions generally run WordPress better. Stick to a supported PHP version, not an antique that only runs because it enjoys chaos.

\n\n

Step 14: Troubleshooting Guide (When Things Don’t Immediately Work)

Here’s the reality: sometimes WordPress won’t load on the first try. Servers love dramatic entrances, not smooth ones. Let’s fix common problems.

\n\n

14.1 Nginx Returns 502 Bad Gateway

This usually means PHP-FPM isn’t working or the socket path is wrong.

Check PHP-FPM status:

sudo systemctl status php8.1-fpm

Check Nginx error logs:

sudo tail -n 200 /var/log/nginx/error.log

If the fastcgi_pass socket path is wrong, update it to the correct one and reload Nginx.

\n\n

14.2 WordPress Installation Fails to Connect to Database

Check wp-config.php for:

DB_NAME
DB_USER
DB_PASSWORD
DB_HOST (usually localhost)

Also verify MySQL user privileges and that the MySQL service is running:

sudo systemctl status mysql

If you created the user with 'wp_user'@'localhost' but WordPress tries a different host, you might need to adjust grants. Typically it’s localhost and everything is fine.

\n\n

14.3 HTTP Works but HTTPS Doesn’t

Tencent Cloud Account with Balance This can happen if DNS isn’t pointing to the correct IP or if the Nginx server block doesn’t match the domain.

Check:

DNS A record for your domain
Nginx server_name
Certbot logs at /var/log/letsencrypt/

Also run:

sudo certbot renew --dry-run

\n\n

14.4 WordPress Loads but Uploads Fail

Tencent Cloud Account with Balance Common causes:

Incorrect ownership of wp-content
Permission issues on uploads directory

Fix ownership:

sudo chown -R www-data:www-data /var/www/wordpress/wp-content

Then retry uploads.

\n\n

14.5 The Site Loads Slowly

Try these steps:

Enable caching (plugin or Nginx caching)
Check server CPU/RAM usage
Review slow database queries (later advanced step)

You can check resource usage quickly:

top

Or:

free -h

\n\n

Step 15: Backups and Monitoring (Because Life Happens)

Before you relax, implement backups. If your server gets nuked by mistake, you’ll be staring at your database like it owes you money.

\n\n

Tencent Cloud Account with Balance 15.1 Database Backups

You can use mysqldump and store backups on disk or object storage.

Example (manual):

mysqldump -u wp_user -p wordpress_db > /tmp/wordpress_db_$(date +%F).sql

For automated backups, use a cron job and consider storing backups in a persistent location or external storage.

\n\n

15.2 File Backups

At minimum, back up:

/var/www/wordpress (themes, plugins, uploads)

Tencent Cloud Account with Balance Better backups reduce restoration pain later. Future you will send present you a thank-you email. Or at least a satisfying text message.

\n\n

15.3 Monitoring

Consider basic monitoring:

CPU and memory usage alerts
Disk space alerts
Web server availability checks

On Tencent Cloud, you may have monitoring tools available. Enable them if you can.

\n\n

Step 16: Final Verification Checklist (The “Make Sure It’s Real” Section)

Before you tell anyone your WordPress is live, run this checklist:

Nginx: sudo nginx -t passes and service is running
PHP-FPM: PHP-FPM service is active
Database: WordPress can create/update tables during install
WordPress login: You can log in to admin dashboard
Uploads: You can upload a media file
Permalinks: Permalink settings work (try visiting a post URL)
HTTPS: Browser shows a valid certificate without warnings
Security: You restricted SSH access and disabled file editing
Backups: You have at least a basic backup plan

Then remove any test files like info.php if you created them earlier:

sudo rm -f /var/www/wordpress/info.php

Leaving a phpinfo page lying around is a little like leaving your Wi-Fi password on a sticky note on the monitor. Sure, it’s “convenient,” but it’s also a choice.

\n\n

Optional Step: Configure WordPress Permalinks and Nginx Rewrite Rules

WordPress permalinks require Nginx rewrite behavior. Our earlier configuration with try_files and passing requests to index.php generally supports it.

In WordPress dashboard, go to Settings → Permalinks. Set your preferred structure (for example “Post name”). Save changes. If permalinks produce 404 errors, check:

Nginx configuration
Whether try_files includes /index.php?$args
Nginx reload success

\n\n

Optional Step: Add Caching Headers for Static Assets

If you didn’t already include it, you can configure longer cache durations for static resources. This reduces repeated downloads and speeds up page loads.

Our earlier config already includes a section for common file types with expires 30d. If you add more file types, ensure they’re truly static and versioned or hashed so updates propagate correctly.

\n\n

Optional Step: Increase Upload Size if Needed

WordPress uploads sometimes fail when files exceed the Nginx limit. If you see errors, adjust:

client_max_body_size

In the server block, set for example:

client_max_body_size 50M;

Then reload Nginx:

sudo systemctl reload nginx

\n\n

Common Pitfalls (So You Don’t Have to Learn the Hard Way)

Tencent Cloud Account with Balance Wrong PHP-FPM socket path: causes 502 errors.
Over-permissive SSH access: invite trouble.
DNS not updated: HTTPS fails or domain doesn’t match certificate.
Permissions issues: uploads and plugin updates fail.
Leaving test files: remove info.php.
Not checking logs: logs are the truth tellers.

When in doubt, check logs first. It’s like checking your windshield before blaming the rain.

\n\n

Conclusion: Your WordPress Is Up, Now Go Publish Something

Deploying WordPress on Tencent Cloud CVM doesn’t have to feel like summoning a server demon. With the steps above, you’ve built a working Nginx + PHP-FPM + MySQL environment, configured WordPress, secured access with HTTPS, and validated functionality with a sensible checklist.

And now you can do the fun part: publish. Add themes, install plugins, write posts, and enjoy the fact that your website can now speak fluent HTTP and survive HTTPS like a champ.

If you run into trouble, revisit the troubleshooting sections and check the relevant logs. Servers don’t enjoy secrets; they prefer receipts. Good luck—and may your database connections be stable and your deployments be boring (in the best way).

" }