Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Kepler is a powerful drag & drop WordPress website builder with all-new website style filters that instantly change the look and feel of your website.

Note
Kepler requires a valid license to use the software beyond the initial 14 day free trial period. To purchase a license, visit Kepler’s website and select a plan that fits your needs. Licenses are not available directly through Linode.

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.

  1. 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.

  2. Under the Select App section, select the app you would like to deploy.

  3. 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.

  4. 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.

Note
Estimated deployment time: Kepler should be fully installed within 2-5 minutes after the Compute Instance has finished provisioning.

Configuration Options

  • Supported distributions: Ubuntu 22.04 LTS
  • Recommended minimum plan: All plan types and sizes can be used.

Kepler Options

  • Webserver Stack (required): Chose which web server to use for the WordPress deployment, Apache2 or NGINX.

  • 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.

  • Wordpress Admin Username (required): Username for your WordPress admin user account. Defaults to admin if no username is entered.

  • WordPress Database Username (required): MySQL username for the WordPress database user. Defaults to wordpress if no username is entered.

  • WordPress Database Name (required): Name for the WordPress MySQL database. Defaults to wordpress if no database name is defined.

  • Website Title: Enter a title for your WordPress site.

    Note
    The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file /home/$USERNAME/.credentials when the WordPress deployment completes.

Limited Sudo User

You need to fill out the following fields to automatically create a limited sudo user, with a strong generated password for your new Compute Instance. This account will be assigned to the sudo group, which provides elevated permissions when running commands with the sudo prefix.

  • Limited sudo user: Enter your preferred username for the limited user. No Capital Letters, Spaces, or Special Characters.

    Locating The Generated Sudo Password

    A password is generated for the limited user and stored in a .credentials file in their home directory, along with application specific passwords. This can be viewed by running: cat /home/$USERNAME/.credentials

    For best results, add an account SSH key for the Cloud Manager user that is deploying the instance, and select that user as an authorized_user in the API or by selecting that option in the Cloud Manager. Their SSH pubkey will be assigned to both root and the limited user.

  • Disable root access over SSH: To block the root user from logging in over SSH, select Yes. You can still switch to the root user once logged in, and you can also log in as root through Lish.

    Accessing The Instance Without SSH
    If you disable root access for your deployment and do not provide a valid Account SSH Key assigned to the authorized_user, you will need to login as the root user via the Lish console and run cat /home/$USERNAME/.credentials to view the generated password for the limited user.

Warning
Do not use a double quotation mark character (") within any of the App-specific configuration fields, including user and database password fields. This special character may cause issues during deployment.

Additional Security Options (Optional)

  • Configure automatic security updates: Select Yes to have the system automatically update WordPress with the latest security updates. Select No to if you wish to manage all updates manually.
  • Use fail2ban to prevent automated intrusion attemps? Select Yes to install fail2ban. Select No to not install fail2ban during installation. You can install this at a later time.

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 www.example.com.

  • Domain: The domain name you wish to use, such as example.com.

  • Do you need an MX record for this domain? Check Yes if you plan on using WordPress to send email. The installer, along with your API Token (required) sets up the necessary MX records in the DNS Manager. Select No if you do not plan on using WordPress to send email. You can add an MX record manually at a later time if you change your decision.

  • Do you need an SPF record for this domain? Check yes if you plan on using WordPress to send email. The installer, along with your API Token (required) sets up the necessary SPF records in the DNS Manager. Select No if you do not plan on using WordPress to send email. You can add an SPF record manually at a later time if you change your decision.

  • Would you like to use a free Let’s Encrypt SSL certificate? Select Yes if you would like the install to create an SSL certificate for you, or No if you do not. You cannot create secure, encrypted conferences without an SSL certificate.

Getting Started After Deployment

Obtain the Credentials

Once the app has been fully deployed, you need to obtain the credentials from the server.

  1. Log in to your new Compute Instance using one of the methods below:

    • Lish Console: Within the Cloud Manager, navigate to Linodes from the left menu, select the Compute Instance you just deployed, and click the Launch LISH Console button. Log in as the root user. See Using the Lish Console.
    • SSH: Log in to your Compute Instance over SSH using the root user. See Connecting to a Remote Server Over SSH for assistance.
  2. Once logged in, access the credentials file by running the following command:

    cat /home/$USERNAME/.credentials
  3. This displays the passwords that were automatically generated when the instance was deployed. Once you save these passwords, you can safely delete this file.

Accessing the WordPress Admin Dashboard

  1. 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.

  2. Within the login page that appears, enter the username (admin username) that you created when you deployed this instance and the associated password that was automatically generated. Then click the Log In button.

  3. 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.

Email restrictions on the Linode Platform
In an effort to fight spam originating from our platform, outbound connections on ports 25, 465, and 587 are blocked by default on Compute Instances for some new accounts. These restrictions prevent applications from sending email. If you intend to send email from a Compute Instance, review the Send Email on the Linode Platform guide to learn more about our email policies and to request the removal of these restrictions.

Going Further

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:

Note
Currently, 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.

More Information

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


Your Feedback Is Important

Let us know if this guide was helpful to you.