Squid

You're sure the log doesn't state "failed to import...."

Only if you edit an existing VM. On a new VM you are allowed to change the BIOS.

TY for the quick fix

You corrected too many capitalizations Getting update information... Installing update... plugin: updating: tips.and.tweaks.plg Warning: parse_ini_file(/etc/unRAID-version): failed to open stream: No such file or directory in Standard input code on line 4 ********************************************************* Open Files Requires Unraid version 6.4 or greater to run. ********************************************************* plugin: run failed: /usr/bin/php retval: 1 Not to mention that the fail notice states Open files and not Tips & Tweaks

Install CA Cfg Editor. Load /mnt/user/Pool/zenstates.py switch the Line endings from CRLF to LF (bottom left). Or, re-edit the file using Notepad++ (not Notepad) and do the same thing under Edit, EOL Conversion

In order for template changes to get pushed out to everyone during an update, the TemplateURL entry has to be populated in the xml That being said though, not all elements in the template will get updated (by design) The only ones that do is Support, Overview, Category, Project, Icon, and Config Updating automatically the repository entry is in effect running a different app and probably not something that should be allowed across the board.

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Do you have python installed? And did you make zenstates.py executable? ( chmod +x /mnt/user/Pool/zenstates.py )

Whether its needed or not I honestly have no clue. Until someone states definitively that no you should not be using it, then the test remains.

TBH, even with no additional apps running, I'd say 4G is the functional minimum

fixed

And yes, I would prefer to know about any and all issues. Not just the big ones.

I'm laughing... Keep 'em coming.

Have you been told yet? 😁

Should probably clarify why I hated the spinner on CA when it's a blank screen. CA is a ton faster (for various reasons) at getting its required information than say the plugins tab or the docker tab. Net result is that the built-in spinner would simply appear and more or less promplty disappear (because there's a delay built-in before it displays).

lol But at least now the problem is relevant to this particular thread and the lsio guys will be able to assist.

My problem with 6.6's spinner is that it just plain looks like crap when it's overlaid against CA's templates. So, for the entire 6.6 run thus far I've been having CA blank the display whenever the spinner would normally show up. And I still didn't like the spinner either, so I just went with the blank display. Finally decided the other day to just go with what I like, as I'm the one who winds up staring at CA day after day after day.

lol k. Low priority for me ( it took me ~2 hours prior to the release of 6.6 to find where CA caused the same thing on the footer - wasn't the most enjoyable experience of my life )

Delete the container. Then update CA and reinstall lsio. Then see if anything changes.

Running unRaid 6.6.3 on 2G of memory is really pushing it. I know that LT's website does state that is the requirement, but realistically that is the bottom of the barrel requirement.

Today's update is a priority update (in at least my opinion). In the course of testing a user's problem with a particular application, I found that CA was pulling the wrong application if 2 or more applications were named 100% identically. This was caused mainly by a minor change in the application feed to lower its bandwidth requirements. (in this case, it was qbittorent). Any issue which results in pulling the wrong application is treated as priority to me. This is fixed now, but the real change is what happens if you should resize your browser when its on CA. Much, much, much faster now at regenerating the display.

You'd need to submit a feature req for this (doubt it supports it). Until it gets implemented, you're probably borked

Question: When you edit the template does it state for repository mace/qbittorent or linuxserver/qbittorent? Just went to test your problem, and a regression error in CA wound up under this circumstance that it would always pull mace instead of linuxserver. Pumping out an update to CA right now.

If the container is in github but NOT in dockerhub (most are in both), then you have to manually build it yourself via the appropriate commands.

Because the host path mappings don't match between containers. The other two are using /data and qbit is using /downloads. Edit qbit accordingly then change its settings to store into /data Sent from my SM-T560NU using Tapatalk