Wordpress One-Click Marketplace Does Not Install Successfully
I deployed a standard WP instance via the marketplace. I created a limited sudo user worker
and disabled root over ssh. After waiting 10 minutes and failing to log in as worker
I tried root and was successful. I dug around and found the worker
user was never created.
I then went to get my credentials and found there's no linode_credentials.txt
as stated in the guide: https://www.linode.com/docs/products/tools/marketplace/guides/wordpress/
I did an nmap scan and found 80 port isn't open
nmap -p22,80,443 139.144.xxx.xxx
Host is up (0.015s latency).
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp closed https
It looks like nothing was actually installed or deployed.
Here is a snippet of my stackscript.log
cat /var/log/stackscript.log | grep -i error
Getting requirements to build wheel: finished with status 'error'
error: subprocess-exited-with-error
raise AttributeError(attr)
AttributeError: cython_sources
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
note: This error originates from a subprocess, and is likely not a problem with pip.
I decided to finally just delete the entire thing and start over. However, I got the same exact issues. The issue might be on my end but I didn't really do anything except wait and log into the server. Anyone getting the same issue?
8 Replies
✓ Best Answer
Our Administrators are aware of this issue and are investigating. In the meantime, we have this guide that walks you through the installation of WordPress on an Instance manually. Obviously this process is a bit more labor intensive, however, if you need to get a new WordPress instance up and running ASAP, that guide will help you do it.
I've been with WP and with Linode for many years now and I agree with the above post… that if you want to install something… anything… it is simply better to do it manually using the supplied guides.
Whether it be the Linode Marketplace or the one-click installs that other ISPs provide, I've never seen one that does not have some kind of issue, and often a major one, with it.
If you have the experience (or the desire to get the experience) to use Linode or D.O. or any of the other cloud providers, you CAN install applications manually. (I don't mean compiling from source… as that is an option for those with more experience than most people have.)
Setting up a LAMP stack on Linode (or any provider) is not hard. The Linode docs are good and there are a zillion 3rd party docs out there that are sometimes even better. And once LAMP is installed, just about anything using LAMP, like WordPress (or Piwigo Gallery which I use) is quite easy and 99% foolproof.
@tlambert Thank you for the quick response and the guide! It might be a nice feature if Linode warns you that there is a known issue with the marketplace product and recommends a guide like that instead
@acanton77 I agree, I'll be building it from scratch instead. Most likely the approach I take moving forward as well
Agreed. I'm not super savvy linux admin. Been using Linode for 13 years though and thought I'd use the Marketplace to upgrade my installation from a few years ago. Wasted the better part of an hour troubleshooting things only to realize NOTHING was installed…
I know this thread is 2 months old now, but I am experiencing the same issues that were discussed in the initial thread. I initially just created an instance from the marketplace which worked just fine, then while messing around with the site settings locked myself out (silly me). I deleted the instance because I thought I could just create it using the same steps, but wordpress has failed to install each time after using the marketplace. I have installed it manually and worked fine, but if there is bugs with the marketplace installer should it be taken down or looked into again?.
@Skrumf - I just ran some tests of our WordPress Marketplace with both a LAMP and LEMP stack and ran into an error in one out of ~10 deploys. I doubt that you and I used that same input variables when deploying the app so that may have something to do with it. I let the Marketplace team know and they are looking into the issue now.
This post titled How can I troubleshoot a Marketplace App? has some great info on how to check what may have gone wrong during app deployment. Specifically, sharing the output of /var/log/stackscript.log
file either here or in a support ticket will give us a better idea of what went wrong.
@tlambert I gave it another go with the same variables and looked into the stackscript.log file and it seemed the issue is happening when it tries setting up the domain record. Once the linode spins up I get this message "msg": "failed to create domain record: 401: Your OAuth token is not author". Without adding in my domain the script works just fine. Would this issue happen because I have the domain hosted on namecheap and not in the DNS Zone in Linode?
Yep, that's likely the root cause. In order for your domain record to be created within the Linode DNS Manager you will need to add your domain to Linode's name servers. This is mentioned in the guide on Deploying the Wordpress Marketplace App.
To make this change, you can follow these instructions from NameCheap support.