After upgraded to 2.4.6 from 2.3.4 in admin while saving CMS page, we are getting 504 timed outerror

[mohamed maideen]

Hello,

Recently we upgraded Magento from 2.3.4 to 2.4.6, after that, we facing some performance fluctuation, some times site is fast and some site is slow, if we are performing any admin operations, that site is very slow, we could not able to edit/save the CMS pages, we are getting 504 error

[toniagency82ed]

You'll need an experienced team to take a look at your logs and codebase and figure out what is causing these issues. Nobody can know what the issue is based solely on the description of the issue you provided.

If you need professional help with that, feel free to contact us.

[zoyascootg16c3]

@mohamed maideen 

A 504 Gateway Timeout error typically occurs when a web server doesn't receive a timely response from another server, such as a database server or an API server. In the context of upgrading Magento from version 2.3.4 to 2.4.6, there are several potential reasons for encountering this issue during CMS page save operations in the admin panel.

Here are some steps you can take to troubleshoot and resolve the 504 Gateway Timeout error:

1. Check Server Resources

2. Verify PHP Configuration
3. Check the Magento logs
4. Clear cache

[pickleball07d4]

Facing a 504 Gateway Timeout error after upgrading Magento can be frustrating, but it's a common issue that can be resolved by optimizing your server and configuration. Here are some steps to help you troubleshoot and fix this issue:

1. Check Server Resources:

   • Ensure that your server has enough resources (CPU, memory, disk space) to handle the increased demands of Magento 2.4.6. Upgrading to a higher-tier hosting plan or server may be necessary.

2. PHP Version and Configuration:

   • Make sure you're using a compatible PHP version with Magento 2.4.6. Check the official Magento 2.4.6 system requirements for the recommended PHP version and settings.
   • Verify that PHP's max_execution_time and max_input_time are set to a value that allows Magento to perform its operations without timing out.
   • Increase PHP's memory_limit to a value suitable for your store's size and complexity.

3. Web Server Configuration:

   • Adjust your web server (e.g., Apache, Nginx) settings to handle Magento's requirements, including increasing the maximum execution time and adjusting timeouts.

4. PHP OPcache:

   • Ensure that PHP OPcache is enabled and properly configured. OPcache can significantly improve Magento's performance.

5. Varnish or Full-Page Cache:

   • If you use Varnish or another full-page cache, verify that it's configured correctly for Magento 2.4.6.

6. Magento Configuration:

   • Review your Magento configuration, including cache settings and indexing. Make sure everything is properly configured and up to date.
   • Clear the cache and reindex if needed.

7. Extensions and Custom Code:

   • Check if any third-party extensions or custom code are causing conflicts or performance issues. Disable or update them as necessary.

8. Logging and Monitoring:

   • Set up proper logging and monitoring to identify the root cause of the performance issues. Tools like New Relic or DataDog can be helpful for tracking down bottlenecks.

9. Content Delivery Network (CDN):

   • Consider using a CDN to offload static assets and reduce server load.

10. Database Optimization:

    • Optimize your database by running tools like MySQLtuner to identify and address performance issues.

11. Server-Level Caching:

    • Implement server-level caching mechanisms like Redis or Memcached to speed up data retrieval.

12. Upgrade Scripts and Patches:

    • Ensure that all necessary upgrade scripts and patches for Magento 2.4.6 are applied correctly.

13. Performance Testing:

    • Perform load testing on your website to identify potential bottlenecks and areas of improvement.

14. Consult Magento Experts:

    • If the issue persists and you're unable to identify the root cause, consider hiring Magento experts or contacting Magento support for assistance.

It's important to approach these troubleshooting steps methodically and consider seeking professional assistance if needed, as server and performance optimization can be complex tasks.

Hicham 
https://pickleballassociationofontario.org/contact

[rimshadevr27ac]

There are a few things I would recommend checking to address the performance fluctuations and 504 errors after upgrading Magento from 2.3.4 to 2.4.6:

• Review Magento system requirements and ensure your server meets the increased needs for v2.4.6, especially around PHP, memory allocation, and other configuration settings.
• Check for any excessive logging or debug settings still enabled that could impact performance. Disable anything not needed on a production site.
• Clear caches and reindex to ensure cached data isn't outdated after the upgrade.
• Enable Redis or Varnish cache if not already in place to improve page load speeds.
• Check for third party module compatibility issues and disable/upgrade any not yet optimized for v2.4.6.
• Review server resources during peak usage times. The upgrade may necessitate allocating more CPU, memory to handle the Magento workload.
• Configure a CDN to offload serving of static assets and media for boosted performance.
• Review database indexes and queries for any outlier slow queries under load.
• Tune your MySQL config for efficiency gains with Magento specific optimizations.
• Check for any custom code issues that could be slowing requests and causing timeouts.

With tuning at the server, network, database, and application level you should be able to smooth out performance after the sizable version jump.

[konstantina904]

I'd suggesting adding a code profiler to see what's going on. Try New Relic or Tideways (free the first 14 days or so). It will tell you what's slow.

[Milople]

Hello @mohamed maideen,

A 504 Gateway Timeout error typically occurs when the server, acting as a gateway or proxy, did not receive a timely response from an upstream server. This can happen for various reasons, including server misconfiguration, resource exhaustion, or slow script execution.

Here are some steps you can take to troubleshoot and resolve the 504 Gateway Timeout error when saving CMS pages in the Magento 2.4.6 admin panel:

• Check Server Resources: Ensure that your server has sufficient resources (CPU, memory, disk space) to handle the request. Check server logs for any resource exhaustion or errors.
• PHP Configuration: Review your PHP configuration settings such as max_execution_time, memory_limit, and post_max_size. These settings can affect the time and resources allocated for script execution and file uploads. Adjust them as needed to accommodate the size and complexity of your CMS pages.
• Magento Configuration: Verify that your Magento configuration is optimized for performance. Check settings related to caching, indexing, and compilation. Rebuild indexes if necessary.
• Check for Long-running Processes: Identify any long-running processes or database queries that may be causing the timeout. Use profiling tools or Magento's built-in logging to track down slow queries or code paths.

If you have any question please contact us.

If the issue will be resolved, Click Kudos & Accept as a Solution.