WordPress plugin diagnostic report: what to send to support safely
To prepare a WordPress diagnostic report for plugin support with BetterShield, open BetterShield › Settings › General, find Report a problem under Privacy & sharing, and press Prepare the Report. It describes how BetterShield is set up on your site and leaves out the site address, email addresses, usernames, IP addresses, keys, tokens, hashes and file contents. Nothing is sent: you read it, press Copy the Report and choose where to paste it.
A good support request saves everyone a round of questions, and this report answers most of them in one paste. If you are locked out and cannot reach the dashboard, start with our guide to getting back in; this post is for the moment you can ask for help and want to do it well.
Quick summary
- Report a problem on BetterShield › Settings › General builds a setup report on your own site, and nothing is transmitted when it does.
- It holds versions, the server type, safe mode and lockdown state, which hardening fixes are on, your sign-in and alert settings, the last audit and up to ten recent BetterShield errors.
- It ends with the line “Left out on purpose: site address, email addresses, usernames, IP addresses, keys, tokens, hashes and file contents.”
- It does name your theme and active plugins, because support often starts by ruling out a clash.
wp bettershield diagnosticsprints the same report from the command line when the dashboard is out of reach.
Why a report beats a description
“It stopped working” gives a helper nothing to go on. What they need is the versions, the server, which protections are on and what changed recently. Those are facts your site already knows, and copying them is faster and more accurate than typing them from memory.
The report is also safe by design. It is prepared on your site, shown to you before anything leaves, and written to leave out the things that should not be pasted into a ticket. You stay in control of whether it goes to the public WordPress.org forum or into a private ticket.
What the report holds
The report is a short block of text, one line or two for each area:
- BetterShield’s version, and the WordPress and PHP versions.
- Whether the site is multisite, the web server type and whether it reads .htaccess, the environment type and the language.
- Whether safe mode is on, whether the site is locked down, and whether a recovery link is on record.
- Which hardening fixes are on, any whose undo failed, and any that are not available on this server.
- Your Login & Access settings, including whether the attempt limit is on and whether the server firewall line is on, with only a count of the entries in each list.
- The password rules, how many accounts use two-factor, whether agents may read the site, and your alert settings with a count of recipients.
- The last audit: when it ran, how many checks ran, the score and the open findings by severity.
- Up to ten of BetterShield’s own errors from the last 7 days.
- Your theme and active plugins, with their versions.
Counts stand in for lists. The report says how many addresses are on an allowlist, not which ones, and how many recipients get alerts, not who they are.
What it leaves out
The last line of the report states it: “Left out on purpose: site address, email addresses, usernames, IP addresses, keys, tokens, hashes and file contents.”
Two things are worth knowing. First, the theme and plugin list is included. Support often starts by ruling out a clash with another plugin, so it is useful, but it is also a list you might not want in public. If you would rather not post it, open a ticket instead of using the forum. Second, the report is read-only: preparing and copying it changes nothing on the site.
Set it up
- Open BetterShield › Settings › General and find Report a problem under Privacy & sharing.
- Press Prepare the Report.
- Read it in the box that appears. Look for anything you would rather not share.
- Press Copy the Report. If the browser will not copy it, select the text and copy it by hand.
- Paste it into your forum post or ticket. Refresh prepares it again after you change something.
The report stays on your clipboard until another copy replaces it, so clear the clipboard if the device is shared.
From the command line
If you or your host use WP-CLI, wp bettershield diagnostics prints the same report, and it works even when you cannot reach the dashboard. The WP-CLI commands page lists the rest.
wp bettershield diagnostics
What to add yourself
The report describes the setup; it does not know what you did. Add, in your own words:
- What you did and what you expected, step by step.
- What you saw, with the exact message. BetterShield’s messages are specific, so the wording matters.
- Where you saw it, such as BetterShield › Protection › Hardening, or the sign-in page.
- What changed recently: a plugin installed or updated, a host or server move, a new proxy or CDN.
Before you write, check Troubleshooting. It is organized by the message you see, with the reason and the fix, and many problems end there.
Where to send it
| Question | Where |
|---|---|
| The free plugin: how something works, a problem, a suggestion | The BetterShield support forum on WordPress.org |
| BetterShield Ultra, your license or billing, or anything you would rather not post in public | BetterShield support; the reply comes to your email |
| A security issue in BetterShield itself | Report it privately, never in the forum; see Security |
A forum is public and indexed, so every answer stays there for the next person with the same question. That is a strength for how-to questions and a reason to be careful with anything private.
What it can break, and how to undo
Preparing and copying the report change nothing on your site, so there is nothing to undo. The only thing to manage is the text you copy: it is on your clipboard and, once pasted, wherever you put it.
If you pasted something you should not have, replace it straight away:
| What was shared | What to do |
|---|---|
| Your recovery link | Press Generate a new link on Protection › Recovery; the old one stops working |
| Recovery codes | Press Issue a New Set on Protection › Recovery |
| An assistant’s credential | Press Rotate on BetterShield › Agents › Connect |
| A password | Change it, then sign out that account’s sessions under Who is signed in on Protection › Login & Access |
| wp-config.php keys | Replace them with a fresh set; everyone signs in again once |
Never paste these in public
The report is safe to share. Other things are not, in text or in a screenshot:
- Passwords, including application passwords.
- Your recovery link, recovery codes, or an unlock link from a lockout email.
- Two-factor backup codes, or the setup code or QR code from your authenticator app.
- The credential an AI assistant uses to connect.
- The contents of wp-config.php, which hold your database password and keys.
Check it is working
- Press Prepare the Report and confirm the box fills with text beginning “BetterShield diagnostic report”.
- Scan it for your site address, an email address, a username or an IP address. None should be there.
- Confirm the last line says what was left out on purpose.
- Check the theme and plugin list, and decide whether the forum or a ticket suits you.
WordPress also has its own diagnostic screen. Tools › Site Health shows BetterShield’s open findings on its Status tab, and its Info tab holds a section called BetterShield: what it keeps about people, which describes records and holds nobody’s data. WordPress’s own sections on the Info tab are not BetterShield’s, so read them before posting them anywhere public. The Site Health documentation on WordPress.org explains the screen.
Recommended settings
We recommend preparing the report fresh each time you ask for help, since a copy from last month describes last month’s site. Read it before you paste it, add the exact message and the steps that led to it, and use a ticket rather than the forum if the plugin list is private. Keep your own recovery link and codes stored away from both.
Frequently asked questions
Does BetterShield send the diagnostic report anywhere?
No. It is prepared on your site and shown to you. You decide whether to copy it and where to paste it.
Does the report include my site address or email addresses?
No. It leaves out the site address, email addresses, usernames, IP addresses, keys, tokens, hashes and file contents.
Does it list my other plugins?
Yes. It names your theme and active plugins with their versions, because support often starts by ruling out a clash. Use a ticket instead of the public forum if you would rather not post that list.
Can I get the report without the dashboard?
Yes. Run wp bettershield diagnostics and it prints the same report.
Is the diagnostic report part of the free plugin?
Yes. It is part of the free BetterShield plugin on WordPress.org.
Conclusion
The diagnostic report gives support the facts about your setup without your secrets. Press Prepare the Report, read it, copy it, and add what you did and what you saw. If something private slips into a public post, replace it at once.
BetterShield is free on WordPress.org. The reference page is Prepare a diagnostic report, and Getting help covers the routes in full.