Magento Forums
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Plesk hosted : Magento 1.7 Fcig timeout (524) mod_fcgi 110 timeout

‎02-11-2020 10:45 AM
‎02-11-2020 10:45 AM

Plesk hosted : Magento 1.7 Fcig timeout (524) mod_fcgi 110 timeout

Hello,

 

Site is doing well except for login phase.

Some users can stay loged in, but some can't login issueing in 524 Gateway and fcgi timeout.

 

I've seen so many posts, couldn't find a fix.

I guess it's mod_fcig who is doing bad.


How to properly solve this ? Files permissions ? .htaccess ? php config files ?


Facts :

 

/var/session/ is just extremly huge, like not ok.

Php 7.0 / php-fastcgi with nginx proxy (plesk)


 

0 Kudos
Reply
1 REPLY 1
‎02-17-2023 11:47 PM
‎02-17-2023 11:47 PM

Re: Plesk hosted : Magento 1.7 Fcig timeout (524) mod_fcgi 110 timeout

The 524 Gateway Timeout error typically occurs when a server takes too long to respond to a request from a client. This can happen for a number of reasons, including slow database queries, slow PHP code, or overloaded server resources.

Here are a few steps you can take to try and resolve the issue:

  1. Increase the timeout limit in your server configuration: You can increase the timeout limit for your server by modifying the "timeout" parameter in your server's configuration file. In Plesk, this file is typically located at /etc/nginx/nginx.conf.

  2. Check the PHP configuration: Make sure that the PHP configuration is optimized for your website. You can check the PHP configuration in Plesk by going to "Domains > example.com > PHP Settings".

  3. Check your database: Slow database queries can cause the site to hang and lead to timeouts. You can optimize your database by running queries to delete unwanted data or optimize indexes.

  4. Clear your Magento cache: Clear your Magento cache by deleting the files in the /var/cache/ folder. You can also try disabling the cache to see if that resolves the issue.

  5. Check server resource usage: Check the resource usage on your server to ensure that the CPU and memory are not being overloaded. You can check this in Plesk by going to "Tools & Settings > Resources".

  6. Check the server logs: Check the server logs for any error messages or warnings that might help you diagnose the issue. You can find the logs in Plesk by going to "Domains > example.com > Logs".

I hope these tips help you resolve the issue.

0 Kudos
Reply