Home›Support›English Support›[Resolved] Getting a bad gateway error when reviewing some of the pages after using the "WPML Multilingual CMS...
[Resolved] Getting a bad gateway error when reviewing some of the pages after using the "WPML Multilingual CMS...
This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing bad gateway errors on specific pages when the WPML Multilingual CMS plugin is activated, particularly when switching languages from French to English. The issue seems to arise due to a conflict between WPML and Elementor Pro plugins. Solution: We recommend the following steps to resolve the issue: 1. Deactivate all non-WPML plugins and switch to a standard WordPress theme to check if the problem persists. Remember to back up your database and website before proceeding. 2. If the error continues, enable the WP debug log, revisit the problematic page, and share the log file with us for further analysis. You can find guidance on enabling the WP debug log here: WordPress Debug Documentation. 3. As a temporary workaround, you can go to WPML > Translations and approve translations in bulk, then adjust the settings in WPML > Settings > Automatic translation to 'Publish right away without reviewing' to avoid reviewing translations that might trigger the error.
If these steps do not resolve the issue or if the solution becomes outdated, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
The 502 error is, by definition, a server error. That means that it's an error that occurs on the server level. Check the screenshot you sent last, the Browser and Cloudflare show a success message, while your server shows an error.
I'm on a 500Mbps network, using Chrome with a VPN. When I checked the specific "Types of Shielding" page, both in my phone and on my PC, I was able to see the issue. It's likely that the issue doesn't depend on the device/browser.
Please reach out to your hosting provider, explain the error you are having and ask them for further information (an error log or any additional details that can give us some insights). Your server might lack the proper resources for your website to work flawlessly.
Of course, we'll keep supporting you, but we'll need assistance from your hosting provider. Please let me know what they answer.
I spoke with WP Engine for quite a while, they did testing on their side and determined it's a coding issue with one of the plugins. We switched this staging site to their legacy network in order to by pass Cloudflare to get a bit more info about the 502 error. It doesn't give much detail but does show a legit 502 browser error vs a very general error from the middle man Cloudflare. You now see the the staging site URL is hidden link which uses their legacy network. Please review the message below from WP Engine and let me know your thoughts.
From WP Engine:
We were able to replicate the issue and each time we did we saw a segmentation fault log in our server log error logs. These are logged elsewhere then the environments error logs I apologize.
104.182.31.9 npoeustg.wpenginepowered.com - [18/Jul/2024:16:12:54 +0000] "GET /types-of-shielding/ HTTP/1.0" 502 1175 "hidden link" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36"
104.182.31.9 npoeustg.wpenginepowered.com - [18/Jul/2024:16:13:12 +0000] "GET /types-of-shielding/ HTTP/1.0" 502 1175 "hidden link" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36"
This type of error is a issue that is stemming from the code base of the site as opposed to a serverside issue. The error by itself doesn't tell us what part of the site is breaking unfortunately. This is something that usually requires toggling plugins and themes to narrow down which plugin or themes are contributing to the issue. Then once that is done I would reach out to the support team for the plugin or theme contributing to the issue for more info.
I hope this helps! If you have any other questions feel free to hop back into phone/chat and reference this ticket number.
Since the site is on a shared WPE server, I copied the site to my dedicated server at WPE to make sure it's not a performance issue on the server side. My dedicated server has a ton of horsepower a should be able to handle this site without a problem.
The URL is: hidden link
I left it on their advanced network
It's using the latest WP 6.5.5
After a few minutes of navigating it produced the same bad gateway error as the original staging site.
I downloaded the dubug.log file so you can take a look.
Thank you for sharing the details. In this situation, we will probably have to escalate your issue to our developers. I'll get a second opinion with Long, he'll answer you here as soon as possible.
Again, I understand this is a time urgent matter. It doesn't look like an issue caused by the user, you can send him the link to the ticket, to check that we are working with you on it, and that this is not an issue caused by you.
I test the issue again on your new staging site with 4 browsers: Chrome, Opera, Firefox, Safari but again, I still don't see the issue. Here is the screen record hidden link
I also copy your site to my local site and check the server log but don't see any useful information because the 502 error doesn't occur there.
Regarding the PHP deprecated message in the WP debug log, it shouldn't cause the issue on your site.
Regarding the feedback from the hosting support, you can try to enable a minimal environment as below and observe the issue again:
- Deactivate all non-WPML plugins.
- Switch to a WordPress theme.
Meanwhile, I'm discussing this issue with our 2nd tier support and I will update you here when I have something to share.
After trying a lot of steps, I can replicate the issue on your staging site:
1. Go to admin WPML > Translations > Review the translation page.
2. Click on the language switcher at the footer/header.
3. You will view the translation page in the frontend > Switch to English language > The error occurs.
I also try these steps on my local site but the issue doesn't occur there. This is a server issue without any error log that indicates where it comes from, it really difficult to debug this so we suggest you go to WPML > Translations > Approve translations in bulk. You can review the translation in the Advanced Translation Editor later.
And go to WPML > Settings > Automatic translation > Select option "Publish right away without reviewing" to not review the translation and prevent this issue.
I followed the steps you recommended, I approved all the translations in bulk and then selected the option "Publish right away without reviewing" under settings.
Can you confirm I completed those steps correctly and that you are not able to reproduce the error on your end?
