I have been running my Plex server for many years on Unraid without any major problems. Recently I noticed that I was only able to play content whilst in my house on my nVidia Shield, no other devices whether in the house, remotely, on wifi or ethernet would play content. Similarly, friends / family connected to my account also could not play content. I decided to ask Google Gemini for help and it was able to quickly diagnose and fix the problem with some commands. This appeared to work for a couple of days before the same problem came back.

I returned to Gemini to assist in fixing the problem once more and again it fixed the issue, but only for a day or two.

As I've gone to fix the fix the issue for a third time, I have gone down a crazy rabbit hole with Gemini trying countless different "fixes" but have ultimately ended up with a completely borked server that apparently has no options left at this point other than to start again from scratch. The actual movie, TV, etc files are all perfectly fine and I can play them when I access the network share via Explorer on my Windows computers but we are at the stage now where the Plex docker is running but cannot actually load up at all and is stuck in a loop with the following error repeating showing up in the Docker > Plex > Logs terminal.

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.3.9314-a0bfb8370/PLEX MEDIA SERVER/a8f51933-f4dd-4f55-e6c852a2-d63bd994.dmp
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.3.9314-a0bfb8370/PLEX MEDIA SERVER/ce9ef944-0838-4c0f-41ddd4ab-13a989f0.dmp
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.3.9314-a0bfb8370/PLEX MEDIA SERVER/c4f7a840-63b5-49e9-b21d76b4-561dec6a.dmp
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!

I eventually got tired of the failed sugestions by Gemini to fix things and thought it would be best to restore from a CA Appdata Backup from Dec 22nd as it was the oldest backup there available but this has also not worked and is giving me the exact same error as before the restore.

At this point I have absolutely no idea what to do. My server is many years old, 96TB with 80TB used, and I really don't want to lose myself and others' watch history as well as many of ther personalised metadata I have included for some of the movies / TV shows. Gemini is suggesting to basically start all over again and we can try to migrate the watch status info but I think at this point I need to stop trusting AI and some advice from real humans!

I am running Unraid Version: 6.10.0-rc4.

For my Plex docker, I was on:
Linuxserver.io version: 1.42.2.10156-f737b826c-ls287
Build-date: 2025-12-13T16:35:02+00:00

Gemini had suggested I change it so that I am forcing it to install / use:
lscr.io/linuxserver/plex:1.41.3.9314-a0bfb8370-ls253

However I have now set it back to download the latest version but this has not resolved the problem and am still getting the same error loop.

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.2.10156-f737b826c/PLEX MEDIA SERVER/d9b29020-a254-499b-f2c71fb8-d0425735.dmp
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.2.10156-f737b826c/PLEX MEDIA SERVER/c03ec40c-f6e3-4c6c-d0a6adb2-d69e9644.dmp
Starting Plex Media Server. . . (you can ignore the libusb_init error)
Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!

For anyone who wants to read through all of the Gemini logs here is our conversation history. Warning it's fairly long!

Please tell me I am not completely screwed and will be losing years and years of history / data. What can I do to salvage and fix this server?

Edited December 30, 2025Dec 30 by VisualHudson

... you need to add/used the docker mod install/add the sqlite3 application...

see: https://github.com/linuxserver/docker-plex/issues/425

*then use the database repair script by adding the github file to your Plex folder and console into the docker and go to the folder and launch the Plex repair script...

Review github:
https://github.com/ChuckPa/DBRepair
*this is the plex repair system script...

so make a folder location...
mkdir /mnt/user/appdata/github

git clone https://github.com/ChuckPa/DBRepair.git
cd DBRepair
chmod +x DBRepair.sh

we will then pass this folder info plex at a location...

next we need to edit the docker.

and add your folder with the needed script:

you will need to add this line to your plex extra parameters:
-e DOCKER_MODS=linuxserver/mods:universal-package-install -e INSTALL_PACKAGES=sqlite3

This will install the needed sqlite package to edit and use the plex documentation and script to fix load and mess with the plex database.

this will install the 3rd party application inside the docker see docker logs:


with the extra parm and the above script...

apply and start the docker.
next console into plex:





Move into the container folder per my picture I used /repair.
and run the db repair script.

cd /repair
./DBRepair.sh

And follow the prompts, this will keep the docker running but kill the plex application and run the necessary sqlite database commands to run clean and fix the plex database.

Edited January 1Jan 1 by bmartino1
Data - typo

otherwise, you will need to complete delete the appdata folder and start over and reimport / set up your media library once more...

Edited January 1Jan 1 by bmartino1

Well I take it that you're not using the information I've already talked about here.

So the only other thing I can recommend is attempt to reclaim the server by editing parts of the Plex XML file.

But since you're not communicating with what you tested, what you haven't tested, not posting diagnostics or other stuff. No info and not communicating. I can't assist you. We're not mind readers. There's no data here that we can go off of that. You haven't already tried and I needed to verify that you've actually ran the script properly to stop your Plex system to attempt a database repair

If you start the flex Docker does it still continue running even though it crashes in the server? If it doesn't continue to stay running then the whole docker is fubar and you've lost all your database information. It must restart...

Not enough info to assist to regulate other things where I'll gladly tell you some other secrets or side stop but again no communication good luck

I'm sorry to not have replied for the last few days, I've been away for New Year and only just getting back to check on things. I greatly appreciate your help and assistance. I want to do anything I can do to try to get the server back up and running as it was.

I cross-posted this problem on Reddit as well as on the Plex forums. A lot of people on Reddit also suggested using the DBRepair tool. Gemini had previously tried to get me to use it but it didn't work. A very helpful redditor spent all evening on Dec 30th trying various methods and tools to try to resolve the problem. He appears to be wayyyy more experienced in this sort of thing than I. I uploaded my database files to Google Drive, he ran them through DBRepair and different things - I don't quite even understand all of the work he so graciously offered to do.

I don't know if he ran every single database backup as I have quite a few from throughout December but he says that there was far too much corruption in the database files. We have managed to use an October 2020 backup of the server (from when I migrated from Windows to Unraid) to create a new database which HAS got Plex up and running as it should. It's a few days ago now so my memory is a little foggy but I do think in using this backup from 2020 we have started a new appdata folder but I'm not 100% sure on that if I'm honest.

However though Plex is now working using the 2020 backup, and has thankfully kept all metadata set before that date, it has come with a bunch of drawbacks like:

-I have had to re-scan and re-add all content, losing any manually set metadata after Oct 2020.

-All watch history since Oct 2020 has gone (yes watch history sync is turned on)

-All Plex in-app statistics since Oct 2020 have gone

-Friends and family shared library settings are all gone

-Plex is not using the exact same libraries but almost like identical copies of them (for instance if I load Plex on my phone it will say libraries are unavailable, but if I change it to the new server it works despite being all the info from Oct 2020 backup of old server)

I do use Tautulli which is mostly still up to date, only lost a couple weeks of data there because of the CA Restore I attempted. Tautulli is working exactly as normal, correctly recognising when things are playing and logging it to same watch history log as before. So I still have watch history / statistics there but I HATE that I've lost all the statistics and mainly watch history within Plex over the last 5 years. I really want to try to get that back!

For the sake of friends and family in particular, I would really like to get all of the old shared library settings back and using the exact same libraries so I don't have to deal with all the problems trying to get people setup with my server again.

I'm sure there is probably more upgrades and work to do, more ways to modernise and all that stuff. This guy has mentioned using Duplicacy? I know my unraid and some apps needs updating or replacing. But before I do any and all of those sorts of things I really want to try to get as close to getting my server back up and running exactly as it was a couple weeks ago.

I dont know if it will help at this piont to upload my Unraid diagnostic logs but I have attached them anyway.

I will link the guy that was helping me to this post and if he has an Unraid forum account maybe he can advise in better detail what we have done so far?

I'm super grateful that we've been able to salvage as much as we can but in an ideal world I feel like we are 95% of the way there, I really want to try to get back to the exact same server I was running just a few weeks ago. If you'd like to take a look bmartino1 I'd be happy to link you to my google drive with all the copies of the databases and stuff?

Edit: I don't know if there's some way to share the Reddit PM history so you can read through what was discussed? Well, apart from screenshotting the whole thing.

Edit 2: The guy from reddit has read through this thread and said this....

Yeah, I confirm I did run both DBRepair and used the Plex specific SQLite to export the DB (called a dump) into a new DB to try to reassemble. The DB passes and it says the restore was successful, but when you view the DB, you see big areas of corruption. We validated that it was not a problem with your system/docker/plex version because I spun up your db on my Unraid and it still failed. Totally open to try new ideas if anyone chimes in with something different. TL;DR: you tried the repair and it was too far gone.

Watch history wise and settings we can attempt to repair

tower-diagnostics-20260103-1222.zip

Edited January 3Jan 3 by VisualHudson

your atleast in a semi stable instance. because you have done a restore already you are now in that state. watch history is not saved taht far back and the sync feature is more for the server to send to plex not vise versa. That data is gone due otthe restroe.

we could have atempted recovery by reinstalling plex by keeping the orginal database which would require a new claim key but no different settings move file path and other.(as i ahve done for migrating between sytems with not wantign to mess with database naming and fixes over the years. diag don't give th full story.

since you were already able to run the repair tool any/everything that can be done remotely has been done you now in a staqble usable state and will have to take the data loss.

I mean, I do have all of these different backups from various points throughout December (including backups from before Gemini / me / this Redditor did anything to the server) so I'm open to trying to use them and doing whatever you think might return things back to exactly how they were?

I think we did try to reinstall Plex using all of the original databases and files, but I'd be willing to give that a try again now if you think that will work & if you could walk me through exactly what you think I should do given my current state? I think that's what you're trying to say we could have attempted?

According to this other guy, he says that the databases have corruption from even before Gemini / anyone else did anything to them which in a way makes me feel a bit better that it wasn't completely due to me using Gemini. But I'm not 100% sure if he tried every one of the database backups through the DB repair, so I don't know if it's worth trying them? But I really have no idea what I'm doing with that.

Plex is stable, yes. Though it doesn't like me adding the nvidia GPU parameters back into the docker settings and there's the other things I've spoken about.

Data loss is very annoying and frustrating, if there's you know of any way to recover that data that'd be great?

Edited January 4Jan 4 by VisualHudson

the problem is the resync back up and the data regenerated trying to resotre or mess form a working state wil cause problems even with some advnce things to atempt to recover not a gurantee nor a sucess but to recretae with teh same database... (as long as the media data didn't chang paths, all data would survie...

it not worth trying to restore form a restored point.

16 hours ago, bmartino1 said:

the problem is the resync back up and the data regenerated trying to resotre or mess form a working state wil cause problems even with some advnce things to atempt to recover not a gurantee nor a sucess but to recretae with teh same database... (as long as the media data didn't chang paths, all data would survie...

it not worth trying to restore form a restored point.

I'm sorry I'm really struggling to understand what it is you're trying to say here.

I also don't understand why it's not worth trying to use the backups when previously that's what everyone was saying to use?

the goal was to keep database data there were things we could have done to dump the sqlite file and or recreate with teh exisitn database

It not worth trying to do now as you are in a working stated restored vaia backup that will cause duplication of file sizes and be more a mess that could break as you dont' understand. beign muti split across other sites and being given mutiple other potenal soultions is whts confusing you. your better off ont he plex form and review the plex docs on teh database...

https://forums.plex.tv/

Plex Support

Support Articles Archive

Plex Support

Repair a Corrupted Database

Note: This article is for Plex Media Server version 1.23.2 and newer. If using an earlier version, see . Though...

any changes now can and will introduce dataloss and is not worth it since you have already corenlty have some resotreed working backup and function system your better off taking the data loss and moving on

6 minutes ago, bmartino1 said:

the goal was to keep database data there were things we could have done to dump the sqlite file and or recreate with teh exisitn database

It not worth trying to do now as you are in a working stated restored vaia backup that will cause duplication of file sizes and be more a mess that could break as you dont' understand. beign muti split across other sites and being given mutiple other potenal soultions is whts confusing you. your better off ont he plex form and review the plex docs on teh database...

https://forums.plex.tv/

Plex Support

Support Articles Archive

Plex Support

Repair a Corrupted Database

Note: This article is for Plex Media Server version 1.23.2 and newer. If using an earlier version, see . Though...

any changes now can and will introduce dataloss and is not worth it since you have already corenlty have some resotreed working backup and function system your better off taking the data loss and moving on

If the goal was to keep database data and I have multiple different copies of the database data, why don't we use those to "dump the sqlite file & recreate the existing database"? Like we can just swap the one of the old database files back in and try your fixes from there.

I am in a kind of working state yes but it's basically a new server. Ideally I want to restore / fix the old server and have it back as it was a couple weeks ago.

But yes it is confusing me having different people propose different ideas, as well as the fact that I'm really not a pro when it comes to Unraid / linux / terminal coding things. But i've come to these different forums trying to keep help from people like you guys who do know what you're talking about. Plus there's no way to know who or where I would receive support. Plex forums no one responded. On here only you have responded. I did get more responses on Reddit. But yeah I really just need someone who knows this stuff more than me to help me get back as it was a couple weeks ago.

First, I'm no expert in plex and given the time days and data when you were here but refused to post already doesn't sit well with me on attempting to help... then claiming x but never answering x...

Nor flowing this site's rules for support. still waiting for some answers... data, logs, diag etc...

I'm reluctant to assist further and continue so I will post 1 last time here and not be back!
Here are some of the steps and next steps on how I would have preceded (as i have gotten into weird situation and didn't want to lose database data that affected plex library movie posters and information...)

BUT! Based on your post and current information due to that data, you no longer have the state nor files form that state. and we would need the 1 sqlite db file... among others to guarantee data!... as You keep claiming a backup, but a backup is only as good as your restore and because your current state is not the same state I CAN'T GUARANTEE THAT THE SAME WOULD WORK OTHERWISE! THUS, the RISK IS TOO high to suggest nor attempt now...

AGAIN Per my first post, as you still didn't answer the initial question... when you were getting the error did the docker stay running?
*as this plays a big part on the step to acquire the database and data for a restore / recreate... STILL NEED/NEEDED THIS INFO!!! if the dbtool would work or needed other reapirs attempts.... if the docker was functional and have to go more manual ways...

... in plex docker formations regales of docker tag (which is also something else i need to know, reconfirm that you are you running plex official? linux server? binhex...

Regardless, you should have a appdata folder mapping /config
root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database# ls

Library/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database#

For me that here...

in this plex folder is the docker configuration and plex configuration for a plex library

and we would need to interact with files in this directory

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database# ls

Library/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database# cd Library/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library# ls

Application\ Support/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library# cd Application\ Support/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library/Application Support# ls

Plex\ Media\ Server/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library/Application Support# cd Plex\ Media\ Server/

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library/Application Support/Plex Media Server# ls

Cache/ Crash\ Reports/ Drivers/ Media/ Plug-in\ Support/ Preferences.xml Scripts/ Updates/

Codecs/ Diagnostics/ Logs/ Metadata/ Plug-ins/ Scanners/ Setup\ Plex.html plexmediaserver.pid

root@BMM-Tower:/mnt/vm-zfs/Dockers/Plex/database/Library/Application Support/Plex Media Server#

on unraid we can enable samba to use a client pc to interact with files...
IN my case this is unraid web terminal...

that said we want to interact with a few files here in same way...

first is the preferences file this is your pelx xml configurations. and we may need to remove some things from it for recreation and a plex calim latter. or fix the intinal issues...
(advanced but is needed...) IDK if you have the OG file...

and we would need to keep volume mounts the same as we would create a new docker with latest tag with out sqlite database


as my examples (as i'm using compose instead of urnaid docker template) my move data in plex will be /data
the data in the sqlite database will be pointed to /data/xyz for content (IF THIS DATA DOESN'T MATCH THEN IT WILL BE DELETED) and you will lose content in plex that cascades to more data loss. so now you may not have the needed pictures and other data!...

SO in a restore we need to confirm and keep data mounts! The reason for a new reclaim key is due to the sync data (WHICH IS NOW LOST) as you have been running in this half state and the old claim key data has synced that data to plex where that data is gone, and I have no guarantee that a sync/resync will restore that data now.

so now that we Know or volume mounts and we know the preferences xml location (appdata) we need to find and interact with the sqlite document...
I've already posted the support articles READ THEM!!! ask question on the PLEX SUPPORT FORUM or contact plex support direct!


out side of the database data ther is picture metada files..

this is noted int eh metadata folder

in side these folders are a break-down into 0-### folders and inside them are Strings of pictures ... this is the content referenced in your sql lite database data and what loads the pictures for your plex library content.

This would need to be restores in the new plex docker...

Similar with media.. This contains the written data that this is xyz content with xyz date and has xyz metadata with descriptions..

all referenced and are requred to be present in the new plex meda data as you should be looking at migration support article at this point and restoring a plex library ...


Now the main piece to look into sqlite access sql dumping and sql reestore...

in plugin support in databases, you should see a sqlit database file
"com.plexapp.plugins.library"

Here is the file the db repair tool touched fixed and attempted to make repairs.

Per your comments and previous communication, you let someone else take your files and run the tool for you instead of running the tool your self...

SO NOW You're IN A WEIRD STATE AND I CAN'T HELP YOU!

TO much unknown...

BUT YOUR GOAL IS IF YOU HAVE THE FILES! Especial a file copy backup!!! as PLEX WILL DELETE MISS-MATH CED OR NON-EXISTING DATA!!!

is to get theses files together and dump your sql database... then we can use tools, commands and other application to edit and open a sql file to reload your data.

all are advance things to do but are simple go to xyz and launch xyz

BUT AGAIN You not answering question, and your is a stable state where its not worth thing to move as you can get into worse database corruption and loss due to REUSING THE plex claim key ... AND have ALREADY OVERWRITTEN PLEX SIDE DATA!

You now stuck with what you have.

I would have preferred to seen your crash log, but you chose redit and multi post and acted instated of question and doing things your self nor GOING TO THE ACTUAL SUPPORT PEOPLE!!! (I'M NOT ONE OF THEM!)

Your PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.3.9314-a0bfb8370/PLEX MEDIA SERVER/c4f7a840-63b5-49e9-b21d76b4-561dec6a.dmp Starting Plex Media Server. . . (you can ignore the libusb_init error)

as there was problay something simple to remove, update or fix in the crash log:

BUT all of that is now gone I can't confirm no place you back into that state nor should you atampt less you face full database corruption and loss!!!

So, i'm sorry you acted without understanding to place yourself where you are now... I can only recommend you contact support:
https://support.plex.tv/

They will most likely have you delete the appdata folder out right and start over with a rescan...

I'm sorry you feel like I refused to post or didn't answer your questions. I posted the thread on Dec 30th. You initially replied on Jan 1st at 4am, I was out of the country. I replied as soon as I could trying to cover as many of the updates and answers as possible - hence why I included the diagnostics file as requested. As also mentioned, I'd be happy to share with you the copies of the databases as well as the crash logs, I have a bunch on Google Drive and can try to pull them from elsewhere I have backups. Admittedly things are a little all over the place now.

In regards to "when you were getting error did docker stay running", I have tried to explain this as best as possible before, as well as providing the Gemini chat log which explains everything I did before posting, but I will do so again. At this point I'm not entirely sure which error you are referring to though. At the timing of posting the original post, Plex docker was running and would give me the crash loop as included in the OP. PlexUI would not load. I could not connect to Plex via other devices. Unraid would show it was running but it was not usable in anyway as shown from the crash loop. Prior to involving Gemini or anyone else's help? Yes Plex docker was running until I was having all the playback issues and I would shut it down as per Gemini's instructions to do the jobs it suggested.

I mentioned in the OP that I am NOT running the official Plex container. I have been using the linuxserver.io container as I have done for the best part of 10 years or so since originally setting up the Plex server on Windows and then migrating to Unraid, following SpaceInvaderOne's YouTube videos. Before involving Gemini, I was on version: 1.42.2.10156-f737b826c-ls287 Build-date: 2025-12-13T16:35:02+00:00 though Gemini had suggested I forced used a slightly older, more stable version instead.

Yes I know how to access the Plex appdata folders via samba / Windows Explorer. You ask if I have OG preferences.xml file... Yes I should do. I've got an entire copy of the appdata folder through CA Appdata Restore, plus I've also got other copies of the Plex appdata folder itself as well as a copy of the the entire folder from 10am on Dec 30th. I feel like reading through the Gemini log would explain and answer all these questions about everything I did before posting asking for help. One thing of note, re-reading through the Gemini log myself now it does look like at some point I was able to successfully run the DBRepair tool from this message I sent to it:

DBRepairTool now appears to be completed...

Automatic Check,Repair,Index started.

Checking the PMS databases

Check complete.  PMS main database is OK.

Check complete.  PMS blobs database is OK.

Exporting current databases using timestamp: 2025-12-30_06.36.00

Exporting Main DB

Exporting Blobs DB

Successfully exported the main and blobs databases.

Start importing into new databases.

Importing Main DB.

Importing Blobs DB.

Successfully imported databases.

Verifying databases integrity after importing.

Verification complete.  PMS main database is OK.

Verification complete.  PMS blobs database is OK.

Saving current databases with '-BACKUP-2025-12-30_06.36.00'

Making repaired databases active

Repair complete. Please check your library settings and contents for completeness.

Recommend:  Scan Files and Refresh all metadata for each library section.

Backing up of databases

Backup current databases with '-BACKUP-2025-12-30_06.45.34' timestamp.

Reindexing main database

Reindexing main database successful.

Reindexing blobs database

Reindexing blobs database successful.

Reindex complete.

Automatic Check, Repair/optimize, & Index successful.

For all the people saying that's what I needed to do. But obviously didn't actually completely fix my issue as you can continue to read in the Gemini log... and it's why I ultimately ended up posting online.

I'm sorry you've completely lost me with talking about volume mounts, I don't understand what you're saying.

Whilst I was walked through the instructions through Gemini, reading through the Plex article on fixing a corrupted database, I can confirm (and you can see yourself in the Gemini chat log) that we did try all of these things - pragma, vacuum, reindex, etc.

Yes I did let someone else have a copy of my files and run repair tools on his computer. But again, this was after doing them myself with Gemini's help.

What questions am I not answering? We're kind of going all over the place here. I'm trying to answer everything possible.

To get Plex running as it is now I've had to use a new claim key, yes? But I've not removed old server from Authorised Devices and can still see it within Plex app. So I'm not sure if helps?

I hope that you can see that I AM trying here. I am doing my best. I'm not trying to be avoidant or dismissive. I am struggling to understand some of your spelling, as well as some of these commands going over my head, or yes getting confused because of different people trying to help, or forgetting things because it's taking like a week or two now. But I am eagerly trying to do what I can and I do appreciate your help. I know you say you are not an expert but you are much more knowledgeable than me when it comes to this. I really need someone who knows what they are talking about to spend time 1:1 with me to get this fixed in one go - that's largely why I used Gemini. But yes it stands we have Plex kind of working but not in the exact same way as it was and with various loses that I would like to try to recover.

Edited January 5Jan 5 by VisualHudson