Error 502 after editing a single post

Hi Morgan,

My host (Big Scoots) says its the Generate Premium/Generate Blocks plugin.

I doubt that but I could be wrong.

Can you disable those two plugins and see if that fixes the issue?

Yes, when I disable the plugins the site returns, albeit with a broken theme (obviously)

Can you narrow it down to which plugin? Is it GenerateBlocks or GP premium?

It's Generate Blocks

Hi there,

Can you try addressing this issue first? To see if its related.
https://share.getcloudapp.com/v1ubmqpN

Let us know.

What error is that? I’m not sure I understand what you are telling me to fix? I see the screenshot but am confused apologies

Oh I see, OneSignal is just throwing that error because its on a staging site not the live, I've disabled OneSignal, issue remains.

I've also uninstalled and reinstalled GenerateBlocks. Every time it's activated the site throws a 502.I would be happy just to pay someone to fix this for me, if there's truly premium support available beyond this forum. Time is money. But I do want to know what happened, if this theme is unstable.

Would it have anything to do with the fact that my license is for morganoverholt.com and not the staging site url? Although, it was working fine for an entire week.

Hi there,

can you disable the OneSignal on the Staging site as its complaining that the URL is not the correct origin. Once we got that out of the way we can take a look at the editing post issue.

Already done

To be clear, the issue is that when I have the Generate Blocks plug-in activated, the site throws a 502. When I deactivate it, the formatting breaks. That’s the issue, to be clear.

Do you have any re-usable blocks on the site? We've seen some issues with WordPress 5.7 and re-usable blocks causing infinite loops, which can increase memory usage.

Deactivating GenerateBlocks can "fix" that memory issue as it does contribute to overall memory usage, but it's likely that something else is using up the bulk of the available memory.

If you deactivate everything except GenerateBlocks, is the error still there?

If so, we'll need some more information from Big Scoots. Any errors in the error_log file mentioning specific functions etc...

GenerateBlocks itself is being used on 30,000+ active websites at the moment, including this one, so the issue you're facing is likely a conflict of some sort with Big Scoots.

Yes I do use re-usable blocks! And that was what I was doing when it crashed. How do I fix the memory issue if I promise to never use re-usable blocks again?

And correct, I have determined that GenerateBlocks is specially the problem.

I will ask my host for the error log. What can I do about the memory/reusable blocks issue?

Is there any way I can log in using temporary admin login details and take a look at your re-usable blocks to see if anything stands out?