diff --git a/content/issues/2022-08-24-plex.md b/content/issues/2022-08-24-plex.md
new file mode 100644
index 00000000..14bff331
--- /dev/null
+++ b/content/issues/2022-08-24-plex.md
@@ -0,0 +1,29 @@
+---
+title: 'Notification: Issues Following Plex Data Breach'
+date: '2022-08-24 12:00:00Z'
+informational: true
+affected:
+  - 'Notifications'
+  - 'plex'
+section: issue
+---
+If you have a Plex account (not via ODIC provider like Google/Facebook/Apple) you will have recieved an email from them notifying you of a recent data breach and advising you to reset your password and force a logout of all connected devices.
+
+Many users have found that after following these steps their Plex server no longer displays any of their libraries and may show an error in the container logs:
+
+```text
+#####################################################
+#   Login via the webui at http://<ip>:32400/web    #
+#   and restart the docker, because there was no    #
+#      plex token found in the preference file      #
+#####################################################
+```
+
+To resolve this issue, stop the container, edit `/config/Library/Application Support/Plex Media Server/Preferences.xml` and delete the following values if they're present:
+
+* PlexOnlineUserName
+* PlexOnlineToken
+* PlexOnlineEmail
+* PlexOnlineHome
+
+Then follow the [claim process](https://github.com/linuxserver/docker-plex#parameters) to add a claim token env and recreate the container.