From e1e1cce1502f617d04b6b8f5b736fdd85d325e80 Mon Sep 17 00:00:00 2001
From: Calvin Leung Huang <1883212+calvn@users.noreply.github.com>
Date: Mon, 14 Jun 2021 12:50:43 -0700
Subject: [PATCH] docs: add troubleshooting sub-section on plugins (#11858)

* docs: add troubleshooting sub-section on plugins

* docs: fix grammatical error
---
 website/content/docs/internals/plugins.mdx | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/website/content/docs/internals/plugins.mdx b/website/content/docs/internals/plugins.mdx
index 7d696c736b..71527be59b 100644
--- a/website/content/docs/internals/plugins.mdx
+++ b/website/content/docs/internals/plugins.mdx
@@ -120,6 +120,27 @@ settings. Like Vault, plugins support [the use of mlock when available](/docs/co
 plugin executable in your [plugins directory](/docs/internals/plugins#plugin-directory) must be
 given the ability to use the `mlock` syscall.
 
+### Troubleshooting
+
+#### Unrecognized remote plugin message
+
+If the following error is encountered when enabling a plugin secret engine or
+auth method:
+
+```sh
+Unrecognized remote plugin message:
+
+This usually means that the plugin is either invalid or simply
+needs to be recompiled to support the latest protocol.
+```
+
+Verify whether the Vault process has `mlock` enabled, and if so run the
+following command against the plugin binary:
+
+```sh
+sudo setcap cap_ipc_lock=+ep <plugin-binary>
+```
+
 # Plugin Development
 
 ~> Advanced topic! Plugin development is a highly advanced topic in Vault, and