Saving the component dialogue resulting in a 502 error | Community
Skip to main content
R
Rajendra_
New Participant
April 5, 2022
Solved

Saving the component dialogue resulting in a 502 error

  • April 5, 2022
  • 1 reply
  • 696 views

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?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Ravi_Pampana

Hi,

 

Index might be corrupted, try re-running the index, we faced similar issue and re-running index fixed the issue. 

1 reply

Ravi_Pampana
Ravi_PampanaAccepted solution
New Participant
April 6, 2022

Hi,

 

Index might be corrupted, try re-running the index, we faced similar issue and re-running index fixed the issue. 

    Terms & ConditionsAccessibility statement

    Loading footer...