504 Error When Attempting to Index Content

the exact error is 504 gateway time out.

Any other errors showing up around the error log for the 504 Gateway entry?

Sounds like it’s simply taking too long to complete a request, as we do try to batch things together with multiple ajax requests over time, to help take care of longer overall queues.

How many posts are you trying to batch process? This would be a total coming from posts, pages, and any custom post types that aren’t excluded from search. At least assuming you’re working with the “Search Page” settings, and not Autocomplete.

Hi Michael,

Thanks for prompt response.

We are attempting to index over 1000+ posts, which include different Custom Post Types (CPTs). We are aware that our load balancer has a 60-second timeout limit, and it seems to be causing the connection to close due to the extended time required for indexing.

Is there a way to manage this situation better? We don’t mind if the sync process takes longer, as long as the content gets properly indexed in the end. Our primary goal is to use your plugin to index our content, and then move on to implementing Algolia Recommend.

If you have command line prompt access with your hosting, we have WP-CLI commands available for bulk indexing.

https://github.com/WebDevStudios/wp-search-with-algolia/wiki/WP-CLI

That said, we’re also looking into reported slowness that we think may be coming from some of the changes with version 2.6.0. We’re still investigating that part. May be worth reverting to 2.5.4 as an extra test.

Hey @kapvin We have just released version 2.6.1 today which should restore async speeds and functionality. We realize that we removed the async aspect with part of the 2.6.0 release. We have revised how we’re allowing to still have synchronous management for the person who originally requested it, but have the plugin default to the previous behavior in 2.5.4 and earlier.

Give it a download and try it out.

Hi @tw2113 i’ve a similar problem with woocommerce’s product sync. I receive this type of error:

“An error occurred:

502 Bad Gateway
Server Error

Web server received an invalid response while acting as a gateway or proxy server.

That’s what you can do”

Can you help me?

@faquini79 Is it happening every time? or is it perhaps just a temporary error?

In case it’s playing a part, have you upgraded to version 2.6.1 yet?

hi @tw2113 , thank you for your answer.

Yes, it happens every time from 1 week and I’ve last version 2.6.1

@faquini79

Couple things quick.

1. Can you start a fresh thread for your issue as while it’s similar, it’s definitely a different issue than what the OP had here. It’ll be best to get you your own dedicated thread
2. Can you try reverting back to 2.5.4 for the plugin version? You can get a copy of that version with https://downloads.www.ads-software.com/plugin/wp-search-with-algolia.2.5.4.zip

Ok @tw2113, I’ll do.