We’ve got an ongoing problem with a client running a pretty decent-sized site based mostly in Page Builder on Pantheon hosting. As an example, this page generates a 502 Error when I try to load it in Page Builder mode. http://www.imagejournal.org/read/visual-art/ Did create a separate server with updates in place and the same error gets thrown. http://test-image-journal.pantheon.io/read/visual-art/ I saw someone else get a similar error but they restarted nginx to solve which isn’t really an option with Pantheon, I don’t think. This site ran for quite a few months before this problem cropped up as well. Other than that I haven’t noticed/replicated the problems they’re having with other pages, but am trying to get more details. In the meantime, any ideas for troubleshooting this? Seen anything similar? (Happy to provide access to the admin, dev server/repo, whatever is useful if a support tech wants to take a closer look.)
Latest message from the client:
I’d like to follow up about the Page Builder issue. This has been ongoing for us, and everyone in the office who’s working on our website is experiencing it on every Page Builder page they edit. It’s really slowing us down in a big way and making us replicate our work.
Sometimes it simply gets stuck loading and freezes, and sometimes it shows us the “Error 502” page. But it’s been universal across all PageBuilder pages, all computers and browsers in the office. In fact, my colleagues are experiencing it as I type…
It often happens when we try to save/publish, and often simply when we click on a module to edit it. It is very, very rare that we’ve made edits to a Page Builder page without it freezing in the past few weeks.
In my unbiased opinion, I do not believe the issue is caused by BB. A 502 error is usually when something like a page or script takes to long to load and the request is killed by the server.
Therefore, is it possible for you to get all the server information, so we can take a closer look.
Another thing to try would be to enable the main BB theme and see if your clients encounter the issue. As on viewing the page source, I noticed quite a few custom scripts in the BB child theme, things like slick.js, paywall.js, etc.
If they do not encounter any issue using the main BB theme, then the problem is likely coming from the child theme. However, 502 errors are quite difficult to combat and some people actually call it an art.
OK, thanks for the response, Danny. I’ll gather together the server info for you — our sysadmin is saying he feels it looks like a PHP memory timeout and there’s not much that can be changed as far as the server config on Pantheon so we may try out the site outside of Pantheon to see if we can isolate the limiting factor more easily. Pantheon ought to be able to handle pretty demanding sites though, so I’m wondering if it is some instability I’ve introduced. Will try out what you’ve suggested with the theme.
It seems the PHP workers available were maxing out (128 available with Pantheon’s “Personal” tier) as a result of the combination of SearchWP’s indexing and BeaverBuilder, so we’ve upgraded to Professional tier and that seems (so far) to have solved the issue. Preliminary only so I’ll update here if more comes to light.