It said it was successful, but the generic CyberPanel page still displayed when visiting the site.
Upon further investigation, the issue appeared to be with this command:
[email protected]:~# wp core download --allow-root --path=/home/example.com/public_html/
Downloading WordPress 5.5 (en_US)...
md5 hash verified: 983821e81b5b8398469e5c1807c4abf4
PHP Fatal error: Allowed memory size of 62914560 bytes exhausted (tried to allocate 36864 bytes) in phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Extractor.php on line 101
It looks like it ran out of memory during the installation.
Let’s review the memory limit and increase it if necessary.
I have a server at DigitalOcean with Ubuntu, CyberPanel, and OpenLiteSpeed, and wanted one of my websites to display an auto index of all the files uploaded to it.
There is a
default.php script in
/usr/local/lsws/share/autoindex that simulates Apache’s auto index, which suffices for my needs, but if you don’t want to use the default, you could copy and edit
default.php to create your own template.
Now, to enable and use this auto index, you have to adjust the
index directive in your website’s virtual host configuration file:
indexFiles index.php, index.html
I downloaded the MySQL server and installed it on my Mac, but every time I tried to connect to it, I got the following error:
Can’t connect to MySQL server on ‘127.0.0.1’ (61)
There can be many reasons for this error, most of which are generously covered online, but in my case it was because MySQL was running on port 3307. I think the port was updated in a recent MySQL server update, because I’ve never had this issue with a previous MySQL server version. Here’s how to check if you have the same problem, and how to change it to port 3306 (unless you want to keep it running on port 3307).
I installed GitLab CE using the Omnibus package on a new CentOS 6 server. Since I had nothing else on the server at that time, everything GitLab setup and configured was sufficient. Later, however, I wanted to setup additional sites on the server using Apache, but now port 80 was already bound to by GitLab’s built-in Nginx web server.
What I really wanted to do is disable the built-in Nginx server and just use my self-managed Apache installation. Here’s how to do just that.
Every now and then I’ll be connected to a server on my Mac with a very specific volume mounted, but then it doesn’t appear anywhere in Finder. When I try to reconnect to it, it’s grayed out, as if I was connected after all.
For a while, the only way I knew how to fix it was to restart, but that’s obviously most inconvenient.
Turns out, there is quite a simple solution, and that is to unmount the volume via the command line.
Open up Terminal and type in the following:
sudo umount -f "/Volumes/NameOfVolume"
Replacing “NameOfVolume” with your volume’s name. After you hit ENTER, type in your Mac’s password when prompted.
Once that’s done, reconnect to the server in Finder (COMMAND + K), select the volume that was previously grayed out, mount it, and now it’ll be in Finder again for you to browse.