# PMS keeps crashing **URL:** \ **Category:** Plex Media Server\ **Tags:** server-linux\ **Created:** [June 27, 2023, 1:36pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727 "2023-06-27T13:36:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 27, 2023, 1:36pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/1 "2023-06-27T13:36:55Z")
Server Version#: 1.32.4.7195 Player Version#: 4.108.0 Rocky Linux PC x86\_64 - build: linux-x86\_64 redhat - GMT 02:00 Linux version: 8.8 (Green Obsidian), language: en-US Processor: 24-core Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz Since a few days, my PMS is not working anymore. I had watched a movie the other night and when the next day I tried browsing my data, it could not connect to PMS. I tried several things: - downgrading to older version - optimizing DB through Plex SQLite - restarting my server, - checked permissions All of the above did not help. The symptoms are, that I can get PMS service to start after a reboot and I can access my server settings etc. But as soon as I try to browse a library, all the thumbnails stay blank and I cannot browe any media info or playback anything. And when I have tried to playback something, it looks like PMS is crashing. Cause then I cannot access server settings anymore either. I have been using Plex since day 1, but never experienced anything like this before. Has anyone ever had anything similar? [Plex Media Server.log](https://forums.plex.tv/uploads/short-url/8xkIR2Ns8XiMn5WzlM8ftXRbmqt.log) (1.0 MB) ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 27, 2023, 4:06pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/2 "2023-06-27T16:06:26Z")
You deleted the previous server instance and created a new one. ( I can see that on Plex.tv in your account ) It looks like, from the small log file you provided, (the ZIP file is better to share) that you forgot to force restart the Web browser (Control + F5) … It’s still looking for the old server & certificate. ```auto Jun 27, 2023 15:09:12.062 [140179069651768] DEBUG - Request: [192.168.1.1:49838 (Subnet)] GET /media/providers (12 live) #213 GZIP Signed-in Token (BeAtS) (Firefox) / Accept => application/json / Accept-Encoding => gzip, deflate / Accept-Language => en / Connection => keep-alive / Host => 84.192.91.106:32400 / Origin => http://localhost:32400 / Referer => http://localhost:32400/ / User-Agent => Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0 / X-Plex-Client-Identifier => vll39dymod33q0muxvlzdava / X-Plex-Device => Windows / X-Plex-Device-Name => Firefox / X-Plex-Device-Screen-Resolution => 1920x947,1920x1080 / X-Plex-Features => external-media,indirect-media,hub-style-list / X-Plex-Language => en / X-Plex-Model => bundled / X-Plex-Platform => Firefox / X-Plex-Platform-Version => 114.0 / X-Plex-Product => Plex Web / X-Plex-Session-Id => 8181f315-32fe-4234-8637-c7c12add26c8 / X-Plex-Token => xxxxxxxxxxxxxxxxxxxx / X-Plex-Version => 4.108.0 Jun 27, 2023 15:09:12.064 [140179069651768] VERBOSE - It took 0.0 sec to serialize a list with 1 elements. Jun 27, 2023 15:09:12.065 [140179124706104] DEBUG - Completed: [192.168.1.1:49838] 200 GET /media/providers (12 live) #213 GZIP 3ms 5460 bytes (pipelined: 9) Jun 27, 2023 15:09:12.070 [140179126815544] DEBUG - CERT: incomplete TLS handshake from 192.168.1.1:49896: sslv3 alert bad certificate (SSL routines) ``` > Jun 27, 2023 15:09:12.028 [140179124706104] WARN - [CERT] TLS connection from 192.168.1.187:49893 came in with unrecognized plex.direct SNI name ‘192-168-1-60.0be32a09665b47ae8f0cb1dbb7e08729.plex.direct’; using installed plex.direct cert ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 27, 2023, 5:03pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/3 "2023-06-27T17:03:00Z")
Ye, the new server was created by accident because the .xml was not mounted yet when i accessed the loopback address. I removed the newly created again and then restarted the server with the original preferences.xml. But behavious is the same. I just tried what you described in another topic: - stop pms - delete preferences.xml - delete cert file in cache - delete browser cookies etc - start pms - open loopback and configure server, it detected the configured libraries. Issue remains the same, as soon as I try to open any library or content, it just hangs, not thumbnails are displayed and after that I cannot access server settings anymore. Here is the ZIP [Plex Media Server Logs\_2023-06-26\_21-13-13.zip](https://forums.plex.tv/uploads/short-url/mll8c4DrhRouQQM7inbnUmVKIRj.zip) (234.8 KB) ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 2:49am UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/4 "2023-06-28T02:49:38Z")
You don’t have an IPv6 network. It’s IPv4. Access the server appropriately please. ```auto Jun 26, 2023 21:12:08.034 [140584552139576] DEBUG - Request: [[::1]:50670 (Loopback)] GET /media/providers (9 live) #53 GZIP Jun 26, 2023 21:12:08.035 [140584599051064] DEBUG - Completed: [[::1]:50670] 200 GET /media/providers (9 live) #53 GZIP 1ms 2362 bytes (pipelined: 2) Jun 26, 2023 21:12:08.037 [140584584473400] DEBUG - Request: [[::1]:50696 (Loopback)] GET /:/websockets/notifications (10 live) #55 GZIP Jun 26, 2023 21:12:08.037 [140584584473400] DEBUG - WebSocket: Performing handshake from origin http://localhost:32400 Jun 26, 2023 21:12:08.037 [140584584473400] DEBUG - Beginning read from WebSocket Jun 26, 2023 21:12:08.053 [140584547920696] DEBUG - Request: [[::1]:50614 (Loopback)] PUT /updater/check?download=0 (10 live) #57 GZIP Jun 26, 2023 21:12:08.053 [140584547920696] DEBUG - [Req#57] AutoUpdate: requesting check endpoint: /updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.32.4.7195-7c8f9d3b6, download: NO ``` Open the server via `127.0.0.1` instead of `::1` ? ```auto Jun 26, 2023 03:42:27.736 [139830586636944] DEBUG - NetworkInterface: Notified of network changed (force=0) Jun 26, 2023 03:42:27.736 [139830543412024] DEBUG - NetworkInterface: Watching for changes on the interfaces. Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - Detected primary interface: 192.168.1.60 Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - Network interfaces: Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1) Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - * 3 eno2 (192.168.0.167) (AC-1F-6B-BC-32-77) (loopback: 0) Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - * 4 br0 (192.168.1.60) (AC-1F-6B-BC-32-76) (loopback: 0) Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1) Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - * 3 eno2 (2a02:1810:9dab:3600:ae1f:6bff:febc:3277) (AC-1F-6B-BC-32-77) (loopback: 0) Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - Creating NetworkServices singleton. Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - NetworkServices: Initializing... Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - NetworkService: Creating new service. Jun 26, 2023 03:42:27.737 [139830586636944] DEBUG - NetworkService: Got notification of changed ne ``` ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 6:19am UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/5 "2023-06-28T06:19:55Z")
@ChuckPa I had it opened via [http://127.0.0.1:32400/web](http://127.0.0.1:32400/web) I keep seeing these cert errors… Box was freshly rebooted, first login to plex, straight to console and this is what I see. ![2023-06-28 10_01_32-beats.synology.me_4589 - Remote Desktop Connection](https://global.discourse-cdn.com/plex/original/4X/b/f/b/bfb8e6742514936114269d1e06cfb16ca7d158f4.png) I have refreshed the cert a few times already ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 6:25pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/6 "2023-06-28T18:25:56Z")
@BeAtS I just looked at your acount. I see where you deleted and recreated the server container a few times. One thing you must do is perform a Control+F5 forced reload when you do this. The reason for it is each server instance gets a new certificate. The log excerpt you show tells us the player (browser) is using the old certificate. ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 6:36pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/7 "2023-06-28T18:36:39Z")
But I open it in a Private browser each time… I had even deleted the cookies before etc. The strange thing is, that as soon as I try to open/list a library. The server hangs, and then I cannot enter settings anymore either. A while later, settings can be accessed again until I try to browse a library again… ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 6:55pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/8 "2023-06-28T18:55:10Z")
I need to know more about your LAN topography. What’s at 192.168.1.1 ? It’s acting like a player device Same question for 192.168.1.187 ? ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 7:27pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/9 "2023-06-28T19:27:48Z")
192.168.1.1 is my gateway 192.168.1.187 is the client I access PMS from (through SSH tunnel) 192.168.1.60 is the PMS server But even if I access the PMS via 192.168.1.60 on the .187, behavious is the same ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 7:41pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/10 "2023-06-28T19:41:05Z")
> [@BeAtS](#): > > 192.168.1.1 is my gateway My concern is that 192.168.1.1 (your gateway) is showing up as if it’s a client/player. That should not be happening. Is there a Proxy involved somewhere ? This isn’t behaving like a normal single-segment configuration If your browser is opening [http://127.0.0.1:32400/web](http://127.0.0.1:32400/web) then this should NOT be happening (IPv4 → IPv6 conversion) ```auto Jun 26, 2023 21:12:13.075 [140584573590328] DEBUG - Request: [[::1]:50614 (Loopback)] GET /web/index.html (9 live) #61 GZIP Jun 26, 2023 21:12:13.076 [140584573590328] DEBUG - [Req#61] Final path: "/usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/index.html" Jun 26, 2023 21:12:13.076 [140584573590328] DEBUG - Content-Length of /usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/index.html is 12383 (of total: 12383). Jun 26, 2023 21:12:13.076 [140584599051064] DEBUG - Completed: [[::1]:50614] 200 GET /web/index.html (9 live) #61 GZIP 0ms 12383 bytes (pipelined: 13) Jun 26, 2023 21:12:13.097 [140584547920696] DEBUG - Request: [[::1]:50614 (Loopback)] GET /web/3519-3519-35b03a3b034aaa63bb09-plex-4.108.0.32184-ffafb0d.css (9 live) #63 GZIP Jun 26, 2023 21:12:13.097 [140584547920696] DEBUG - [Req#63] Final path: "/usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/3519-3519-35b03a3b034aaa63bb09-plex-4.108.0.32184-ffafb0d.css" Jun 26, 2023 21:12:13.098 [140584547920696] DEBUG - Content-Length of /usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/3519-3519-35b03a3b034aaa63bb09-plex-4.108.0.32184-ffafb0d.css is 80610 (of total: 80610). Jun 26, 2023 21:12:13.098 [140584571480888] DEBUG - Request: [[::1]:50604 (Loopback)] GET /web/main-179-69d37121295f158388fa-plex-4.108.0.32184-ffafb0d.css (9 live) #5d GZIP Jun 26, 2023 21:12:13.098 [140584571480888] DEBUG - [Req#5d] Final path: "/usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/main-179-69d37121295f158388fa-plex-4.108.0.32184-ffafb0d.css" Jun 26, 2023 21:12:13.098 [140584601160504] DEBUG - Completed: [[::1]:50614] 200 GET /web/3519-3519-35b03a3b034aaa63bb09-plex-4.108.0.32184-ffafb0d.css (9 live) #63 GZIP 1ms 80610 bytes (pipelined: 14) Jun 26, 2023 21:12:13.098 [140584552139576] DEBUG - Request: [[::1]:50646 (Loopback)] GET /web/js/3519-3519-35b03a3b034aaa63bb09-plex-4.108.0.32184-ffafb0d.js (9 live) #54 GZIP Jun 26, 2023 21:12:13.098 [140584571480888] DEBUG - Content-Length of /usr/lib/plexmediaserver/Resources/Plug-ins-7c8f9d3b6/WebClient.bundle/Contents/Resources/main-179-69d37121295f158388fa-plex-4.108.0.32184-ffafb0d.css is 458076 (of total: 458076). ``` I am not going to pull the “not supported OS” card just yet but Rocky Linux is doing something I do not understand. Favoring IPv6 over IPv4 on the Internet is the standard – I get that. It should NOT be happening on the loopback adapter. What happens if you turn IPv6 support OFF in your network config ? The LAN is IPv4 – Everything should work without interruption. ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 8:09pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/11 "2023-06-28T20:09:53Z")
I had IPv6 support disabled already, the ::1 requests go away, but does not change the behaviour that the PMS is crashing/freezing. FYI, this configuration had been working without issues for almost 2 years. Nothing changed on the server nor on PMS, but it stopped working overnight. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 9:26pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/12 "2023-06-28T21:26:00Z")
> [@BeAtS](#): > > Nothing changed on the server nor on PMS, but it stopped working overnight. Nothing changed but it stopped working – Mutually exclusive statements. Something changed else it would be running. We need to figure out what changed. Clarify for me please ? Are we chasing Crashng/Freezing or are we chasing cert errors? ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 9:27pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/13 "2023-06-28T21:27:07Z")
We are crashing/freezing, I have no idea if the cert errors are related. ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 9:28pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/14 "2023-06-28T21:28:42Z")
Thanks, we’ll get the cert error but I agree crashing/freezing is more important. Have you run this to check and fix damage in the DBs (which will cause freeze/crash)? > **[GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server...](https://github.com/ChuckPa/PlexDBRepair)** > > Database repair utility for Plex Media Server databases - GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases I recommend the ‘stop auto start exit’ sequence ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 10:24pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/15 "2023-06-28T22:24:42Z")
```auto Automatic Check,Repair,Index started. Checking the PMS databases Check complete. PMS main database is OK. Check complete. PMS blobs database is OK. Exporting current databases using timestamp: 2023-06-29_00.08.09 Exporting Main DB Exporting Blobs DB Successfully exported the main and blobs databases. Proceeding to import into new databases. Importing Main DB. Importing Blobs DB. Successfully imported databases. Verifying databases integrity after importing. Verification complete. PMS main database is OK. Verification complete. PMS blobs database is OK. Saving current databases with '-BACKUP-2023-06-29_00.08.09' Making repaired databases active Repair complete. Please check your library settings and contents for completeness. Recommend: Scan Files and Refresh all metadata for each library section. Backing up of databases Backup current databases with '-BACKUP-2023-06-29_00.10.39' timestamp. Reindexing main database Reindexing main database successful. Reindexing blobs database Reindexing blobs database successful. Reindex complete. Automatic Check, Repair/optimize, & Index successful. Enter command # -or- command name (4 char min) : 7 Starting PMS. Started PMS ``` Issue remains the same though ☹ ![2023-06-29 00_26_38-Clipboard](https://global.discourse-cdn.com/plex/original/4X/e/0/f/e0f0a176cde4543d2d1c6c738896dc2dd90edbd0.png) ![2023-06-29 00_26_56-Plex](https://global.discourse-cdn.com/plex/original/4X/1/c/1/1c103ea8565d8d8670e2cc10466336e1bbe9445d.jpeg) ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 10:35pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/16 "2023-06-28T22:35:37Z")
Grab the logs ZIP please and attach. ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 10:38pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/17 "2023-06-28T22:38:35Z")
Since I cannot access the settings page now, what are the most important logs you need? Cause I cannot grab the ZIP from the troubleshooting page. ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 28, 2023, 10:59pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/18 "2023-06-28T22:59:03Z")
[Plex Media Server Logs\_2023-06-29\_00-57-42.zip](https://forums.plex.tv/uploads/short-url/ye51NysLSlYuH2u5TBAEpHWKaAw.zip) (517.1 KB) ---
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [June 28, 2023, 11:42pm UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/19 "2023-06-28T23:42:43Z")
I see a lot here. 1. I see two adapters. Is the default br0 correct ? ```auto Jun 29, 2023 00:57:14.944 [0x7f07f6284b38] DEBUG - [HCl#d] HTTP requesting GET https://v4.plex.tv/pms/:/ip Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - Detected primary interface: 192.168.1.60 Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - Network interfaces: Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1) Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - * 3 eno2 (192.168.0.167) (AC-1F-6B-BC-32-77) (loopback: 0) Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - * 4 br0 (192.168.1.60) (AC-1F-6B-BC-32-76) (loopback: 0) Jun 29, 2023 00:57:14.945 [0x7f07fd0400d0] DEBUG - Creating NetworkServices singleton. ``` This is what’s happening. Plex.tv is ignoring it because it’s hammering the cloud server. ```auto Jun 29, 2023 00:57:15.447 [0x7f07f6694b38] DEBUG - [HttpClient/HCl#18] HTTP/2.0 (0.1s) 422 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx (reused) Jun 29, 2023 00:57:15.447 [0x7f07f1d45b38] DEBUG - MyPlex: Published Mapping State response was 422 Jun 29, 2023 00:57:15.447 [0x7f07f1d45b38] DEBUG - MyPlex: Got response for 96714816d05da00aafa43b71a0c9130b17e2f0f1 ~ registered :0 Jun 29, 2023 00:57:15.447 [0x7f07f1d45b38] DEBUG - MyPlex: updating mapped state - current state: 'Not Mapped' Jun 29, 2023 00:57:15.447 [0x7f07f1d45b38] DEBUG - MyPlex: mapping state set to 'Not Mapped'. ``` You need to shut this down and leave it off for a few hours for Plex.tv to “cool down”. ---
**Author:** ![BeAtS](https://avatars.discourse-cdn.com/v4/letter/b/13edae/32.png) [@BeAtS](https://forums.plex.tv/u/BeAtS)\ **Post date:** [June 29, 2023, 5:32am UTC](https://forums.plex.tv/t/pms-keeps-crashing/845727/20 "2023-06-29T05:32:06Z")
> [@ChuckPa](#): > > You need to shut this down and leave it off for a few hours for Plex.tv to “cool down”. Shut the PMS service down? [Next page](https://forums.plex.tv/t/pms-keeps-crashing/845727.md?page=2)