Looping on "Starting Plex Media Server" since migrated to new repository

Server Version#: Linuxserver.io version:- 1.43.0.10492-121068a07-ls295
Player Version#: 1.112.0.359-0d79a49f
Running on Ugreen Ugos Docker

Followed support article then getting loop on startup with:
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (::1) 32400 port [tcp/] succeeded!
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (::1) 32400 port [tcp/
] succeeded!
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (::1) 32400 port [tcp/] succeeded!
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (::1) 32400 port [tcp/
] succeeded!
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (::1) 32400 port [tcp/*] succeeded!
*
Player reports "Unauthorized Access”

Applied a new Claim Code with no change.

PMS now broken, should I perform a clean install and restart from scratch?

Help greatly appreciated

Can we please get a copy of your server logs to see what is going on?

Plex Media Server Logs_2026-03-14_17-24-47.zip (6.3 MB)
Thanks!

Your server is very active right now. Looking at your logs it only shows about 84 minutes of activity across all 6 Plex Media Server log files. The server is running and processing data, however I am not seeing any of the normal server initialization logs. Since you say this is a UGreen NAS, I am tempted to say give it a couple more hours/let it run overnight and then reboot it in the morning, wait 5 minutes and get a fresh set of logs if the issues are persisting.

Thanks, will do.

FYI we were running fine before the repository change announcement.

Logs collected just after restart.
Hopefully meaningfull
Why loop refers IP v6 constantly?
Can we disable that to return to IPv4?

Plex Media Server Logs_2026-03-15_11-50-54.zip (5.6 MB)

Ok, I am seeing your docker/NAS networking acting odd:

Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG - Network interfaces:
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 2 eth0 (192.168.1.100) (6C-1F-F7-B5-5F-78) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 5 br-35b78847736c (172.30.0.1) (02-42-1E-E6-F2-AE) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 6 br-3704c3aec973 (172.24.0.1) (02-42-72-27-78-F6) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 8 br-8ab4a8208c6c (192.168.32.1) (02-42-F6-72-41-51) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 9 br-b0741897cbe3 (172.19.0.1) (02-42-56-3E-A6-FA) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 10 br-1a1446d927c9 (172.26.0.1) (02-42-B0-AF-20-73) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 11 br-59b5593abbd5 (172.18.0.1) (02-42-A2-8F-FE-24) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 12 br-5d6d3323c049 (172.20.0.1) (02-42-E1-26-29-A7) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 13 br-ac0010427445 (172.25.0.1) (02-42-59-4C-FF-40) (loopback: 0)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
Mar 15, 2026 04:12:43.573 [139749978856248] DEBUG -  * 2 eth0 (2a01:e0a:c12:5810:e3dd:72ae:7dc:ec3b) (6C-1F-F7-B5-5F-78) (loopback: 0)

I am seeing 0.0.0.0 addresses, 192.x, and 172.x docker addresses ideally Plex should see one network interface. Right now its bouncing between them

This morning performed a docker compose up -d --force-recreate then on NAS:32400, app.plex.tv and Windows app we’re back up and running.
There’s still a persisting flow of
Connection to localhost (::1) 32400 port [tcp/*] succeeded!
in the container log.
Now looking on how to fix this loopback announcement.
To start with, will use arm64 image in place of amd64 that Plex chose.