Replies: 0

Hello,

On the firewall dashboard I am getting the following error:

Warning: mysqli_query(): (22003/1690): BIGINT UNSIGNED value is out of range in '(unix_timestamp() - <code>cpanel_wp017</code>.<code>wp54_wflocs</code>.<code>ctime</code>)' in /home/cpanel/public_html/wp-includes/wp-db.php on line 1924
WordPress database error: [BIGINT UNSIGNED value is out of range in '(unix_timestamp() - <code>vcpanel_wp017</code>.<code>wp54_wflocs</code>.<code>ctime</code>)']

In phpAdmin, I checked and the wflocs table is there and is apparently adding items and functioning as far as reporting of blocked IPs.

In the WordFence diagnostics everything is green and listed as ok under MySQL

MySQL version is 5.7.25 and I use PHP version 7.2.14

I uninstalled WordFence and reinstalled via the WordPress.org repository, but no change.

The int for the ctime is 10 but i didn’t mess with it.

Thanks.

• This topic was modified 13 minutes ago by VidYen, LLC.
• This topic was modified 13 minutes ago by VidYen, LLC.

Replies: 0

This morning I got this message from Wordfence:

* File appears to be malicious: wp-content/plugins/updraftplus/vendor/phpseclib/phpseclib/tests/Unit/Crypt/RSA/LoadKeyTest.php
File Type: Not a core, theme, or plugin file from wordpress.org.
Details: This file appears to be installed or modified by a hacker to perform malicious activity. If you know about this file you can choose to ignore it to exclude it from future scans. The matched text in this file is: $key = ‘MIICXAIBAAKBgQCqGKukO1De7zhZj6+H0qtjTkVxwTCpvKe4eCZ0FPqri0cb2JZfXJ/DgYSF6vUp’ .\x0a ‘wmJG8wVQZKjeGcjDOL5UlsuusFncCzWBQ7RKNUSesmQRMSGkVb1/3j+skZ6UtW+5u09lHNsj6tQ5’ .\x0a ‘…
The issue type is: Backdoor:PHP/SEemf0Ji
Description: A backdoor known as SEemf0Ji

The file is dated January 30 2019 when the plugin was updated. And only today it did popup as an error.

I check with UpdraftPlus and got this answer:
This is a false positive; you can see the original file from the phpseclib project here – https://github.com/phpseclib/phpseclib/blob/master/tests/Unit/Crypt/RSA/LoadKeyTest.php – containing the same string as a test RSA key in a harmless context.

Could it have to do with the fact that I used the french version of plugin ?
Please correct Wordfence scan.

Replies: 0

Greetings all. We have a point release for Wordfence today, version 7.2.1. Please update as soon as you are able.

• Improvement: Integrated Wordfence with Wordfence Central, a new service allowing you to manage multiple Wordfence installations from a single interface.
• Improvement: Added a help link to the mode display when a host disabling Live Traffic is active.
• Improvement: Added an option for whitelisting ManageWP in “Whitelisted Services”.
• Fix: Enqueued fonts used in admin notices on all admin pages.
• Fix: Change false positive user-reports link to use https.
• Fix: Fix reference to non-existent function when registering menus.

Thanks everyone for great comments and suggestions. Send any of those you might have to feedback@wordfence.com and someone will get back to you.
Keep in mind, the feedback address is not a place to request support.
Also, no support questions will be answered in this thread.
Free support requests can be posted at https://wordpress.org/support/plugin/wordfence
Our premium customers can open a ticket at http://support.wordfence.com

Replies: 0

Hi,

I’m trialing Wordfence as I need to limit the information exposed by WordPress about existing users. I have the option ‘Don’t let WordPress reveal valid users in login errors’ ticked under brute force protection, but this does not seem to work because when I enter a non-existant username on the login screen, the error message says ‘Error: invalid username’ – obviously confirming that the username does not exist. If I enter a valid username but incorrect password, I get an error saying that ‘ERROR: The password you entered for the username <username> is incorrect.’ – confirming that a user with that username exists.

I thought that this setting was supposed to fix this issue? Am I mistaken or am I doing something wrong? I am only using the free version of Wordfence not premium, is this the problem?

Many thanks
Kevin

• This topic was modified 18 minutes ago by the_lar.

Replies: 0

Hi,

Does Wordfence have any option to disable errors on the lostpassword form? This is a serious security issue as it allows hackers to discover if a username or email exists. Ideally, regardless of whether the username or email exists, WordPress should display a generic message saying that ‘IF there is a matching user, an email will be sent’ – something like that anyway.

I’ve been searching all day for a solution to this and it doesn’t seem like anything exists.

Many thanks
Kevin

Replies: 0

wp_remote_post() test back to this server failed! Response was: cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.

Should I worry about this error?

• This topic was modified 1 hour, 1 minute ago by srsrsrp.

Replies: 1

Tried to log in today to write a new post and found that my blog is missing.

Here is the error code:

Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0

Fatal error: Unknown: Failed opening required ‘/home/shaunch/public_html/wordfence-waf.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in Unknown on line 0

Per your ideas above, I can’t update anything … there’s nothing to update. Exact steps to reproduce, just try to visit my blog. I have tried contacting someone at WP all afternoon … got zip. Contacted JetPack, and they referred me to you and a plugin called Wordfence. I can assure you I did not install it … never heard of it, never saw it.

Please help … I’ve been writing here for several years … can’t believe everything could be gone.

Thank you,
Lois Bryan

• This topic was modified 1 hour, 24 minutes ago by Lois Bryan.

Replies: 0

After receiving an email from Wordfence today, I tried to access my site to update the plug-ins it flagged as out of date. This list included Wordfence which needed updating to 7.2.1.

When I tried to reach the site, it generated an HTTP error 500 and I could not access the site or WordPress. I confirmed the site was still running from another device without the WordPress credentials cached.

I then found this error in the WordPress log so I disabled Wordfence and WordPress was running again.

Warning: require_once(lib/wordfenceConstants.php): failed to open stream: No such file or directory in /home/content/p3pnexwpnas10_data01/17/42279417/html/wp-content/plugins/wordfence/wordfence.php on line 71

Fatal error: require_once(): Failed opening required ‘lib/wordfenceConstants.php’ (include_path=’.:/opt/remi/php72/root/usr/share/pear:/opt/remi/php72/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/content/p3pnexwpnas10_data01/17/42279417/html/wp-content/plugins/wordfence/wordfence.php on line 71

I’m reluctant to re-enable Wordfence until I confirm the cause of the crash. Wordfence now shows it’s version 7.2.1 even though I never updated it. Is this a known issue with this version? I didn’t even realize Wordfence was set to auto-update.

Replies: 1

Hello –

We are finding in a lot of cases where we set up staging sites in sub-directories off of the root where the site in the root directory has Wordfence enabled and it blocks any Ajax requests on the site in the sub-directory being made.

Is there a way to disable this or list a specific directory in the file tree not to be watched by Wordfence? The only other option I have right now is to disable the plugin altogether on the production site, which is not ideal.

Thanks.

Replies: 1

Hi,

I just received the email below from Wordfence.

Is WF saying that I have these files in my site but they are not part of the wp release in repo?

Two possibly relevant points:

1) A few days ago, I downgraded wp core from 5.0.3 down to 4.9.9 using a downgrade plugin. It looks like many if not all of the files below belong to Gutenberg, included in wp 5.0 +. Could it be this plugin did not delete files that belonged to wp 5.x?

2) I got this message about 2 minutes after WF was updated to 7.2.1.

Thanks ahead of time 🙂

High Severity Problems:

* Unknown file in WordPress core: wp-admin/edit-form-blocks.php

* Unknown file in WordPress core: wp-includes/blocks/archives.php

* Unknown file in WordPress core: wp-includes/blocks/block.php

* Unknown file in WordPress core: wp-includes/blocks/categories.php

* Unknown file in WordPress core: wp-includes/blocks/latest-comments.php

* Unknown file in WordPress core: wp-includes/blocks/latest-posts.php

* Unknown file in WordPress core: wp-includes/blocks/shortcode.php

* Unknown file in WordPress core: wp-includes/blocks.php

* Unknown file in WordPress core: wp-includes/class-wp-block-parser.php

* Unknown file in WordPress core: wp-includes/class-wp-block-type-registry.php

* Unknown file in WordPress core: wp-includes/class-wp-block-type.php

* Unknown file in WordPress core: wp-includes/css/dist/block-library/editor-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/editor-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/editor.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/editor.min.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/style.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/theme-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/theme-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/theme.css

* Unknown file in WordPress core: wp-includes/css/dist/block-library/theme.min.css

* Unknown file in WordPress core: wp-includes/css/dist/components/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/components/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/components/style.css

* Unknown file in WordPress core: wp-includes/css/dist/components/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/edit-post/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/edit-post/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/edit-post/style.css

* Unknown file in WordPress core: wp-includes/css/dist/edit-post/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/editor-styles-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/editor-styles-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/editor-styles.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/editor-styles.min.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/style.css

* Unknown file in WordPress core: wp-includes/css/dist/editor/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/format-library/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/format-library/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/format-library/style.css

* Unknown file in WordPress core: wp-includes/css/dist/format-library/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/list-reusable-blocks/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/list-reusable-blocks/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/list-reusable-blocks/style.css

* Unknown file in WordPress core: wp-includes/css/dist/list-reusable-blocks/style.min.css

* Unknown file in WordPress core: wp-includes/css/dist/nux/style-rtl.css

* Unknown file in WordPress core: wp-includes/css/dist/nux/style-rtl.min.css

* Unknown file in WordPress core: wp-includes/css/dist/nux/style.css

* Unknown file in WordPress core: wp-includes/css/dist/nux/style.min.css

* Unknown file in WordPress core: wp-includes/js/dist/a11y.js

* Unknown file in WordPress core: wp-includes/js/dist/a11y.min.js

* Unknown file in WordPress core: wp-includes/js/dist/annotations.js

* Unknown file in WordPress core: wp-includes/js/dist/annotations.min.js

* Unknown file in WordPress core: wp-includes/js/dist/api-fetch.js

* Unknown file in WordPress core: wp-includes/js/dist/api-fetch.min.js

* Unknown file in WordPress core: wp-includes/js/dist/autop.js

* Unknown file in WordPress core: wp-includes/js/dist/autop.min.js

* Unknown file in WordPress core: wp-includes/js/dist/blob.js

* Unknown file in WordPress core: wp-includes/js/dist/blob.min.js

* Unknown file in WordPress core: wp-includes/js/dist/block-library.js

* Unknown file in WordPress core: wp-includes/js/dist/block-library.min.js

* Unknown file in WordPress core: wp-includes/js/dist/block-serialization-default-parser.js

* Unknown file in WordPress core: wp-includes/js/dist/block-serialization-default-parser.min.js

* Unknown file in WordPress core: wp-includes/js/dist/blocks.js

* Unknown file in WordPress core: wp-includes/js/dist/blocks.min.js

* Unknown file in WordPress core: wp-includes/js/dist/components.js

* Unknown file in WordPress core: wp-includes/js/dist/components.min.js

* Unknown file in WordPress core: wp-includes/js/dist/compose.js

* Unknown file in WordPress core: wp-includes/js/dist/compose.min.js

* Unknown file in WordPress core: wp-includes/js/dist/core-data.js

* Unknown file in WordPress core: wp-includes/js/dist/core-data.min.js

* Unknown file in WordPress core: wp-includes/js/dist/data.js

* Unknown file in WordPress core: wp-includes/js/dist/data.min.js

* Unknown file in WordPress core: wp-includes/js/dist/date.js

* Unknown file in WordPress core: wp-includes/js/dist/date.min.js

* Unknown file in WordPress core: wp-includes/js/dist/deprecated.js

* Unknown file in WordPress core: wp-includes/js/dist/deprecated.min.js

* Unknown file in WordPress core: wp-includes/js/dist/dom-ready.js

* Unknown file in WordPress core: wp-includes/js/dist/dom-ready.min.js

* Unknown file in WordPress core: wp-includes/js/dist/dom.js

* Unknown file in WordPress core: wp-includes/js/dist/dom.min.js

* Unknown file in WordPress core: wp-includes/js/dist/edit-post.js

* Unknown file in WordPress core: wp-includes/js/dist/edit-post.min.js

* Unknown file in WordPress core: wp-includes/js/dist/editor.js

* Unknown file in WordPress core: wp-includes/js/dist/editor.min.js

* Unknown file in WordPress core: wp-includes/js/dist/element.js

* Unknown file in WordPress core: wp-includes/js/dist/element.min.js

* Unknown file in WordPress core: wp-includes/js/dist/escape-html.js

* Unknown file in WordPress core: wp-includes/js/dist/escape-html.min.js

* Unknown file in WordPress core: wp-includes/js/dist/format-library.js

* Unknown file in WordPress core: wp-includes/js/dist/format-library.min.js

* Unknown file in WordPress core: wp-includes/js/dist/hooks.js

* Unknown file in WordPress core: wp-includes/js/dist/hooks.min.js

* Unknown file in WordPress core: wp-includes/js/dist/html-entities.js

* Unknown file in WordPress core: wp-includes/js/dist/html-entities.min.js

* Unknown file in WordPress core: wp-includes/js/dist/i18n.js

* Unknown file in WordPress core: wp-includes/js/dist/i18n.min.js

* Unknown file in WordPress core: wp-includes/js/dist/is-shallow-equal.js

* Unknown file in WordPress core: wp-includes/js/dist/is-shallow-equal.min.js

* Unknown file in WordPress core: wp-includes/js/dist/keycodes.js

* Unknown file in WordPress core: wp-includes/js/dist/keycodes.min.js

* Unknown file in WordPress core: wp-includes/js/dist/list-reusable-blocks.js

* Unknown file in WordPress core: wp-includes/js/dist/list-reusable-blocks.min.js

* Unknown file in WordPress core: wp-includes/js/dist/notices.js

* Unknown file in WordPress core: wp-includes/js/dist/notices.min.js

* Unknown file in WordPress core: wp-includes/js/dist/nux.js

* Unknown file in WordPress core: wp-includes/js/dist/nux.min.js

* Unknown file in WordPress core: wp-includes/js/dist/plugins.js

* Unknown file in WordPress core: wp-includes/js/dist/plugins.min.js

* Unknown file in WordPress core: wp-includes/js/dist/redux-routine.js

* Unknown file in WordPress core: wp-includes/js/dist/redux-routine.min.js

* Unknown file in WordPress core: wp-includes/js/dist/rich-text.js

* Unknown file in WordPress core: wp-includes/js/dist/rich-text.min.js

* Unknown file in WordPress core: wp-includes/js/dist/shortcode.js

* Unknown file in WordPress core: wp-includes/js/dist/shortcode.min.js

* Unknown file in WordPress core: wp-includes/js/dist/token-list.js

* Unknown file in WordPress core: wp-includes/js/dist/token-list.min.js

* Unknown file in WordPress core: wp-includes/js/dist/url.js

* Unknown file in WordPress core: wp-includes/js/dist/url.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/lodash.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/lodash.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/moment.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/moment.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/react-dom.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/react-dom.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/react.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/react.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-element-closest.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-element-closest.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-fetch.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-fetch.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-formdata.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-formdata.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-node-contains.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill-node-contains.min.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill.js

* Unknown file in WordPress core: wp-includes/js/dist/vendor/wp-polyfill.min.js

* Unknown file in WordPress core: wp-includes/js/dist/viewport.js

* Unknown file in WordPress core: wp-includes/js/dist/viewport.min.js

* Unknown file in WordPress core: wp-includes/js/dist/wordcount.js

* Unknown file in WordPress core: wp-includes/js/dist/wordcount.min.js

* Unknown file in WordPress core: wp-includes/rest-api/endpoints/class-wp-rest-autosaves-controller.php

* Unknown file in WordPress core: wp-includes/rest-api/endpoints/class-wp-rest-block-renderer-controller.php

* Unknown file in WordPress core: wp-includes/rest-api/endpoints/class-wp-rest-blocks-controller.php

* Unknown file in WordPress core: wp-includes/rest-api/endpoints/class-wp-rest-search-controller.php

* Unknown file in WordPress core: wp-includes/rest-api/endpoints/class-wp-rest-themes-controller.php

* Unknown file in WordPress core: wp-includes/rest-api/search/class-wp-rest-post-search-handler.php

* Unknown file in WordPress core: wp-includes/rest-api/search/class-wp-rest-search-handler.php

Replies: 0

Hi

This is a minor visual / CSS issue which is affecting us and really annoying, to be honest.

The input text field, like in the import section, is hidden when we use a plugin: https://dns.d.pr/sIIaKz when the original way shows it like this: https://dns.d.pr/MV9ZlE

After contacting the other plugin’s author, this is the reply that I got:

It is not due to our plugin but Wordfence itself has a style border:0 which is hiding the text input. Actually, WordPress default style is overriding the Wordfence border:0 style, but because our plugin is overriding WordPress default style, the Wordfence’s unnecessary style has applied. You may need to notify Wordfence about this unwanted extra css. You can check screenshot of the issue https://ibb.co/F3nmVL9

Can this be fixed by removing that style in your plugin, by all means?

Thank you

• This topic was modified 8 minutes ago by bnbox.

Replies: 0

I am not able to start wordfence scan. I always get this message: “Scan Failed
The scan has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself.” I tried all the obvious steps, but that didn’t help.

I am on the latest plugin version.

The logs always say this: “[Feb 06 03:56:14] Scan stop request received.”

Any ideas ?

Replies: 0

I like the new Wordfence Central functionality, but I’d rather use it via my own self-hosted administrative website – i.e. just like the UpdraftCentral offering does for backups.

Is this something that you may offer in the future?

Replies: 0

Hi

Apologies if this has been posted before. Is it possible to customise the locked out page? I’d like to create a more user friendly layout using the client’s brand.

Many thanks

JM

Replies: 0

Dear Support

I have been using Wordfence for some time now and twice this week it has locked me out completely ( I am currently locked)

I had originally solved the problem by disabling the plugin, logging into WordPress and installing Wordfence Assistant to disable the firewall. I reactivated the plugin, reconfigured the firewall settings, and whitelisted my IP not to have this happen again. I still kept the WA activated (did not know whether disable it) Yesterday, trying to log in it shut me out again. Send them the email address ( I am the admin) but never received to unblock it. H

What step am I missing?
Many thanks

Teresa C.

Replies: 0

Hi,

I’ve been given a big security checklist by my client and I need to see whether the features of Wordfence meet this criteria, this particular point relates to the logging of sensitive security events. The criteria I’ve been given is as follows:

A minimum set of logs (enough to detect suspicious activities as soon as possible) must be produced by the web application.

• Authentication (success and failure)
• Password changes
• Password reset
• Writing operation performed by users
• Access failure (security or error)
• Input rejected by filters

However, some elements must not be logged:

• Passwords and password hashes
• Payment information (credit card numbers and CVV)
• Fullname of users

Could anyone give me some steer as to whether this kind of information is logged by Wordfence and how I can access it? I have looked under ‘Live traffic’ and while that shows logins and logouts, it doesn’t seem to show authentication failures, password resets.

Many thanks
Kevin

Replies: 0

Howdy – i’ve been a long time user of Wordfence Premium, but even their customer support staff don’t seem to be much help. Using WF 7.2.1 on WP 5.0.3.

In a few instances of my WP installations, i run a separate web app alongside the WP site. As such, these apps make a lot of requests to non-WP pages and scripts. From time to time, WF blocks these requests, mostly the AJAX calls.

I would like to know how to manually add URLs to the Wordfence Whitelist so that those calls are no longer blocked at all. I have read the documentation, but putting WF into Learning Mode doesn’t seem to work all the time, and adding things manually seems like it should be very simple – but it is not!

I am on the Firewall Options page, down in the Whitelisted URLs section. In all of the documentation – and after contacting support – i still don’t know what to put in the Param Type or Param Name fields. There is NO DOCUMENTATION on this. Can anyone shed some light on what those do, and how to allow all access to a particular page/script?

Thanks in advance, AirYT

Replies: 0

Hello,, Dave,,^^ How are you^^

I am not sure you remember me or not. You were help me before like this topic^^
“https://wordpress.org/support/topic/my-wordfence-is-something-wrong/#post-11094827”

I was updated Worefence. And I have same problem as before like this “https://prnt.sc/mhhrfn“^^

However, I had file which you make for me new code like this “https://prnt.sc/mhhtw5“^^
ㄴ So, I try to download file “wordfenceClass.php” from ftp.
ㄴ And I carefully look.
ㄴ But I can not found about line 5945 and 6006…

So…
Could you help me one more time when you have enough time,,??

I am so sorry…

Thank you Dave…

Replies: 0

Hey,

I really love the wordfence central – but I’m stuck on a few sites with an error when it’s trien to do the second step:
“Passing public key to Wordfence Central.”.

I only get the Error “An error occurred”, nothing specific. Any ideas, how to solve this? WordPress and Wordfence are Up-to-date.

Regards
matthias

P.S. I’ve read this:
https://www.wordfence.com/help/central/connect/

But I can’t find any of this problems on the sites.

• This topic was modified 1 hour, 55 minutes ago by .

Replies: 0

please give instructions on how to delete my Central account completely, and my WF account too