lsphp 255641 username cwd DIR 253,0 4096 17015496 /home/username/website/wp-admin
lsphp 255641 username 7u REG 253,0 51 21152705 /home/username/website/wp-content/wflogs/ips.php
lsphp 255641 username 8u REG 253,0 560 21152784 /home/username/website/wp-content/wflogs/config.php
lsphp 255641 username 9u REG 253,0 40083 21112604 /home/username/website/wp-content/wflogs/attack-data.php
lsphp 255641 username 10u REG 253,0 14218 21116318 /home/username/website/wp-content/wflogs/config-synced.php (deleted)
lsphp 255641 username 11u REG 253,0 37889 21112666 /home/username/website/wp-content/wflogs/config-livewaf.php
lsphp 255641 username 12u REG 253,0 1545298 21153461 /home/username/website/wp-content/wflogs/config-transient.php
lsphp 255641 username 14u IPv4 2263568748 0t0 TCP localhost:40946->localhost:memcache (SYN_SENT)
lsphp 257665 username cwd DIR 253,0 4096 17016270 /home/username/website
lsphp 257665 username 7u REG 253,0 51 21152705 /home/username/website/wp-content/wflogs/ips.php
lsphp 257665 username 8u REG 253,0 560 21152784 /home/username/website/wp-content/wflogs/config.php
lsphp 257665 username 9u REG 253,0 40083 21112604 /home/username/website/wp-content/wflogs/attack-data.php
lsphp 257665 username 10u REG 253,0 14218 21112680 /home/username/website/wp-content/wflogs/config-synced.php (deleted)
lsphp 257665 username 11u REG 253,0 37889 21112666 /home/username/website/wp-content/wflogs/config-livewaf.php
lsphp 257665 username 12u REG 253,0 1545298 21153461 /home/username/website/wp-content/wflogs/config-transient.php
lsphp 257665 username 14u IPv4 2263561840 0t0 TCP localhost:40924->localhost:memcache (SYN_SENT)
lsphp 265986 username cwd DIR 253,0 4096 17016270 /home/username/website
lsphp 265986 username 7u REG 253,0 51 21152705 /home/username/website/wp-content/wflogs/ips.php
lsphp 265986 username 8u REG 253,0 560 21152784 /home/username/website/wp-content/wflogs/config.php
lsphp 265986 username 9u REG 253,0 40083 21112604 /home/username/website/wp-content/wflogs/attack-data.php
lsphp 265986 username 10u REG 253,0 14216 21116535 /home/username/website/wp-content/wflogs/config-synced.php (deleted)
lsphp 265986 username 11u REG 253,0 37889 21112666 /home/username/website/wp-content/wflogs/config-livewaf.php
lsphp 265986 username 12u REG 253,0 1545298 21153461 username/wp-content/wflogs/config-transient.php
lsphp 265986 username 14u IPv4 2263533408 0t0 TCP localhost:40930->localhost:memcache (SYN_SENT)
These notifications are sent by their firewall to indicate that it has blocked its service because it is making anomalous connections, of type SYN_SENT, which are usually attributable to outward DDoS attacks.
If the firewall performs this type of action, it means that something abnormal or “different than usual” is being performed.
]]>I startet to use the plugin on a demo WordPress with PHP8.3 and it startet running. However, I disabled it and enabled it on a different WordPress with PHP8.2 and it work too.
My problem, it don’t work if the plugin is already enabled and I try to enable it on another installation. I see the message “plugin enabled” but after a reload it is still disabled. It look like there is a check for that…
Is it possible to support such situation? Maybe a “salt” or “hash” for every installation?
best regards, Andyt
]]>the website was still not being cached dynamically and that is due to the “cleantalk-spam-protect” plugin as it continued to add no-cache headers. As soon as I deactivated the plugin, the Dynamic Cache started working as expected as per the following CURL test
They then said:
And if you wish to keep on using the CleanTalk plugin, then you should discuss this further with their support team on how exactly to remove the headers added by the plugin which currently affect the functionalities of the dynamic cache.
As this plugin has been Deactivated to attain the Memcache feature for several hours, I would appreciate your earliest advice about this, as I am concerned about my website’s security without this plugin being Activated.
Thanks Alan
]]>Plugin could not be activated because it triggered a fatal error.
Fatal error: Cannot redeclare wp_cache_add() (previously declared in /home/audubonartists/public_html/wordpress/wp-includes/cache.php:41) in /home/audubonartists/public_html/wordpress/wp-content/plugins/memcached/object-cache.php on line 22
I looked at the file manager and commented out lines 14-23, but that caused the whole site to go down with a fatal error and I had to uncomment it.
]]>I am using WordPress 6.1.1 with PHP 7.4 on the server and enabled the Memcache extension. From the Query Monitor plugin I get the following message:
Persistent object cache plugin not in use.
The Memcache object cache extension for PHP is installed, but is not in use by WordPress. You should install a Memcache plugin.
I installed the CacheMaster plugin to hopefully fix this issue. However on the Basic page I only get three choices for the driver: File, MySQL an SQL Lite. Why do I not see Memcache? If for some reason CacheMaster does not see it can I use another driver? In any event, I tried each the thee drivers and enabled the caching, but still see the same message.
]]>A persistent object cache makes your site’s database more efficient, resulting in faster load times because WordPress can retrieve your site’s content and settings much more quickly.
Your hosting provider can tell you if a persistent object cache can be enabled on your site. Your host appears to support the following object caching services: Memcache, Memcached.
I manage my own server. Memcache is installed. This has been verified by my hosting company.
Does a plugin need to be used to make this error go away?
Can you please shed some light on this situation? I can’t be the only one that is wondering! lol
Thanks in advance,
-Joe
]]>The plugin worked right out of the box after activation and initial setup, even WordPress Site Health detects the presence of an object cache.
]]>Just to let you know of an issue when using your plugin on Siteground (Nginx server) and activating memcache. Orders started coming in as blanks with all customer data lost.
Took a while for siteground support to find the issue, but thorough testing showed that the issue only appeared when Mailchimp for WooCommerce plugin was active.
Steve