WordPress Redis

Check that the three services are active, that only the expected ports listen and that the site answers locally:

sudo systemctl is-active apache2.service mysql.service redis-server.service
sudo ss -tln | grep -E ':(80|3306|6379) ' curl -s -o /dev/null -w 'wordpress http / -> %{http_code}\n' http://127.0.0.1/

Apache, MySQL and Redis are all active. Port 80 serves the site. MySQL (3306) and Redis (6379) listen on loopback only.

Check the WordPress version and the object cache status with WP-CLI:

cd /var/www/html/wordpress
sudo -u www-data /usr/local/bin/wp core version --allow-root sudo -u www-data /usr/local/bin/wp redis status --allow-root | grep -E 'Status:|Client:|Drop-in:|Redis Version:'

Status: Connected and Drop-in: Valid confirm that WordPress serves its object cache from Redis through PhpRedis. Redis requires the per-VM password, so it rejects an unauthenticated redis-cli ping.

Check the credentials file permissions, then read it:

sudo stat -c 'mode %a owner %U:%G' /stage/scripts/wordpress-redis-credentials.log
sudo cat /stage/scripts/wordpress-redis-credentials.log

The file is 0600 root:root and holds this instance's unique WP_ADMIN_PASSWORD, WP_ADMIN_URL, database password and Redis password. Nothing ships with a known password. First boot creates the WordPress admin for each VM, and blank or common default passwords are rejected.

Print the installed versions of WordPress, PHP, MySQL and Redis:

cd /var/www/html/wordpress
sudo -u www-data /usr/local/bin/wp core version --allow-root php -v | head -1 mysql --version redis-server --version | grep -oE 'v=[0-9.]+'

Browse to http://<public-ip>/ to see the WordPress front end with the default sample content.

Browse to http://<public-ip>/wp-admin/ (or /wp-login.php) and sign in as SecureAnyCloud with the WP_ADMIN_PASSWORD from Step 6.

The dashboard shows site activity, recent comments and a quick-publish box.

Go to Settings, then Redis, to see the object cache status, flush the cache or review metrics. Status Connected and Redis Reachable confirm that the cache is live.

• WordPress install: /var/www/html/wordpress/
• wp-config.php: /var/www/html/wordpress/wp-config.php
• Object cache drop-in: /var/www/html/wordpress/wp-content/object-cache.php
• Redis Object Cache plugin: /var/www/html/wordpress/wp-content/plugins/redis-cache/
• Redis config: /etc/redis/redis.conf (loopback, per-VM requirepass)
• Apache vhost: /etc/apache2/sites-available/wordpress.conf
• Apache logs: /var/log/apache2/wordpress-{access,error}.log
• MySQL data: /var/lib/mysql/
• WP-CLI: /usr/local/bin/wp
• First-boot script: /usr/local/sbin/wordpress-redis-firstboot.sh
• Credentials: /stage/scripts/wordpress-redis-credentials.log (mode 0600 root:root)

• HTTPS: install certbot and obtain a Let's Encrypt certificate with sudo apt-get install -y certbot python3-certbot-apache && sudo certbot --apache.
• Set your real domain: run sudo -u www-data wp option update home 'https://your-domain' and ... siteurl 'https://your-domain', or use the General settings screen.
• Restrict the NSG so port 80/443 is open to your CDN or load balancer only, and keep 22 limited to your management CIDR.
• Tune the cache: for larger working sets, adjust maxmemory in /etc/redis/redis.conf (it ships at 128mb, allkeys-lru). Flush the cache with Settings, Redis, Flush Cache.
• Update plugins and themes monthly with wp plugin update --all and wp theme update --all.
• Enable two-factor authentication with the Wordfence or Two Factor Authentication plugin.
• Patch monthly: run sudo apt-get update && sudo apt-get upgrade && sudo reboot.