Hal

I have increased php memory limit to 512 and timeout to 600. It runs much longer now and deletes some users. But I get an nginx 504 timeout error now. Any ideas?

I increased timeout to 90 seconds, and memory to 256M, and that did not help. It seemed to run longer, but very few users were actually deleted, if any.

Sure, max_execution_time is 30 seconds, memory_limit is 128M. I will increase those and try again, thx.

sorry this is the error …

2023/04/03 14:53:45 [error] 2392#2392: *637 FastCGI sent in stderr: “_sub_type,permalink,primary_focus_keyword_score,readability_score,is_cornerstone,is_robots_noindex
,is_robots_nofollow,is_robots_noimageindex,is_robots_noarchive,is_robots_nosnippet,open_graph_image,open_graph_image_id,open_graph_image_source,open_graph_ima
ge_meta,twitter_image,twitter_image_id,twitter_image_source,primary_focus_keyword,canonical,title,description,breadcrumb_title,open_graph_title,open_gra
ph_description,twitter_title,twitter_description,author_id,post_parent,number_of_pages,post_status,is_protected,is_public,has_public_posts,blog_id,pe
rmalink_hash,created_at,updated_at) VALUES ('5', 'post', 'page', 'https://staging500.resultsbydesign.com/', NULL, '30', '0', NULL, '0', NULL, NULL, NULL, ...PHP message: WordP<br>ress database error Table 'pma_staging.yoast_wp_seo_models_indexable_hierarchy' doesn't exist for query DELETE FROMyoast_wp_seo_models_indexable_hierarchyWHEREindexable_id` = ‘
0′ made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/presbyterian-mission/page-front.php’), get_header, locate_template, load_t
emplate, require_once(‘/themes/presbyterian-mission/header.php’), wp_head, do_action(‘wp_head’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End_Integ
ration->call_wpseo_head, do_action(‘wpseo_head’), WP_Hook->do_action, WP_Hook->apply_filters, Yoast\WP\SEO\Integrations\Front_End_Integration->present_head, Yoast\WP\SEO\Memoizers\Me
ta_Tags_Context_Memoizer->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->for_current_page, Yoast\WP\SEO\Repositories\Indexable_Repository->find_by_id_and_type, Yoa
st\WP\SEO\Builders\Indexable_Builder->build_for_id_and_type, Yoast\WP\SEO\Builders\I” while reading response header from upstream, client: 34.121.70.25

Thanks

Found it now, thanks! The fact that cloudflare is a proxy, does that matter? The ip address I have is the owners normal one. But with cloudflare you get a short term, temporary cloudflare ip.

When I log into wordpress.com and go to My Sites, there is no Manage. There is Settings, but I go there, there is no Security.

I’ll try the second suggestion, but I am skeptical since this is cloudflare and the visible ips are cloudflares and not the users real ip.

Why are the emails not being sent? That would solve this problem for the owner and others.

Thanks, the best I can tell that is not being used on the current live site. But maybe I can make it work.

Thanks, but why on one site and not the development site? Is there a setting somewhere?

Thats so great! Thank you! We can close this then. Thanks again.

@lastsplash I see where to whitelist ip addresses there. But I thought there was a setting somewhere to tell jetpack to use the x_forwarded_for header instead that actual ip which be cloudflare’s ip address for the Protect feature, ie for the “Jetpack has locked your site’s login page”.

I cannot find the Protect feature configuration. Can someone provide a direct link? When I login to cloud.jetpack.com I get a blank page after the login. Thx.

The test tool looks good now. Yes there was a cloudflare setting. It took a minute or so to find it. Thanks!

How do you determine active? It is clearly activated in the CMS and I got this image from the owner of the site: https://www.dbswebsite.com/wp-content/uploads/jetpack.jpg

Thanks! I whitelisted jetpack’s ips. xmlrpc should work now. I did read all the documentation. This a pretty active site, and I only know of 2 instances of this happening. That makes it pretty hard to know of a “fix”. One of those was the site owner too. Both said they never got the email.

I guess my real question is since the site/jetpack sees cloudflare ip addresses, and not the user’s real ip, does that cause any problem since those can be re-used by more than one person? example: somebody does something suspicious and leaves the site. Then that ip is assigned to someone else at some point. Could that “someone else” be blacklisted?