SOLVED
Saving the component dialogue resulting in a 502 error
We have an issue, where saving a component inside the XF. It's giving 502 bad gateway as request didn't go through at all. So, I'm trying to find why the requests are blocked.
Our AEM is running on the GCP so this issue started to occur after migration to GCP.
On one of the environment it gives 502 and on another one it takes too much but saves the dialog.
What possibly could be the reason here?
1 Accepted Solution
Correct answer by
Hi,
Index might be corrupted, try re-running the index, we faced similar issue and re-running index fixed the issue.
Correct answer by
Hi,
Index might be corrupted, try re-running the index, we faced similar issue and re-running index fixed the issue.
