Jaap de Wit

Same here, after update the plugin disabled itself on all websites I’m running it. Error: The plugin creame-whatsapp-me/whatsappme.php has been deactivated due to an error: Plugin file does not exist.

Must have been an error in the update. Enabling the plugin solved the issue.

@webtemyk thanks that solved the issue!

I’ve changed the template but then nothing is showing. From what country are you trying to look at the site? Strange you can’t see it.

Hi,

Nothing wrong with the website. It’s available. What error do you get?
Screenshot here: https://snipboard.io/VBpSiw.jpg

Cheers,
Jaap

Sure:

load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3 Uncaught TypeError: ((n.event.special[g.origType] || {}).handle || g.handler).apply is not a function
at HTMLDocument.dispatch (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3)
at HTMLDocument.r.handle (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3)
at Object.trigger (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3)
at Object.a.event.trigger (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:9)
at HTMLButtonElement.<anonymous> (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3)
at Function.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:2)
at a.fn.init.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:2)
at a.fn.init.trigger (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:3)
at Object.success (avia-builder.js?ver=0.9.5:1024)
at i (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=4.9.8:2)

Hi Oliver,

I did some more research and found out that it’s Varnish combined with the plugin which is causing this issue. I inserted a Varnish rule to exclude /my-account and now it’s working fine.

So maybe this is something you can look at?

Cheers,
Jaap

Hi Héctor,

I’ve enabled both caching and data sampling and CPU usage dropped back to normal. Thanks for your quick response and solution!

Cheers,
Jaap

Hi,

I’ve tested it with all plugins disabled. Login as a customer then works just fine. When I activate the quotes plugin the problem comes back. Please help.

Cheers,
Jaap

HI,

I’ve tried disabling all plugins but Woo and Offers but the problem persists. Also tried it with twentyseventeen theme, same issue. The buttons in the mails keep pointing to email.domainname.com.

What else can I try?

iThemes fixed this issue yesterday in ithemes security pro version 4.0.0. Changelog:

4.0.0 – 2017-06-21 – Chris Jean & Timothy Jacobs
Bug Fix: Fixed an infinite loop that could occur when expiring a cookie and Hide Backend is enabled.

@pronl I’ve openend a support ticket with iThemes last week since I have a subscription. Curious what they can find out. I’ve also discovered the problem happens in Chrome only and can also be solved by clearing the cache.

Further details:

– WP 4.8
– iThemes security pro 3.9.0 with hide backend enabled
– PHP 7

In the logs I see:

On apache:
[Mon Jun 19 06:49:39.824088 2017] [proxy_fcgi:error] [pid 8312] [client 127.0.0.1:45415] AH01067: Failed to read FastCGI header
[Mon Jun 19 06:49:39.824154 2017] [proxy_fcgi:error] [pid 8312] (104)Connection reset by peer: [client 127.0.0.1:45415] AH01075: Error dispatching request to :

On Nginx it’s this error:
2017/06/15 12:10:12 [error] 13221#0: *5102088 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xx.xxx.xxx.xx, server: https://www.websiteurl.nl, request: “GET / HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php7.0-fpm.sock:”, host: “www.websiteurl.nl”

@mattkslx I’ve noticed that it only happens the moment I’m trying to go to the custom login url of the website. And yes, it also seems to happen only with WP 4.8 sites.

To answer your questions:

– iThemes is still active since it triggers the error. When I get the error I change the directory name to ithemes-security-pro.old (so not the plugins dir). Then login through the normal url /wp-admin.
– Go to plugins section, you will see the ithemes plugin is disabled
– Rename the directory back to it’s original name with FTP
– Refresh plugins section, ithemes plugin should be enabled again.
– The hide backend feature is still enabled during the process. Probably another workaround for this issue is to disable it in the correct database table.

Hope this will help.

This worked for me:

– Rename the plugin directory with FTP
– Login the website and go to plugin section
– Rename the plugin directory to original name
– Refresh plugin section

Hi,

I had the same issue. You probably use W3 Total cache or another caching plugin. try adding _yith_ywraq_session_ to the ignored string section of the database cache.

Cheers,
Jaap

@daymobrew, it’s version PHP Version 5.3.29