Skip to content

2020

  • in podcast
  • 2 min read

Fix WordPress Plugin Installation Permission Issue

Hello and welcome to "Continuous Improvement," the podcast where we explore solutions to the everyday challenges we encounter in our digital lives. I'm your host, Victor.

In today's episode, we're going to delve into a common issue faced by WordPress users when installing plugins. Have you ever come across the error message, "Installation failed: Download failed. Destination directory for file streaming does not exist or is not writable?" Well, fear not, because we have the solution for you.

Recently, while working on my WordPress website, I encountered this very issue. After some investigation, I discovered that the problem lay within the permissions of the content folder. This happened because I had been editing files as a superuser, using the "sudo su" command, while the installation required write access for the "ec2-user."

So, let's get to the solution. Assuming you are setting up on AWS EC2 instances and logged in as the "ec2-user," and assuming that your WordPress installation is located in the "/var/www" path, you'll need to execute the following command to change the ownership:

Open up your terminal and type:

"sudo chown -R ec2-user:apache /var/www."

This command changes the ownership of the WordPress directory to the "ec2-user" and the "apache" group. After executing this command, you should now be able to successfully install your desired plugin.

And there you have it! A simple solution to a common WordPress installation problem. By changing the ownership of the directory, we ensure that the correct user has the necessary write permissions to complete the plugin installation.

Remember, continuous improvement is all about finding solutions to the obstacles we encounter along our digital journeys. If you have any questions or suggestions for future topics, please feel free to reach out to us.

Thank you for tuning in to this episode of "Continuous Improvement." I hope you found the solution to the WordPress plugin installation error helpful. Until next time, keep improving!

  • in zh
  • 1 min read

修復WordPress插件安裝權限問題

問題

當我嘗試在WordPress中安裝插件時，遇到了以下錯誤：

安裝失敗：下載失敗。檔案串流的目標目錄不存在，或者無法寫入。

這個問題是由於內容文件夾的權限問題導致的。我已經以超級用戶（sudo su）的身份編輯了一些文件，但安裝需要ec2-user的寫入權限。

解決方案

假設你在AWS EC2實例上進行設定，並且已登入為ec2-user，並假設WordPress位於/var/www路徑中，執行以下命令以更改所有權：

sudo chown -R ec2-user:apache /var/www

改變所有權後，你現在應該可以成功地安裝插件。

  • 1 min read

Fix WordPress with All Pages Returning 404 Not Found

Problem

I encountered a strange issue with WordPress: while the homepage loaded properly, all the other pages failed to do so. Instead, an error page displayed the message:

Not Found

The requested URL was not found on this server.

However, since I had migrated the files from another server, all the pages should already exist. I suspected that the .htaccess file might be the culprit, but after hours of troubleshooting, I still had no clue.

Solution

As it turns out, in my case, the .htaccess file was correctly configured. The issue lay elsewhere. To resolve it, edit the httpd.conf file:

    sudo vi /etc/httpd/conf/httpd.conf

Locate the section that starts with:

    <Directory "/var/www/html">

Change the configuration from AllowOverride None to:

    AllowOverride All

Finally, restart the server:

    sudo systemctl restart httpd

After doing this, all the pages should render properly.

  • in podcast
  • 2 min read

Fix WordPress with All Pages Returning 404 Not Found

Welcome to another episode of "Continuous Improvement," the podcast where we delve into common issues and their solutions for web development. I'm your host, Victor. In today's episode, we'll be discussing a perplexing problem with WordPress and how to resolve it. So let's dive right in.

A while ago, I stumbled upon a strange error with WordPress. While the homepage loaded fine, all the other pages returned a dreaded "Not Found" error, claiming that the requested URL was not found on the server. Puzzled, I began investigating the issue, suspecting it might have to do with the .htaccess file. However, after spending hours troubleshooting, I realized that the problem lay elsewhere.

To fix this particular issue, I discovered that the solution lies in editing the httpd.conf file. You can find it by typing the following command:

sudo vi /etc/httpd/conf/httpd.conf

This command will open the configuration file in the built-in text editor, "vi." Once opened, search for the section that starts with:

<Directory "/var/www/html">

In this section, you'll need to modify the configuration from AllowOverride None to:

AllowOverride All

This change allows the server to inherit the .htaccess settings, ensuring that all the pages render correctly. Once you've made the alteration, it's time to restart the server. You can do this by executing the command:

sudo systemctl restart httpd

And voila! After performing these steps, all your WordPress pages should now load without any issues.

And there you have it! The solution to the perplexing issue of WordPress pages returning a "Not Found" error. By modifying the httpd.conf file and changing the configuration from AllowOverride None to AllowOverride All, we allow the server to read the .htaccess file and enable the proper rendering of all pages.

I hope you found this episode of "Continuous Improvement" insightful. Stay tuned for more troubleshooting tips and web development solutions. If you have any questions or suggestions for future episodes, feel free to reach out. Until then, keep improving and happy coding!

  • in zh
  • 1 min read

修復WordPress，所有頁面都返回404未找到

問題

我遇到了一個關於WordPress的奇怪問題：首頁可以正常加載，但所有其他頁面都無法做到。相反，錯誤頁面顯示了這樣的信息：

未找到

找不到請求的URL在此服務器上。

然而，由於我已經將檔案從另一台服務器遷移過來，所以所有頁面都應該已經存在。我懷疑.htaccess檔案可能是問題所在，但經過幾個小時的故障排除，我仍然沒有線索。

解決方案

事實證明，在我的情況下，.htaccess檔案配置正確。問題在於其他地方。要解決它，编辑httpd.conf檔案：

    sudo vi /etc/httpd/conf/httpd.conf

找到以以下開頭的部分：

    <Directory "/var/www/html">

將配置從AllowOverride None改為：

    AllowOverride All

最後，重啟服務器：

    sudo systemctl restart httpd

做完這些，所有頁面都應該可以正常顯示。

  • 1 min read

Fixing Endless Redirection with HTTPS Settings in WordPress When Using AWS Load Balancer

Problem

I set up a WordPress blog on two Amazon Web Services (AWS) EC2 instances located in different availability zones. In front of these instances, an Elastic Load Balancer (ELB) is configured to redirect all HTTP requests on port 80 to HTTPS on port 443. Since the wp-config.php file was not updated to reflect this change, the requests were still using HTTP. To correct this, I updated the following values to use HTTPS:

    define('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] . '/');
    define('WP_HOME', 'https://' . $_SERVER['HTTP_HOST'] . '/');

However, this led to an endless redirection loop, eventually resulting in an error stating "too many redirections."

Solution

To resolve the issue, add the following line to the wp-config.php file:

    $_SERVER['HTTPS'] = 'on';

This will fix the issue. Configurations like this can be challenging to troubleshoot, and you may spend many hours looking for a simple solution. Hopefully, this post will save you some time if you encounter this particular issue.

  • in podcast
  • 2 min read

Fixing Endless Redirection with HTTPS Settings in WordPress When Using AWS Load Balancer

Hello, and welcome to another episode of Continuous Improvement. I'm your host, Victor. Today, we're going to discuss a common issue that many WordPress users face when setting up their websites on AWS EC2 instances. Specifically, we'll dive into the problem of endless redirection loops and how to fix them. So, let's get started!

Imagine this. You set up your WordPress blog on two AWS EC2 instances located in different availability zones. To manage the traffic, you wisely configure an Elastic Load Balancer (ELB) to redirect all HTTP requests to HTTPS. However, you encounter a roadblock when your requests keep looping endlessly, resulting in an error stating "too many redirections." Frustrating, right?

Luckily, there's a simple solution to this problem. Let me walk you through it step by step. Here's what you need to do.

First, open up your wp-config.php file. This file holds important configurations for your WordPress website. Look for the following lines of code:

define('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] . '/');
define('WP_HOME', 'https://' . $_SERVER['HTTP_HOST'] . '/');

You'll notice that these lines specify the WP_SITEURL and WP_HOME values using HTTPS. While this seems like the correct approach, it actually creates the endless redirection loop that we're trying to solve.

So, here's the fix. Add the following line to your wp-config.php file:

$_SERVER['HTTPS'] = 'on';

By adding this line, you're explicitly telling WordPress that HTTPS is enabled. This bypasses the endless redirection loop issue and ensures a smooth user experience.

And there you have it! A simple solution to a potentially frustrating problem. Configurations like these can be challenging to troubleshoot, and you might spend hours searching for a solution. But with this fix, you'll save valuable time and get your website up and running smoothly.

I hope you found this episode helpful. If you have any other WordPress-related issues or questions, feel free to reach out to me on our podcast's website or social media channels. Remember, continuous improvement is all about learning, growing, and overcoming challenges one step at a time.

Thank you for listening to Continuous Improvement. I'm your host, Victor, signing off. Stay curious, keep improving, and until next time!

  • in zh
  • 1 min read

使用AWS負載平衡器時，透過HTTPS設定修復WordPress的無盡重定向

問題

我在兩個位於不同可用性區域的Amazon Web Services (AWS) EC2實例上設置了一個WordPress博客。在這些實例前，配置了一個Elastic負載平衡器 (ELB)，以將所有在80端口的HTTP請求重定向到443端口的HTTPS。由於wp-config.php文件未更新以反映此變更，請求仍在使用HTTP。為了糾正這個，我更新了以下值以使用HTTPS：

    define('WP_SITEURL', 'https://' . $_SERVER['HTTP_HOST'] . '/');
    define('WP_HOME', 'https://' . $_SERVER['HTTP_HOST'] . '/');

然而，這導致了一個無窮的重定向循環，最終導致一個錯誤，說明"重定向太多次"。

解決方案

要解決這個問題，需要在wp-config.php文件中添加以下行：

    $_SERVER['HTTPS'] = 'on';

這將修復此問題。這樣的配置可能難以排除故障，您可能會花費很多時間尋找一個簡單的解決方案。希望這篇文章能為您節省一些時間，如果您遇到這個特殊問題。

  • 1 min read

Installing PHP 7.2 Instead of PHP 5.4 on Amazon Linux 2

Problem

When you launch a new Amazon Linux 2 AMI server and try to install PHP using the following command:

yum install php

After a successful installation, if you check the version using php -v, you'll see:

PHP 5.4.16 (cli) (built: Oct 31 2019 18:34:05)

However, the latest PHP version is 7.2, and you may want to use this newer version instead.

Solution

You can enable PHP 7.2 via Amazon Linux Extras with the following command:

sudo amazon-linux-extras enable php7.2

Once it is enabled, follow the subsequent instructions to complete the installation:

yum clean metadata
yum install php-cli php-pdo php-fpm php-json php-mysqlnd

That's it. Check the PHP version again using php -v, and it should now display:

PHP 7.2.28 (cli) (built: Mar 2 2020 19:38:11) ( NTS )
  • in podcast
  • 2 min read

Installing PHP 7.2 Instead of PHP 5.4 on Amazon Linux 2

Hello everyone, and welcome to another episode of Continuous Improvement, the podcast where we explore different solutions to common problems in the tech world. I'm your host, Victor. In today's episode, we'll be talking about a common issue that many of us face when setting up an Amazon Linux 2 AMI server and trying to install PHP.

And we're back. So, imagine this: you've just launched a brand new Amazon Linux 2 AMI server, and you're excited to get started. But as you try to install PHP using the usual command yum install php, there seems to be a problem. The version it installs is PHP 5.4.16, and you realize that the latest version is PHP 7.2. What do you do?

Well, fear not! There is a solution to this dilemma. You can enable PHP 7.2 via Amazon Linux Extras. Let me walk you through it.

First, open up your terminal and run the following command with sudo privileges:

sudo amazon-linux-extras enable php7.2

This command will enable PHP 7.2 through the Amazon Linux Extras. Once it's enabled, we can proceed with the installation.

But hold on, there's one more step before we install PHP 7.2. We need to clean the metadata. Run the following command:

yum clean metadata

This will ensure that we have the most up-to-date information for the installation process. Now, we can finally install PHP 7.2 along with some additional packages that we'll need. Run this command:

yum install php-cli php-pdo php-fpm php-json php-mysqlnd

And that's it! You've successfully installed PHP 7.2 on your Amazon Linux 2 AMI server. To double-check, run php -v in your terminal, and you should see something like this:

PHP 7.2.28 (cli) (built: Mar 2 2020 19:38:11) ( NTS )

And there you have it, a step-by-step solution to upgrade your PHP version on an Amazon Linux 2 AMI server. Remember, keeping your software up to date is essential for security and performance reasons.

Thank you for tuning in to this episode of Continuous Improvement. If you found this information helpful, please consider subscribing to our podcast and leaving us a review. If you have any suggestions for future topics or questions, feel free to reach out to us on our website or social media channels.

Until next time, I'm Victor, your host, signing off.