@wRINkLe-sTiCk Same for you. See my earlier comment.
@anon18523487 Since the Password REstart my Plex server on my Qnap is dead and won’t even load.
1 Like
Thanks for this - I’d apt purged the server and reinstalled and it still wasn’t showing up when I went in via the 192.168 address, but this did the trick
@anon18523487 I did as suggested. When I enabled remote access I get the error Not Authorized you do not have access to this server.
Plex Media Server Logs_2022-08-24_18-35-37.zip (510.5 KB)
On my IOS device it says "User could not be authenticated. This IP appears to be having trouble signing in to an account (detected repeated failures)
I cant reclaim my server after resetting my password.
@anon18523487 I also disabled, waited 30, enabled, etc - still “unable to connect … securely” and iOS also can’t authenticate.
Same issue as everyone else. specially:
- No web access to PLEX server from my own account.
- Clients not able to connect to plex server, from WEB, Plex app (ios) or Firestick/TV apps
On the bright side the my own Plex App(ios) and TV app (Samsung) seem to be working once again.
Update: 20 hours later all services are back on line.
Same here.
From the logs:
Aug 24, 2022 19:52:20.814 [0x7fbe0936eb00] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error code="1003" message="API rate limit exceeded" status="429"/>
</errors>
Thanks for the info…
Yep certificate error…
TimeAug 24, 2022 20:09:23.836
LevelError
Thread5076
MessageCERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
i have been trying to fix my plex Remote Access but still not working , i can use as local it works good , can you please check my log thanks
@anon18523487 your workaround is not working for me. I assume you guys will eventually fix it on your end?
Bumping this as well. have 3 servers running, all have been reset multiple times, no conflicting ports, full access and the claim of “remote access” on internal network but as soon as I switch to an external network (usually 4g) I get the same “cannot make a secure connection”.
I’m assuming it’s just hitting the limits of the system with everyone resetting but good luck getting things figured out.
@anon18523487 I’m having issues as well. Everything works locally and using ROKU and Android apps. Having zero luck with browsers externally and smart TV apps (Vizio and Samsung). I tried disabling Remote Access, shutting down PMS for 5 minutes, then re-enabling Remote Access. Also tried shutting down PMS for 15 minutes, then restarting.
Plex Media Server Logs_2022-08-24_19-54-07.zip (1.8 MB)
I am also experiencing an issue after resetting credentials. The logs show:
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
I am grateful for the timely notice of the exposure, but really want to be watching media at the moment after a day of work. A sentiment I think we all share.
@anon18523487 I’m also having the same problems. I can connect locally, but getting the ‘Unable to connect securely’ message with any remote connection. The server says " Fully accessible outside your network" though. I did the disable remote access for 30 minutes, restarted the server and re-enabled remote access. The problem persists. I’ve attached my logs if that helps. Thank you!
Plex Media Server Logs_2022-08-24_19-59-34.zip (6.2 MB)
{edit: So it turns out only web browsers aren’t working - remote apps on Phones/Roku sticks, etc are working. Clearing browser cache/cookies did not help. So anyone trying to use a web browser has problems when using the https://app.plex.tv/ url. If we use a custom domain url to my server, it works fine (like http://domainname.net:32400/web/ ). Maybe that information will help others too, until this is resolved. }
I’m getting the API rate limit as well. no idea what happened. Followed directions, I haven’t been rate limited ever before, reset password, claimed server and now I’m stuck.
Can someone on plex’s side clear my IP from the rate limit? who do I DM for that?
Looks like there may be a few different issues in this thread at this point, original problem was that from the local server all appears well, remote access enabled and server is re-claimed, but some or all external connections are appearing to not work, or sporadically work depending on device type (specifically not working on the app.plex.tv webapp)
From what we gathered earlier in the day it just seems to be that there are countless people reclaiming, and trying to obtain certs at startup is a crap shoot. What worked for me was just restarting the PMS app a bunch of times per @anon18523487 , and waiting a few minutes in between each attempt. Eventually it did go through. I’m working off Windows Server 2019, but if the issue is your specific local PMS retrieving this cert at startup from the Plex company side of things, and failing because of request saturation, the OS may not matter much.
Looking at some other reddit threads and various FB groups it’s worked for others as well, some have had success also peppering in a toggle of remote access in between PMS restarts. I myself didn’t have to do the toggle, and it’s been working with no issue now across all users and seemingly all streaming devices (including app.plex.tv) for about the last 6 hours (17:30 EST). Good luck all!
Good morning, since yesterday when I reset the plex password and unlink the plex server devices included, I have the same problem as you, I can’t get plex to generate a new certificate, I don’t know why but plex only works for me with insecure connections, before all the reset only worked with secure connections my server.
Has anyone managed to solve the problem?
I have been enabling and disabling the remote service for hours and alternating with the restart of the server both the plex server and the computer and the same problem.
try to log off the server with the same result.
CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
Our servers are a bit busy now so it’s taking longer to respond to the server requests. Please be patient as thing should hopefully settle down soon.
@martigs Same issue as others. Please just wait a bit longer.
1 Like
That imagined that it was the same problem as the others because at some point it also indicates something about the api limit.
It will be solved automatically, I don’t have to reset anything, I imagine, right?
