18 minutes ago, Triplerinse said:

Yes I got one, it does say if you are running it on docker or nas you can ignore the email.

Awesome, I missed that part of the email! Good catch!

13 hours ago, Triplerinse said:

Yes I got one, it does say if you are running it on docker or nas you can ignore the email.

Indeed, as i just stated in the other plex support thread - As the email states, if you are using Docker then it's a No-Op, the problem is mine, and possibly it's even a No-Op for me too as i use AUR upstream, so as long as AUR fix any packing issues then we are all good :-)

I just updated the docker to the latest and am now unable to connect to my Plex. I am seeing a lot of same errors in the plex docker logs:

2026-03-15 00:26:00,026 DEBG 'start-script' stdout output:

Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)

2026-03-15 00:26:00,084 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23230706597968 for <Subprocess at 23230706484560 with name start-script in state STARTING> (stdout)>

2026-03-15 00:26:00,085 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23230706602048 for <Subprocess at 23230706484560 with name start-script in state STARTING> (stderr)>

2026-03-15 00:26:00,085 WARN exited: start-script (exit status 255; not expected)

2026-03-15 00:26:00,085 DEBG received SIGCHLD indicating a child quit

2026-03-15 00:26:03,089 INFO spawned: 'start-script' with pid 131

2026-03-15 00:26:03,094 DEBG 'start-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.

2026-03-15 00:26:03,300 DEBG 'start-script' stdout output:

Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)

2026-03-15 00:26:03,364 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23230707984208 for <Subprocess at 23230706484560 with name start-script in state STARTING> (stdout)>

2026-03-15 00:26:03,364 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23230707987792 for <Subprocess at 23230706484560 with name start-script in state STARTING> (stderr)>

2026-03-15 00:26:03,364 WARN exited: start-script (exit status 255; not expected)

2026-03-15 00:26:03,364 DEBG received SIGCHLD indicating a child quit

2026-03-15 00:26:04,365 INFO gave up: start-script entered FATAL state, too many start retries too quickly

Does any one else see similar errors?

Looks like the database got corrupted and I had to rebuild it. Now, all is back.

HW transcoding seems to be broken on the newest release of Plex (1.43.1.10611), at least for intel GPUs

Rolling back to binhex/arch-plexpass:1.43.1.10540-1-01 works fine

Can confirm that HW transcoding broke. Took a painful amount of time to diagnose with an nvidia gpu.

Edit: In my case it was Brave that was broken =(

Edited April 13Apr 13 by duckstin

On 4/11/2026 at 6:00 PM, kayjay010101 said:

HW transcoding seems to be broken on the newest release of Plex (1.43.1.10611), at least for intel GPUs

Rolling back to binhex/arch-plexpass:1.43.1.10540-1-01 works fine

Did you ever hear from anyone on this? I am running 1.43.1.10561 and it keeps telling me that an update is available. And when I do it, it does the download and unpack and everything. But then it doesn't update. Glad it's not working since HW transcoding is broke. Bur wonder if someone said anything to you.

12 hours ago, Greg Marcom said:

Did you ever hear from anyone on this? I am running 1.43.1.10561 and it keeps telling me that an update is available. And when I do it, it does the download and unpack and everything. But then it doesn't update. Glad it's not working since HW transcoding is broke. Bur wonder if someone said anything to you.

I've only posted this here, so apart from duckstin reporting the same issue (and then retracting it), I haven't heard anything.

Saw users on Reddit reporting the issue as part of the newest Plex update the same day I posted my comment here, so I assume we just have to wait for Plex to fix it themselves in the next update. But I haven't actively kept up with how that's going - as long as it's working for me I'm in no hurry to update. They might have already fixed it, I don't know.

I see some Reddit users reporting only 1.43.0 is "transcode safe" and all 1.43.1 updates are broken, but rolling back from 1.43.1.10611 to 1.43.1.10540 fixed transcoding for me ¯\_(ツ)_/¯

I think there's a lot of noise coming from some users not realizing the issue isn't affecting all hardware equally, from what I've seen only certain Intel GPUs are confirmed as having their transcoding broken by the update. But I don't know how widespread the issue is or anything, like mentioned, I just rolled back and haven't kept up with it

No idea about your update issue, seems like an issue with your unraid installation perhaps?

Edited April 23Apr 23 by kayjay010101

My binhex plexpass docker is stuck on Plex Media Server is currently running database migrations.
it has been several hour, what can i do?

My logs say this on loop:

2026-04-29 19:38:39,109 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23301248886704 for <Subprocess at 23301249254736 with name start-script in state RUNNING> (stdout)>

2026-04-29 19:38:39,109 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23301248887376 for <Subprocess at 23301249254736 with name start-script in state RUNNING> (stderr)>

2026-04-29 19:38:39,109 WARN exited: start-script (exit status 255; not expected)

2026-04-29 19:38:39,109 DEBG received SIGCHLD indicating a child quit

2026-04-29 19:38:40,112 INFO spawned: 'start-script' with pid 153

2026-04-29 19:38:40,122 DEBG 'start-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.

2026-04-29 19:38:41,123 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2026-04-29 19:38:41,468 DEBG 'start-script' stdout output:

Error: Unable to set up server: std::exception (N2DB9ExceptionE)

Edited April 29Apr 29 by Kaallis

I use the plex docker from linuxserver.io with a plex pass and the latest Plex version 1.43.1.10611 - HW-transcoding is working fine 👍

Edited April 29Apr 29 by Zonediver

On 4/29/2026 at 2:58 PM, Kaallis said:

My binhex plexpass docker is stuck on Plex Media Server is currently running database migrations.
it has been several hour, what can i do?

My logs say this on loop:

2026-04-29 19:38:39,109 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23301248886704 for <Subprocess at 23301249254736 with name start-script in state RUNNING> (stdout)>

2026-04-29 19:38:39,109 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23301248887376 for <Subprocess at 23301249254736 with name start-script in state RUNNING> (stderr)>

2026-04-29 19:38:39,109 WARN exited: start-script (exit status 255; not expected)

2026-04-29 19:38:39,109 DEBG received SIGCHLD indicating a child quit

2026-04-29 19:38:40,112 INFO spawned: 'start-script' with pid 153

2026-04-29 19:38:40,122 DEBG 'start-script' stdout output:

[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.

2026-04-29 19:38:41,123 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2026-04-29 19:38:41,468 DEBG 'start-script' stdout output:

Error: Unable to set up server: std::exception (N2DB9ExceptionE)

Restored a backup and I'm good!

I install recently UNRAID, and I'm keeping having an issue that on restart that ask to make Parity, and once completed and all seems work, I launch the Plex app and I got this , and I don't understand what I can do, and how to avoid the issue.

Looks like there’s a problem with this site

Firefox can’t connect to the server at 192.168.2.222:32400

Hi I am really struggling with my container right now. I am very much on the beginner side so bare with me. I believe my db is corrupted, so when I try to access the included DBRepair script by using the Plex container console I cannot get the script to stop the container. Is there another way I can stop the container but keep the console window running so I can use the script?

On 5/29/2026 at 9:38 PM, Aeonofgods said:

Hi I am really struggling with my container right now. I am very much on the beginner side so bare with me. I believe my db is corrupted, so when I try to access the included DBRepair script by using the Plex container console I cannot get the script to stop the container. Is there another way I can stop the container but keep the console window running so I can use the script?

it shouldnt stop the container, it should stop (kill) the plex process running in the container, if the container did actually stop you wouldn't be able to interact with the db repair script to repair your db, clear?.

23 hours ago, binhex said:

it shouldnt stop the container, it should stop (kill) the plex process running in the container, if the container did actually stop you wouldn't be able to interact with the db repair script to repair your db, clear?.

Yes that makes sense and I eventually got it to work. Unfortunately the script could not repair the db so I had to nuke it and start over

14 minutes ago, Aeonofgods said:

Yes that makes sense and I eventually got it to work. Unfortunately the script could not repair the db so I had to nuke it and start over

i would encourage you to consider installing Appdata Backup in CA.

30 minutes ago, binhex said:

i would encourage you to consider installing Appdata Backup in CA.

I did after this happened, lesson learned!