Guides - Deploying WordPress through the Linode Marketplace
Quickly deploy a Compute Instance with many various software applications pre-installed and ready to use.
WordPress is an industry standard open source CMS (content management system) used by the majority of the web. With 60 million users around the globe, WordPress provides an intuitive platform for content-focused websites for both personal and business use. Its focus on best-in-class usability and flexibility makes it possible to have a customized website up and running in minutes.
Deploying a Marketplace App
The Linode Marketplace allows you to easily deploy software on a Compute Instance using the Cloud Manager. See Get Started with Marketplace Apps for complete steps.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Complete the form by following the steps and advice within the Creating a Compute Instance guide. Depending on the Marketplace App you selected, there may be additional configuration options available. See the Configuration Options section below for compatible distributions, recommended plans, and any additional configuration options available for this Marketplace App.
Click the Create Linode button. Once the Compute Instance has been provisioned and has fully powered on, wait for the software installation to complete. If the instance is powered off or restarted before this time, the software installation will likely fail.
To verify that the app has been fully installed, see Get Started with Marketplace Apps > Verify Installation. Once installed, follow the instructions within the Getting Started After Deployment section to access the application and start using it.
NoteEstimated deployment time: WordPress should be fully installed within 2-5 minutes after the Compute Instance has finished provisioning.
- Supported distributions: Debian 11, Ubuntu 22.04 LTS
- Recommended minimum plan: All plan types and sizes can be used, though a minimum of a 4GB Dedicated CPU Compute Instance is recommended for production websites.
- Email address (required): Enter the email address you wish to use when configuring the WordPress admin user, generating SSL certificates, and optionally creating DNS records for a custom domain.
- Admin Username (required): Username for your WordPress admin user account.
- Admin Password (required): Password for your WordPress admin user account.
rootpassword (required): The root password for your MySQL database.
- WordPress Database Password (required): The root password for your WordPress database.
- Website Title: Enter a title for your WordPress site.
Limited User (Optional)
You can optionally fill out the following fields to automatically create a limited user for your new Compute Instance. This is recommended for most deployments as an additional security measure. This account will be assigned to the sudo group, which provides elevated permission when running commands with the
- Limited sudo user: Enter your preferred username for the limited user.
- Password for the limited user: Enter a strong password for the new user.
- SSH public key for the limited user: If you wish to login as the limited user through public key authentication (without entering a password), enter your public key here. See Creating an SSH Key Pair and Configuring Public Key Authentication on a Server for instructions on generating a key pair.
- Disable root access over SSH: To block the root user from logging in over SSH, select Yes (recommended). You can still switch to the root user once logged in and you can also log in as root through Lish.
Custom Domain (Optional)
If you wish to automatically configure a custom domain, you first need to configure your domain to use Linode’s name servers. This is typically accomplished directly through your registrar. See Use Linode’s Name Servers with Your Domain. Once that is finished, you can fill out the following fields for the Marketplace App:
- Linode API Token: If you wish to use the Linode’s DNS Manager to manage DNS records for your custom domain, create a Linode API Personal Access Token on your account with Read/Write access to Domains. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See Get an API Access Token. If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
- Subdomain: The subdomain you wish to use, such as www for
- Domain: The domain name you wish to use, such as example.com.
Getting Started After Deployment
Accessing the WordPress Admin Dashboard
Open your web browser and navigate to
http://[domain]/wp-admin/, where [domain] can be replaced with the custom domain you entered during deployment or your Compute Instance’s IPv4 address or rDNS domain (such as
192-0-2-1.ip.linodeusercontent.com). See the Managing IP Addresses guide for information on viewing IP addresses and rDNS.
NoteA TLS/SSL certificate is automatically generated for your custom domain, enabling you to connect to the site over the
httpsprotocol. If you did not enter a custom domain, a TLS/SSL certificate is configured on the rDNS domain instead. Connections using your IP address are not secured and will use the
Within the login page that appears, enter the username (admin username) and password (admin password) that you created when you deployed this instance. Then click the Log In button.
Once logged in, the WordPress Admin Dashboard appears. From here, you can create new posts, add users, modify the theme, and adjust any settings.
Viewing Your Website
Open a web browser and navigate to
http://[domain], replacing [domain] with the custom domain you entered during deployment or your Compute Instance’s IPv4 address or rDNS domain. See the
Managing IP Addresses guide for information on viewing IP addresses and rDNS. Your WordPress site should now be displayed.
Manually Configure a Domain
If you didn’t set up a domain during the deployment process, you can add it manually following the instructions in this section. Before beginning, make sure you have a registered domain name.
Within the name servers for your domain name, create an A record. The hostname / name field should be @ for a bare domain (
example.tld) or should specify the subdomain you wish to use, such as app for
app.example.tld. It’s common to create two A records, one using @ and one using www. The IP address should be the IPv4 address of your new Compute Instance. If you do not have a name server, consider using Linode’s DNS Manager.
Update WordPress so that it uses your new domain name. This can be done directly in the WordPress Admin panel or through the command line. See Changing The Site URL to learn more.
Log in to Admin dashboard. See Accessing the WordPress Admin Dashboard.
Click on the Settings link in the sidebar and then click on the General option from the dropdown menu that appears.
Within the General Settings form, update the WordPress Address (URL) and Site Address (URL) fields with the full domain you assigned to your site (such as
Click the Save Changes button at the bottom of the form.
Now that your WordPress installation is deployed, you can start adding content and modifying it to suit your needs. Here are a few links to help get you started:
- WordPress Support: Learn the basic workflows for using WordPress.
- Securing WordPress: Advice on securing WordPress through HTTPS, using a secure password, changing the admin username, and more.
- WordPress Themes: A collection of thousands of WordPress themes.
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on