Lucas Vidal de Andrade
WPML Supporter since 11/2023
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
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.
|
brianB-36
|
Thank you Lucas! I'm reaching out to WP Engine now and see what they can do. I'll keep you posted.
|
brianB-36
|
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.
[Thu Jul 18 16:12:47.135856 2024] [core:notice] [pid 12964] AH00052: child pid 29257 exit signal Segmentation fault (11)
[Thu Jul 18 16:12:55.151054 2024] [core:notice] [pid 12964] AH00052: child pid 8319 exit signal Segmentation fault (11)
[Thu Jul 18 16:13:17.233584 2024] [core:notice] [pid 12964] AH00052: child pid 9004 exit signal Segmentation fault (11)
These are the 502s we got around that time as well.
73.75.85.68 npoeustg.wpenginepowered.com - [18/Jul/2024:16:12:46 +0000] "GET /types-of-shielding/ HTTP/1.0" 502 1175 "hidden link" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) 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: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.
John C. | Technical Support Specialist
|
brianB-36
|
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.
hidden link
Let me know your thoughts on these errors.
Thanks!
Brian
|
Lucas Vidal de Andrade
WPML Supporter since 11/2023
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Portuguese (Brazil) (Português )
Timezone:
America/Sao_Paulo (GMT-03:00)
|
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.
We'll get back.
|
Long Nguyen
WPML Supporter since 02/2022
Languages:
English (English )
Timezone:
Asia/Ho_Chi_Minh (GMT+07:00)
|
Hi Brian,
Thanks for sharing more information.
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.
Thanks for your patience.
|
Long Nguyen
WPML Supporter since 02/2022
Languages:
English (English )
Timezone:
Asia/Ho_Chi_Minh (GMT+07:00)
|
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.
Looking forward to your reply.
Thanks
|
brianB-36
|
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?
|
Long Nguyen
WPML Supporter since 02/2022
Languages:
English (English )
Timezone:
Asia/Ho_Chi_Minh (GMT+07:00)
|
Hi,
Yes, on your new staging site hidden link
I approve all translation reviews in WPML > Translations and add the workaround code in the documentation to the file functions.php in the child theme folder.
https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
Now I cannot replicate the issue there, those pages can be viewed in both languages French and English.
If you still see that issue on your end, please take a screen record of this on the new staging site.
Looking forward to your reply.
Thanks
|
