To find where %TEMP is - just start a windows command line session within a logged in session with same windows account as that which Plex Media Server.exe runs under and then do this to find the path
echo %TEMP%
I expect it to be pointing to
C:\Users\djkev\AppData\Local\Temp
I have looked at the logs which covered period Jul 12, 2022 17:27 to 22:05
I see that there was a lockup where the server was inaccessible. No evidence of any crashes but some deadlock that led to requests being queued up
This lockout started around 17:40 - soon after the launch of PMS at 17:27
You shutdown PMS and restarted it 20:09 - at that point there were over 1000 queued requests and the Plex Media Server started returning error code 503 to requests - the 503’s started at 18:24
The shutdown and restart at 20:09 happened within 1 second duration which makes me think you must have a script / automated action doing this.
So server was restarted at 20:09 and ran till 20:15 when it appears that you probably rebooted windows and Plex Media Server started again at 20:22
To investigate lockups / deadlocks, there is specific set of diagnostics which includes getting a list of connections through the loopback IP address and also forcing a process dump (previously specified here 503 Service Unavailable - Plex Media Server / Desktops & Laptops - Plex Forum)
I would like to send you a development build of Plex Media Server with a fix for a compiler bug that may lead to such issues and crashes - I expect to have that available sometime next week. That would be best option rather than go through the process of capturing the deadlocks diagnostics.
