From what I know of the Shield server app, it will usually fail like that when there’s a permission problem accessing the storage where you are keeping the metadata. ( A USB drive ? ).
Please re-check the Nvidia Shield’s permissions to make certain those didn’t reset during the uninstall/reinstall process. I think it will remove permission after uninstalling.
(A Shield Experience 9.x change)
Thank You!
@ChuckPa, I just tried to restart and I have everything back to normal, but I am still unable to connect to ‘Shield’ securely. I tried a new browser and fresh restart as well.
Is it only complaining about securely but connecting otherwise with ‘http://’ from a private browser window ?
@ChuckPa, yes. It is only complaining about connecting securely. If I turn it off, then I get that it is unreachable, but that is why I figured the problem is on the Shield, since the web is able to tell the difference of what state it is in.
Please confirm :
@ChuckPa, yea. Both devices are on the same subnet and the subnet address is RFC-1918 compliant.
There was a problem with Plex.tv throughout the afternoon,
Would you mind restarting all the Plex apps and retesting?
Just restarted and tested, but I am still getting the same result.
If you close your browser (all windows)
Now open fresh,
immediately open an Incognito (private) window
In that private window , open the Shield by its LAN IP only (http://lan.ip.of.shield:32400/web)
Does it give you:
Hello, after a password reset, connected devices sign-out, then reclaiming, my “Plex Server Log” is full of the getting the “[14332] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429” and “error code=‘1003’ message=‘API rate limit exceeded’ status=‘429’” errors. I also changed from Docker network settings a couple of times (network=host versus own network) to test some stuff. Might this be causing this limit to be reached? If so, I’ll stick with network=host in the future.
Could you please reset my cert as well? Thanks!
I have reset your certificate.
You chewed through a bunch of resets there 
Please restart the server.
@ChuckPa, thank you so much. It finally worked. I accessed it through the ip and it worked. I tried that before already, but I’m sure all the troubleshooting and resets nudged something so that I could access it. Thanks again for your help.
Thank you very much! All is working correctly now. Yea, those resets…was troubleshooting some Ansible stuff triggering a lot of redeployments of Plex as a result. It’s fixed now 
I am getting the same error, cert expired today.
HTTP error requesting GET https://104-163-187-191.98598031246e41f397b727036f5a77fb.plex.direct:32400/identity (60, SSL peer certificate or SSH remote key was not OK) (SSL certificate problem: certificate has expired)
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
Works fine on computer with the plex player, but mobile devices have no love. 
Edit: Seem to have solved the issue myself by delting the cert-v2.p12 file from the server and restarting the server.
Edit2: Deleting the .p12 file let my mobile devices connect again, but I am still getting the following API rate limit exceeded error:
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
Soooo…what to do?
@ChuckPa anyone at Plex able to look at my cert issues?
Need mine too cert reset please
Apologies… I didn’t get a notification. Your cert has been reset.
Restart the server
Your cert was new 2 days ago. There are no errors showing.
What indications do you have of needing a cert?
Do you have the logs available please
No worries, all good, restarting shortly.
Is there something I can do on my server to prevent this from happening again?
From what I saw, PMS had made multiple requests then got stuck in a “GENERATING” state due to getting stacked up with so many requests
Without seeing your logs, I’d be making blind suggestions however,
Make certain the permissions in the “Plex Media Server” directory are as they should be.
When in doubt, if you’re running stock configuration (default user plex, etc)
then sudo chown -R plex:plex /var/lib/plexmediaserver just to make certain something else didn’t compromise your PMS storage. PMS can be running while you do this.
