502 Bad Gateway while indexing.

[sajal]

We're trying to index the content (XF 1.5) on our site with this plugin. Out site is hosted at AWS. I keep getting 502 bad gateway errors while indexing from the admin side. We've set nginx timeout 3600 seconds.

Also, a couple of times I can resume the uncompleted deferred processes from the dashboard. But, after that, even I can't do that, and thus not able to complete the indexing process.

I tried to check php error logs, admin side server logs, but nothing related to this.

Any thoughts greatly appreciated.

 

[djbaxter]

See if this helps:

How to Solve 502 Bad Gateway Issues? - KeyCDN Support

Having issues with a 502 Bad Gateway error? This guide gives you practical tips to solve origin not reachable problems.

www.keycdn.com

How Can I Solve 502 Error Bad Gateway from Cloudflare? - Interserver Tips

502 Bad Gateway means our network is not able to connect with your server for communication. The 502 Bad Gateway error is an HTTP status code which indicate

www.interserver.net

 

[sajal]

Thanks @djbaxter I'll check if that helps.

 

[duderuud]

Also no backend server errors?

 

[sajal]

@duderuud We sorted out this by setting a new domain only for admin side, and bypassing CloudFlare altogether.