After having the certificate reset, all was working fine till this morning when the Plex server is inaccessible via http://10.0.1.150:32400/web
The good news is the Shield can be pinged but I am reluctant to pull the power on it as last time it corrupted the DB, had to reset and then took weeks to set it up again.
WiFi:
Reply from 10.0.1.155: bytes=32 time<1ms TTL=64
Reply from 10.0.1.155: bytes=32 time<1ms TTL=64
Reply from 10.0.1.155: bytes=32 time<1ms TTL=64
Reply from 10.0.1.155: bytes=32 time<1ms TTL=64
LAN:
Reply from 10.0.1.150: bytes=32 time<1ms TTL=64
Reply from 10.0.1.150: bytes=32 time<1ms TTL=64
Reply from 10.0.1.150: bytes=32 time<1ms TTL=64
Reply from 10.0.1.150: bytes=32 time<1ms TTL=64
I am also able to map the Shield’s drives to my Mac and obtain all the logs which I didn’t post here for privacy reasons.
The Shield it self is obviously running, turns on other devices via CEC but no image appears on the screen + green light on top of it also doesn’t show.
good thinking @BigWheel - shield app via LAN gives “Unable to connect to 10.0.1.150”
can still ping the device but not showing up as media player on windows but can access internal drive and copy data from it. I am starting to think the external 1TB ssd is the issue as its not accessible.
Probably will end up disabling it access to NAS and pulling the plug while crossing all fingers…
OK I did a restart finally and you were right and I’ve just learnt something new - Plex has used up the 1TB external storage for metadata I presume. I never thought that was possible but guess it is. I think that solves the mystery?
Issue resolved thanks @BigWheel - external drive used for Plex server /metadata storage was full.
I think it would be helpful to include in Plex server setup doco perhaps here (Plex Media Server Requirements | Plex Support ) that Plex Server can use 1TB plus in storage of metadata.
The issue isn’t getting the storage, rather not knowing at the start how much may be required.