Server Version#: 1.43.3.10896-cb3ebc72d
My Plex server certificate is missing and Plex cannot get a new one.
The log shows:
CERT: Certificate did not exist, fetching a new one.
Failed to upload CSR: 429
API rate limit exceeded
Could someone please reset the certificate/CSR rate limit for my server so Plex can request a new certificate?
For several weeks, your server has been requesting a fresh certificate almost daily. Such behavior will lead to a rate limit.
It implies an issue on your side. Usually a problem with access permissions or a locked certificate file. Ensure that the whole plex data folder is accessible to the Plex server container with full read/write permissions. Maybe manually delete the file cert-v2.p12 from the Cache subfolder.
Do also verify that you don’t have a cronjob, which is emptying out the cache folder daily.
yes, I’ve found the issue and removed it before I messaged you guys, but didn’t mention it.
Please stop and restart your server now.
Done.
I stopped Plex completely, confirmed it was inactive, and then started it again.
The certificate issue is now fixed. The new CSR request returned HTTP 204 and Plex successfully downloaded a new cert-v2.p12.
However, Remote Access is still showing as Not Mapped.
UPnP itself succeeds:
NAT: UPnP, mapped port 14093 to 10.2.XXXX:32400
PublicAddressManager: Mapping succeeded for 10.2.XXXX:14093
But Plex then repeatedly logs:
MyPlex: Published Mapping State response was 422
MyPlex: mapping state set to ‘Not Mapped’
Could you please advise on the 422 response?
Where is the machine located?
10.x.x.x is not a public IP. You will need to
Thanks. To clarify the setup:
The Plex server is running in a Proxmox LXC on my home LAN.
The 10.2.0.201 address shown in the log is therefore the private LAN destination of the UPnP mapping, not my public IP.
It also seems that Remote Access is intermittent rather than permanently broken.
For example, at 12:53 Plex reported:
MyPlex: mapping state set to ‘Unknown’
MyPlex: mapping state set to ‘Not Mapped’
MyPlex: Published Mapping State response was 422
Then at 13:00 Plex tried UPnP again and succeeded:
NAT: UPnP, mapped port 14093 to 10.2.0.201:32400
PublicAddressManager: Mapping succeeded for 10.2.0.201:14093
NAT: UPnP, public address is [public IPv4 redacted]
MyPlex: mapping state set to ‘Mapped - Publishing’
MyPlex: mapping state set to ‘Mapped’
At 13:08 it briefly changed to Unknown / Mapped - Publishing again, and then returned to Mapped.
So the UPnP mapping itself does work, and Plex is able to detect the real public WAN address, but the Remote Access state appears to go up and down during the day.
Could the repeated HTTP 422 responses be related to this intermittent behaviour, or is there something else in the network setup that I should check?
Edit: looks like the same issue now as was reported in Remote Access broken since ~Aug 16 — every publish rejected with 422 (same symptoms as thread 940388
From where do you draw this conclusion?
Is UPnP even allowed in your router settings?
Have you created a manual port forwarding in your router? If you did, have you inserted its public port number into the Plex configuration?
Thanks.
I draw that conclusion from the Plex Media Server logs themselves.
At 13:00 PMS logged:
NAT: UPnP, attempting port mapping.
NAT: UPnP, found device http://10.2.0.1:... with private address <10.2.0.201>
NAT: UPnP, usable device
NAT: UPnP, mapped port 14093 to 10.2.0.201:32400
PublicAddressManager: Mapping succeeded for 10.2.0.201:14093
NAT: UPnP, public address is [public IPv4 redacted]
Immediately afterwards it changed through:
MyPlex: mapping state set to ‘Mapped - Not Published’
MyPlex: mapping state set to ‘Unknown’
MyPlex: mapping state set to ‘Mapped - Publishing’
MyPlex: mapping state set to ‘Mapped’
UPnP is enabled on my UniFi Dream Router.
I do not have a manual port forwarding rule for Plex.
In Plex, “Manually specify public port” is also disabled, so Plex is currently relying entirely on UPnP and the external port is assigned dynamically.
The confusing part is that this succeeds and Plex reaches “Mapped”, but at other times it changes back to “Not Mapped” and I see repeated:
MyPlex: Published Mapping State response was 422
So I am trying to understand why the state is intermittent even though PMS is able to create the UPnP mapping successfully.
The result is an invalid state though. Because 10.x.x.x adresses cannot be a public server address. Which may be why plex.tv is throwing out this mapping soon afterwards.
Thanks. I think we may be talking about two different values in the log.
I am not interpreting 10.2.0.201 as the public server address. That is the private LAN endpoint of the UPnP mapping.
PMS logs the public address separately. For example, at 13:00 the sequence was:
NAT: UPnP, attempting port mapping
NAT: UPnP, found device http://10.2.0.1:... with private address <10.2.0.201>
NAT: UPnP, usable device
NAT: UPnP, mapped port 14093 to 10.2.0.201:32400
PublicAddressManager: Mapping succeeded for 10.2.0.201:14093
NAT: UPnP, public address is [public IPv4 redacted]
Immediately afterwards:
MyPlex: mapping state set to ‘Mapped - Not Published’
MyPlex: mapping state set to ‘Unknown’
MyPlex: mapping state set to ‘Mapped - Publishing’
MyPlex: mapping state set to ‘Mapped’
So PMS does appear to obtain the actual public IPv4 address separately.
The reason I am confused is that this works for a while and reaches “Mapped”, but at other times the same server returns to “Not Mapped” with “Published Mapping State response was 422”.
If the “Mapping succeeded for 10.2.0.201:14093” line should contain the public IP instead of the private destination, please let me know, because I may be misunderstanding what that specific Plex log field represents.
UPNP port mappings are temporary, Plex will read it but not refresh it. If your LXC isn’t using DHCP for it’s address the Router will drop it. Varies from router to router but anywhere from 3 to 10 minutes.
For a stable port forward it is best not to use UPNP.
okay, I’ve changed it and will monitor it. Thanks!
