If you are search on google 500 internal server error problem solution then you have come to the right blog. Causes of blog access drastically reduced | What is a 500 internal server error problem? What are the countermeasures and preventive measures?
We often get consultations about blog access being reduced. In addition, access to the main site that I have been operating since 2015 has dropped dramatically in the second half of February 2019. The loss of access to blogs, which are important sources of income, is a matter of life and death for those who are dedicated to blogs. In this article, we will introduce how to deal with and prevent server errors that may have caused the blog access drastically.
1. Server error is the cause of drastic decrease in blog access? Even though my main site didn't update much until January 2019, the past article was replaced by an explosion that replaced and earned quite a lot. However, there was a significant decrease in access around February 15, 2019. It was a little later that there was a big Google update, so I thought the update wasn't the direct cause. Half the number of page views per day. I was wondering why there was a sudden drop in access, but remembered that there was error information in Google's Search Console before, and I checked it.
2. What is "500 server error"? As confirmed in March 2019, the server error occurred in October 2018. At that time there was no particular effect, so I left it alone, but the error display disappeared. But just in case, check the "error log" of the X server that runs the blog. There was a spectacular sight ... There were over 3000 errors per day. This is the error content [Thu Mar 14 05: 14: 09.522159 2019] [fcgid: warn] [pid 347931] (104) Connection reset by peer: [client 180.29.66.37:44152] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https: // ~~~ 1 [Thu Mar 14 05: 14: 09.522159 2019] [fcgid: warn] [pid 347931] (104) Connection reset by peer: [client 180.29.66.37:44152] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https: // ~~~ This is an error that occurs when the server is under heavy load. When this happens, the following screen appears to the accessing user. ↓ 500 internal server error screen
A similar screen appears when many accesses are concentrated, but there is a slight difference. ↓ 503 error screen The 503 error is temporary due to concentration of access, and the 500 error is caused by some technical problem that causes high load.
3. What is the “500 server error” solution? If server errors are the cause of drastic drop in access, I want to do something quickly. I was very impatient and looked for a countermeasure. The quickest way is to remove the plug-in. I stopped and removed all plug-ins that I didn't use immediately and those that weren't so important even if I used them. A few days later, when I checked the error log again, the error log that was 3000 or more is 1000 or less. There was a certain effect. Then, I decided to delete more plug-ins, changed my policy to do as much as possible without plug-ins, and decided to shape up the plug-ins. The main site has used more than 50 plug-ins so far, leaving only the minimum necessary and reducing it to a total of 8. Check the error log again. This is around 100. Eventually, server errors have decreased considerably, but not zero. It would be enough to reduce thousands to tens. What about access? Reduced server errors but did not return access as a result. Of course, once access has been reduced, it won't come back so easily.
4. What are the precautions to prevent the “500 server error” from occurring? Even if you have never received a 500 server error warning, you may have a variety of errors when you check the "error log" of the rental server. It is good to check once. Even if nothing appears in the error log, it is necessary to prevent it from appearing in the future. The preventive measure is to “reduce plug-ins as much as possible”, which had a certain effect this time. There seems to be a technical method such as “checking the description of PHP”, but it is difficult for the main person to create content like me every day and it is not recommended because it takes a lot of time. If you are worried about the technical aspects of it, I think it would be better to look for someone who will check php with “Konara” and ask for improvement. ↓ Coconara service search screen
The cost is probably much cheaper than searching on the net and asking the contractor. Click here for Coconut. Because you can ask only what you need without spending money, KokoNara is a service that allows you to find a very good person. So this time, we introduced how to deal with server errors and preventive measures that caused the drop in blog access. Note that WordPress plugins are convenient and easy to install, but can be heavy and cause server errors. Measures to drastically reduce access will continue. In the next article, we will examine the new drastic drop in access and its causes. Thank you for watching to the end.
1. Server error is the cause of drastic decrease in blog access? Even though my main site didn't update much until January 2019, the past article was replaced by an explosion that replaced and earned quite a lot. However, there was a significant decrease in access around February 15, 2019. It was a little later that there was a big Google update, so I thought the update wasn't the direct cause. Half the number of page views per day. I was wondering why there was a sudden drop in access, but remembered that there was error information in Google's Search Console before, and I checked it.
2. What is "500 server error"? As confirmed in March 2019, the server error occurred in October 2018. At that time there was no particular effect, so I left it alone, but the error display disappeared. But just in case, check the "error log" of the X server that runs the blog. There was a spectacular sight ... There were over 3000 errors per day. This is the error content [Thu Mar 14 05: 14: 09.522159 2019] [fcgid: warn] [pid 347931] (104) Connection reset by peer: [client 180.29.66.37:44152] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https: // ~~~ 1 [Thu Mar 14 05: 14: 09.522159 2019] [fcgid: warn] [pid 347931] (104) Connection reset by peer: [client 180.29.66.37:44152] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https: // ~~~ This is an error that occurs when the server is under heavy load. When this happens, the following screen appears to the accessing user. ↓ 500 internal server error screen
A similar screen appears when many accesses are concentrated, but there is a slight difference. ↓ 503 error screen The 503 error is temporary due to concentration of access, and the 500 error is caused by some technical problem that causes high load.
3. What is the “500 server error” solution? If server errors are the cause of drastic drop in access, I want to do something quickly. I was very impatient and looked for a countermeasure. The quickest way is to remove the plug-in. I stopped and removed all plug-ins that I didn't use immediately and those that weren't so important even if I used them. A few days later, when I checked the error log again, the error log that was 3000 or more is 1000 or less. There was a certain effect. Then, I decided to delete more plug-ins, changed my policy to do as much as possible without plug-ins, and decided to shape up the plug-ins. The main site has used more than 50 plug-ins so far, leaving only the minimum necessary and reducing it to a total of 8. Check the error log again. This is around 100. Eventually, server errors have decreased considerably, but not zero. It would be enough to reduce thousands to tens. What about access? Reduced server errors but did not return access as a result. Of course, once access has been reduced, it won't come back so easily.
4. What are the precautions to prevent the “500 server error” from occurring? Even if you have never received a 500 server error warning, you may have a variety of errors when you check the "error log" of the rental server. It is good to check once. Even if nothing appears in the error log, it is necessary to prevent it from appearing in the future. The preventive measure is to “reduce plug-ins as much as possible”, which had a certain effect this time. There seems to be a technical method such as “checking the description of PHP”, but it is difficult for the main person to create content like me every day and it is not recommended because it takes a lot of time. If you are worried about the technical aspects of it, I think it would be better to look for someone who will check php with “Konara” and ask for improvement. ↓ Coconara service search screen
The cost is probably much cheaper than searching on the net and asking the contractor. Click here for Coconut. Because you can ask only what you need without spending money, KokoNara is a service that allows you to find a very good person. So this time, we introduced how to deal with server errors and preventive measures that caused the drop in blog access. Note that WordPress plugins are convenient and easy to install, but can be heavy and cause server errors. Measures to drastically reduce access will continue. In the next article, we will examine the new drastic drop in access and its causes. Thank you for watching to the end.
0 Response to "500 internal server error problem solution "
Post a Comment
WELCOME to https://www.googleadsensesafetips44.tk/.