PREVENT YOUR SERVER FROM CRASHING Never again lose customers to poor server speed Let us help you. Today, we’ve seen the top causes for the error and how our Support Engineers fix them. Reset the default settings for your browser. CentOS Web Panel error 503 backend fetch failed happens mainly due to memory allocation issues or bad varnish cache configuration. Go to Varnish configuration file ( /etc/varnish/default.vcl) and find these lines. Close a few of the open tabs in the browser if there are many, then try loading the website again. In Magento 2, already set root path to /pub => wrong path in varnish configuration file. This usually happens even with a fresh installation of Magento 2 (frequently reported in Magento 2.3)īy default, the path to health_check.php file in varnish is /pub/health_check.php. The other possibility that caused 503 error is wrong health_check.php file location in varnish configuration file. Wrong health_check.php location in Varnish config file It should be like this after you make changeįinally, save file and restart Magento 2 server to apply changes. To larger value (for example, 70000 bytes should work well for 3000 products) -p http_resp_hdr_len=70000 \Īlso, change http_resp_size (Maximum number of bytes of HTTP backend response) to the value that fit the increased value of http_resp_hdr_len, for example 10000 http_resp_size should be good with 70000 http_resp_hdr_len -p http_resp_size=100000 \ The path to varnish configuration file isĮdit the file with a text editor and change the http_resp_hdr_len value (located in line 101 after thread_pool_max ) -p http_resp_hdr_len=8192 \ (Maximum length of any HTTP backend response header – read here for more detail) If you receive this error message, it indicates that the server is malfunctioning and cannot respond appropriately. The generic message of the 503 error is Service Unavailable, and there are some other 503 responses, such as the topic of today’s article backend fetch failed. We will change http_resp_hdr_len value in Varnish configuration file. You might be very familiar with the error 503 which commonly occurs when you are visiting webpages on your browsers. (safe http_resp_hdr_len value = product number multiplied by 21) The default value of Varnish is 8192 bytes, which mean it is only stable for a store with less than 400 products. If your store has a large number of products (more than 400), the error may happen because the length of cache tags used by Magento 2 exceed the default value of Varnish. Length of cache tags used by Magento exceed Varnish’s default value Note: In case you see the error message: Error 503 service temporarily unavailable, read this tutorial to learn how to fix it => How to fix Magento 2 Error 503 service temporarily unavailable Possible causes of the error and solution 1. In this series of tutorials on fixing Magento 2 issues, I will guide you all the possible causes of the error and of course, the solution to resolve the error. One of the most common error that Magento 2 user encounter is 503 Backend fetch failed with varnish cache However, due to its complexity, there are many type of error may occur when working with Magento. Magento 2 comes with many complicated features which makes it one of the most powerful open source Ecommerce platform at the moment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |