Only EAC3: EAE timeout! EAE not running, or wrong folder? Could not read

Plex Media Server
1

Server Version#: 1.41.1.9057
Player Version#: 4.138.0

Some days ago. I can’t watch any videos with EAC3 audio.
I delete Caches and Codecs folders and restart Plex. Nothing change.

I check many post and nothing can help me.

Req#11c/Transcode/rjspigxdafp0sx3t6sok9kp7/c9315d10-325d-4f48-ba89-b3d0840c78ef] [eac3_eae @ 0x7f66bc8a6680] EAE timeout! EAE not running, or wrong folder? Could not read ‘/tmp/pms-2725970f-3ece-4fc6-948d-efaeff554e32/EasyAudioEncoder/Convert to WAV (to 8ch or less)/rjspigxdafp0sx3t6sok9kp7_477-0-0.wav’

[Req#134/Transcode/rjspigxdafp0sx3t6sok9kp7/c9315d10-325d-4f48-ba89-b3d0840c78ef] [eac3_eae @ 0x7f66bc8a6680] error reading output: -5 (I/O error)

[Req#138/Transcode/rjspigxdafp0sx3t6sok9kp7/c9315d10-325d-4f48-ba89-b3d0840c78ef] Error while decoding stream #0:1: I/O error

Plex Media Server.log (265.8 KB)

2

@FunPower_Owner

Thanks for your logs. That’s really helpful.

Here, you can see PMS can’t get its certificate to talk to Plex.tv (which you need for all the codecs , including EAE, to work correctly.

Oct 11, 2024 11:29:49.266 [139959285418808] DEBUG - Beginning read from WebSocket
Oct 11, 2024 11:29:49.268 [139959318989624] DEBUG - [HttpClient/HCl#20] HTTP/1.1 (0.1s) 429 response from PUT https://plex.tv/api/v2/devices/e208425a43917e662d2bb2ef0c885c0cc36c5ca6/certificate/csr?reason=missing&invalidIn=0 (reused)
Oct 11, 2024 11:29:49.268 [139959281199928] 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"/>

Every time you delete your docker container and create a new one, you get a new certificate (Plex.tv sees it as a new server instance)

There is a limit to the number of certificates you’re allowed during normal operation and you unfortunately exceeded that limit.

I have reset it for you.

Please RESTART the server. DO NOT create a new one.

3

Thx for your reply.

I stop Plex and wait 2 min.
Start Plex. Same error.

I delete Codecs Folder and Restart Plex.
Same Error.

Plex Media Server.log (378.7 KB)

4

I have the same problem. Is it possible to reset for me to?
I tried the same as TS. delete codecs and restart PMS but nothing helps.

5

I`m curious why this happens. I haven’t deleted the docker container. This has happened before and then deleting the codec solved it.

6

Here another Log and same problem without the error code=“1003”…

Plex Media Server.log (782.8 KB)

PLS i sure i not alone with this problem, Thx for your help.

7

HTTP 1003 is a non-base HTTP error code.
In this case, it’s Plex.tv sending the error that the API was contacted too many times over the interval

That’s why it says “API rate limit exceeded”.

There are several possible causes:

  1. The server is trying to get a new certificate
  2. The server is trying to test for & establish Remote Access
  3. The server wants Codecs & Drivers but, after the requested Codec/Driver is downloaded, the file can’t be saved. (This will be in the PMS log).

In all these cases, PMS has no choice but to try again.
You’ll see the error message in both the Console and the Logs but they do go by quickly so you might miss them.

Certificates and Drivers/Codecs not being saved, ESPECIALLY IN DOCKER, is almost always a file permission problem.

  1. You specified the UID/GID for the container to run as. That UID/GID must have valid permission access outside the container too.
  2. You (or the Container manager) specified the path to where /config is placed in the real filesystem.
  3. The problem is when UID/GID 1) Can’t see /config and 2) can’t create anything in /config – or anywhere below. (e.g. certificates / codecs)

Part of the Certificates issue is:

  1. PMS wants a certificate.
  2. Plex.tv gives it (unless its already asked for too many)
  3. PMS tries to save it.
  4. REGARDLESS – PMS will use the certificate it has, keeping it in memory.
  5. Next restart, PMS tries to load the last certificate – OOOPs, and it gets another LOL
8

@FunPower_Owner

I couldn’t find 1003 in that log. Might you have shared the wrong one?

9

I know you try to help me but i always install in same way and work perfectly.

Everything else work great. Just Plex stop working 2 week ago.

Pls. Just tell me what to do.

Thx

10

Let’s rewind a bit?

Given this is the fundamental error –

Could not read ‘/tmp/pms-2725970f-3ece-4fc6-948d-efaeff554e32/EasyAudioEncoder/Convert to WAV (to 8ch or less)/rjspigxdafp0sx3t6sok9kp7_477-0-0.wav

In your docker container config, where is /tmp pointing to?

11

never touch

/tmp

12

Now for the fun part.

  1. Make sure PMS DEBUG logging is enabled, VERBOSE logging is disabled. SAVE if changes made

  2. Restart PMS

  3. Let it sit completely idle for 3-4 minutes (I want to capture the startup sequence)

  4. Download the logs ZIP file

  5. Attach that ZIP file here.

13

image
image825×293 102 KB

Zip log in 2 min

14

so that’s your container’s /tmp. Understood. :slight_smile:

15

in /tmp

image
image834×249 112 KB

Plex Media Server Logs_2024-10-11_17-53-55.zip (2.7 MB)

16

@FunPower_Owner

Q: You’re running a docker container inside a VM ?

Which platform?
Which Hypervisor?

Q: Do you also have the PMS installed from the SNAP store or only the Docker image?

17

VM

Promox/ubuntu 20.04
Docker. I use GitHub - dockserver/dockserver: Docker + Traefik with Authelia and Cloudflare Protection

18

I use that for many years and about 2 week ago. Broke…

19

Ok,

PMS on Proxmox → Common KVM VM ------ makes sense and works. (Even I can do that. hahaha)

No idea how to make that other monster work.

What does it do?

20

Just help you install everything correctly.

Plex is in: /opt/appdata/plex