Nyghthawk

No idea if I did that. I figured I’d start “from scratch” but ultimately the app data folder is still there. So there can’t be that much to do / change?

So I had been NOT upgrading to 6.9.2 due to hearing issues with updates. I forgot what unraid version I was on. I downloaded the unraid update a few days ago and then told my server to reboot to finish the update overnight. Wake up in the morning this is about 12 hour difference. Unraid server is not booting. I check the sever. It sees the usb. But won’t boot to the usb now. ive tried various ports for the usb. Tried letting it sit there and off for a bit. I have had this thing running for years. And latest uptime was just over 120 days. How can I fix this? Can I just take the usb out “backup” the files. Make a new bootable usb and put my configure files back in?? any help please. edit: just plugged usb into a regular windows pc. Loads to devices. But I cannot open it. Corrupted usb? Or is this normal? edit2: formatted new usb (with trial I’m assuming) seems to be booting up with GUI. I “hope” Unraid makes a random backup of the usb before updating. If it does where can I find it? If it doesn’t. What do I lose? Edit3: original usb seems dead. Dead. Dead. Can’t even format it on another PC. what are my steps?

Thanks didn't think of checking the docker hub, will look there (i looked at the git page and didnt see anything)

I guess its a misunderstanding on both parts. The first post is "old" before 5.11 came out, hence why "latest" was 5.10 at the time. Now that we are PAST 5.10 being the "latest" and "latest" now referring to 5.11, I was wondering if 5.10 was ADDED as a tag to force 5.10 builds, just like for example 5.9 forces just those builds. I noticed that the FIRST page being "old" and not updated. So I ask, does putting the tag 5.10 force a build to 5.10 or is there only the ones listed still on the outdated first post. latest - The most recent build version of the Unifi controller software, regardless of release train. (now being 5.11 thus skipping the ability to force 5.10) LTS - The most recent Long Term Support release. 5.9 - The most recent 5.9.x release. 5.8 - The most recent 5.8.x release. 5.7 - The most recent 5.7.x release.

I don't get what you are saying? I know the builds exist for up to 5.11.xx, but the tags FORCED a specific version (5.9, 5.7 etc), I didn't see any mention of forcing 5.10.xx as a build option, so I asked. What is wrong with that? I was checking to see if maybe it was ADDED as the latest is 5.11 now and when this was first posted, the latest was 5.10 with 5.9 being very stable.

didnt see any mention of it anywhere...

Does linuxserver/unifi-controller:5.10 work? right now running linuxserver/unifi-controller:5.9

does your calibre docker have an updated version? the RDP version is outdated also anyone get lazylibrarian to work well with the new libgen issues? Error fetching link data from libgen.io: Response status 503: service_unavailable always get that no matter what "mirror" i use. I can click the same link and click download myself WITHOUT getting this 503 error...and one of the best mirrors changed their layout so the parser does not work.

Just a thought, can you not point your Calibre database folder (or files it looks for) to the same Folder that your LL files download to? (I only speculate as I JUST am about to set this up, and you brought up the same valid question that I was thinking)

Nope does NOT work.

I think i just give up......seriously. Fuck Cox and their blocking of port 80 just moved everything over to cloudflare, setup DNS, able to install letsencrypt using DNS, gets certs, still NOTHING effing works

i put subdomain.domain.com pointing to unraidIP: PORT

huh? So in proxy manager, I add that whole thing as the name?

Port 180 forwarded to unraid:1880 and port 443 to unraid:18443 Proxy Manager ports are 1880 and 18443 respectively

so right now i have port 180 forwarded to my unraid server..... port 180 is open per your site you gave me.... so I cannot use proxy manager then? since it can only listen on port 80 correcT?