Remote Access not successful

Plex Media Server Remote Access
1

  • machineIdentifier: 37973b185ea6bddbd4772435a73b5144c5fd91aa

    Since 2026-07-05, every registration publish is rejected, continuously, for days:

    MyPlex: sendMapping resetting state - previous mapping state: 'Mapped - Publishing'.

    MyPlex: mapping state set to 'Unknown'.

    MyPlex: Published Mapping State response was 422

    MyPlex: mapping state set to 'Mapped - Publishing'.

    [EventSourceClient/pubsub/...] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.

Same here, could use a reset :slight_smile: Thanks!

2

@atom5ive there is nothing wrong with your cert that I can see. Not being able to set up remote access is not mean the cert is the issue. Do you have the specific cert error ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, in your server logs?

3

Thanks @BigWheel No, I’ve got no cert-acquisition errors on my end. I grepped every log and there are zero Error acquiring new certificate / Failed to upload CSR / 429 lines.

The server is serving a valid cert right now: a Let’s Encrypt *.plex.direct cert, valid May 12 → Aug 10 2026. The only CERT: lines I have are benign local TLS handshake aborts from a device on my LAN (sslv3 alert bad certificate) nothing to do with acquisition.

What I’m actually experiencing: since Jul 5 my server randomly disappears from my account’s server list. At any given moment it’s missing roughly 60% of the time, it flaps in and out every few minutes. The effect is that anyone whose app does a fresh lookup during a “down” window sees no server / empty library, while anyone already connected keeps streaming, so it looks random, “some people can, some can’t.” I can’t see my own library from a fresh client either, even though the server is up the whole time and serves perfectly over a direct connection.

That lines up exactly with the one failing signature I do have, the mapping publish looping on 422, which never lets plex.tv mark the server reachable:

MyPlex: mapping state set to 'Unknown'.

MyPlex: Published Mapping State response was 422

MyPlex: mapping state set to 'Mapped - Publishing'.

[EventSourceClient/pubsub/...] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.

MyPlex: sendMapping resetting state - previous mapping state: 'Mapped - Not Published (Not Reachable)'.

So the cert path looks healthy, it’s specifically the mapping/registration publish returning 422, continuously since Jul 5. Is there any chance you could reset the mapping/registration record for machineId 37973b185ea6bddbd4772435a73b5144c5fd91aa?

Happy to pull any other logs that would help. Thanks for the quick look!

4

The only thing failing is the mapping publish looping on 422.

Honestly, I think I just tripped your anti-abuse. My server restarted too many times in a short span, an auto-updater plus a couple of Plex crashes on my end, and since Jul 5 every publish has been rejected with 422, so the server flaps in and out of my directory and shared users randomly can’t see it. I’ve since removed the thing that kept restarting it.

Could you reset the registration/mapping record for my server so it can publish again? machineId 37973b185ea6bddbd4772435a73b5144c5fd91aa. Really appreciate it.

5

you understand that would remove all access you would have given to folks?

6

Thanks @BigWheel really glad you flagged that, I had no idea a reset would remove all my shares. I share with ~5 people, so I’d rather not re-invite everyone if I can avoid it.

Two quick questions: (1) Now that I’ve removed what was restarting the server (deleted the auto-updater, and the crashes have stopped), will the mapping/registration throttle expire on its own if the server just stays up? (2) Is there any reset that clears just the publish/mapping throttle without touching my shared users?

If the only reset wipes shares, I’m happy to just wait it out now that nothing’s re-triggering it, just wanted to confirm that’s a reasonable path. Really appreciate the help.

7

Following up, it’s still flapping in and out and my clients keep losing the server, so I’d really like to get it cleared. If there’s a version of the reset that clears the mapping/registration throttle without wiping my shares, that’s my first choice, please do that whenever you can. If that’s not possible, go ahead and do the full reset; I understand it removes my shares and I’m fine re-inviting everyone. Either way I’d love to get it knocked out soon. Really appreciate the help.

8

the server record is removed. you will need to reclaim and such then reinvite folks

9

Thank you, working on that now. Was able to reclaim and add everyone back. Thank you for taking the time to support me, much appreciated.