So we set it up to use in the database in wordfence-waf.php file.

define('WFWAF_STORAGE_ENGINE', 'mysqli');

Even so, Wordfence keeps going back to learning mode.

What else can we do? How can we identify why this continues to happen?

Thank you for your help.

I am using running a website on multiple servers behind a load balancer. When I save my exported order file I seem to only get **some** (not all) of the orders) in my file.

I scaled down to 1 server during a period of light traffic and the export saves/runs/opens as expected – with all of the orders.

When I export while running multiple servers it seems that there is a piece of the complete order file in the tmp directory of each server and that I am only saving one of those pieces.

Is there a way to ensure that the export executes all on one server so that I download 1 complete file?

Thanks,
Dave

https://www.ads-software.com/plugins/woo-order-export-lite/

web servers:
ensrv server in US
jpsrv server in Japan
cnsrv server in China
※Source(wordpress) in all of the web server are the same.

database:
server in US

Now I faced a problem. It takes long time for myjp.com access to database in US. Can I install separated database in Japan , China and US? If so, how to Maintain data synchronization？

web servers:
ensrv server in US
jpsrv server in Japan
cnsrv server in China
※Source(wordpress) in all of the web server are the same.

database:
server in US
※Is it good for all the web server access to one db server? I am afraid that it is very slow for web server in Japan or China.

restriction for acecss by registration (login status).
when a user registered by myen.com(en.mydomain.com) he can only access to myen.com. If he accesses to other sites(myjp.com, mycn.com) he will get an error or redirect to myen.com
※I will record the sub site where he first registered in the database.

restriction for access by ip.
switch(ip)
case :
ip in Japan, he can only access to myjp.com
ip in China, he can only access to mycn.com
ip else, he can only access to myen.com

how to do all or parts of these functions?
At first, which parts are possible or impossible ?

Here’s a generic image of my setup:
https://cl.ly/image/0a1X0I2X2R0v

I’ve tested this multiple ways. In the following scenarios all I’m doing is swapping the order of the servers out of the text area or removing them:

Scenario 1:
server a <– purges
server b <– does not purge

Scenario 2:
server b <– purges
server a <– does not purge

Scenario 3:
server a <– purges

Scenario 4:
server b <– purges

So in each scenario only the first server will ever purge. I’ve verified the array inside the config as well and I do see all the servers listed, I’ve also turned on debugging and there’s no error that occurs in relation to varnish. In each instance I was running, varnishlog -c -m RxRequest:PURGE which will only show purge requests as they happen.

I’ve also tested another plugin: Multi-Varnish HTTP Purge which does purge both of them at the same time as expected, however, I don’t want to use another plugin to accomplish this

Let me know if you have any ideas or tricks I might be missing

https://www.ads-software.com/plugins/w3-total-cache/

Does anyone have any experience with this? What kind of solution have you implemented?

Is there any documentation on this?

https://www.ads-software.com/plugins/w3-total-cache/

When testing on our development site I had the tables split into four databases but on the same server. This worked.

However, when it came to splitting the databases across different servers the site crashed.

I’ve tried a number of different configs. Including:

$wpdb->add_database(array(
	'host'     => 'xxx1',     // If port is other than 3306, use host:port.
	'user'     => DB_USER,
	'password' => DB_PASSWORD,
	'name'     => 'db1name',
));

$wpdb->add_database(array(
	'host'     => 'xxx2',     // If port is other than 3306, use host:port.
	'user'     => DB_USER2,
	'password' => DB_PASSWORD2,
	'name'     => 'db2name',
	'write'    => 1,
	'read'     => 1,
	'dataset'  => 'news',
	'timeout'  => 0.2,
));

$wpdb->add_table( 'news', 'tablename' );

I have also tried using :

$wpdb->add_callback('my_db_callback');
function my_db_callback($query, $wpdb) {
	// Multisite blog tables are "{$base_prefix}{$blog_id}_*"
	if ( preg_match("/tablename/", $wpdb->table) )
		return 'news';

Can anyone tell me what i’m missing? we ideally want to split the tables over several servers but currently i have settled for a master/slave environment.

Any help would be grand…

https://www.ads-software.com/extend/plugins/hyperdb/

A

wp-content/advanced-cache.php
	wp-content/db.php
	wp-content/object-cache.php
	wp-content/plugins/w3-total-cache/
	wp-content/w3-total-cache-config-{sitename}-preview.php
	wp-content/w3tc-{sitename}/

As much as possible, I’d like to copy these files from one server to another once, rather than continuously syncing them. Does anybody know if any of these files/dirs or their subdirectories will need to be constantly synchronized between the multiple boxes?

Want to run busy wordpress site(s) on multiple server nodes (typical LAMP stack). I want the blogs to be pointed to a single database node (not localhost). Content to public would be served from n server nodes but updates to be done on single instance.

Need wordpress admin/dashboard to be served off of single node pointing to a single database instance. Single node can either be public or internal DNS, though if you can set up one you can do the other. I have complete control over apache, mysql, rsync scripts, php, etc. but I’d like to contain this within apache as much as possible for simplicity’s sake (read: I don’t want to have to compile new php modules or apache modules if possible).

Why does it seem so hard to do this and why is there nothing that I can find easily on the wordpress support site? I can’t be the only person wanting to do this….

Use case:

User logins to dashboard, uploads images which get rsynced from single box to multiple boxes/servers.
Updates blog posts which is pointed to single database.

How can I get this done easily? I am thinking of adding in a redirect for /wp-admin/ to point to https://admin.somesite.com which is a virtual host with internal DNS pointed