Getting 504 timeout error updated the plugins but still showing application timed out error
Had a chat with pantheon suupport team they have been telling there is slow performance issues with the plugin [0x00007f1fd4816a00] is_file() /code/wp-admin/includes/class-wp-filesystem-direct.php:418
[0x00007f1fd4816980] is_file() /code/wp-content/plugins/wpml-string-translation/classes/translation-files/Manager.php:90
[0x00007f1fd48168f0] get() /code/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTextDomain.php:105
[0x00007f1fd4816850] loadCustomMOFile() /code/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTextDomain.php:70
Our developer worked on this issue, but the problem still persists. They found this post (https://wpml.org/forums/topic/504-gateway-time-out-nginx/), which suggests changing the WordPress theme to the default to troubleshoot, which we are very reluctant to do.
Below are the steps they have taken and the error they are seeing. Could you please advise?
1.) The plugin has been updated, and no issues have been seen on the development site.
2.) We blocked two abusive IP addresses: 52.58.146.230 and 47.76.35.19 that were hitting the website repeatedly
3.) They have followed the below steps:
a. - Just to be safe, make sure to have a website backup before proceeding
- Go to WPML -> Support in your admin dashboard
- Click the \"troubleshooting\" link below the plugin versions list
- Look for the \"Clean up\" section and hit these buttons:
# Clear the cache in WPML
# Remove ghost entries from the translation tables
# Fix element_type collation
# Synchronize local job ids with ATE jobs
# Synchronize translators and translation managers with ATE
# Set language information
# Fix post type assignment for translations
I’m sorry that you ran into trouble with this! I’ll need a little more information to see what’s happening here.
Am I correctly understanding that the problem is not occurring on the development site?
I recommend updating WordPress to the latest version and ensuring that the MySQL version meets the minimum requirements. You can find more information on this topic by visiting https://wordpress.org/about/requirements/.
If the issue still persists, I suggest temporarily deactivating all non-WPML plugins and testing the site again.
Before proceeding with any changes, please make sure to back up your database first.
Hi - Our developer confirmed that our site is using the below versions of WordPress/MySQL:
• WordPress version: 6.1.1
• Mysql verion: 10.4.25-MariaDB-log
Do the above versions meet WMPL's requirements? Is there anything you can recommend other than updating WordPress?
Updating WordPress may not necessarily resolve your problem. However, to troubleshoot the issue best, we need to work on the latest available code. Another step is to temporarily deactivate all plugins except WPML to check the issue.
Could you please move forward with the troubleshooting without updating WordPress or temporarily deactivating all plugins except WPML? Due to the high level of customization on our site, these options are not practical and will either cost too much or carry the risk of breaking multiple points of functionality.
I suggest creating a testing site where you can move your live site and perform some tests to identify the issue. It is possible that the problem may not occur on the latest version of WordPress. Customizing WordPress core files is not recommended.
After setting up a staging site, you can perform additional troubleshooting steps to resolve the issue.
Thank you for helping with this. Our developers have a staging site already set up. Could you list the next troubleshooting steps so I can share the steps with them?
Thank you. Please see this post in this thread from December 8:
Our developer worked on this issue, but the problem still persists. They found this post (https://wpml.org/forums/topic/504-gateway-time-out-nginx/), which suggests changing the WordPress theme to the default to troubleshoot, which we are very reluctant to do.
Below are the steps they have taken and the error they are seeing. Could you please advise?
1.) The plugin has been updated, and no issues have been seen on the development site.
2.) We blocked two abusive IP addresses: 52.58.146.230 and 47.76.35.19 that were hitting the website repeatedly
3.) They have followed the below steps:
a. - Just to be safe, make sure to have a website backup before proceeding
- Go to WPML -> Support in your admin dashboard
- Click the \"troubleshooting\" link below the plugin versions list
- Look for the \"Clean up\" section and hit these buttons:
# Clear the cache in WPML
# Remove ghost entries from the translation tables
# Fix element_type collation
# Synchronize local job ids with ATE jobs
# Synchronize translators and translation managers with ATE
# Set language information
# Fix post type assignment for translations
