Squid

Threw some duct tape onto the appfeed and v2 templates should be working now. Will swap out the duct tape for a real solution after work.

CA's fault. Wait til after I get off of work

Note: There is a current problem with the feed. Any V2 templates will not install correctly. You will see "false" under sections of the template which need to be removed. Namely, PostArguments, ExtraArguments. This will be fixed after work today.

Not there is not any webHooks supported at the moment

Just to get the obvious out of the way: Do you have internet access? Do you have the correct API key? Do you have the correct URL? Did you pay your bill to the indexer? Did you make any changes to your network setup / container that coincided with the problem?

Still no go. (Unless a reboot is required)

Take a note of the path mappings / ports / etc for that app. Remove the app, then re-add it via Apps and recreate your ports / mappings.

Update CA

Replacement appfeed up and running. So now I can easily make sure that everything is running smoothly You have to update CA in order for it to pick up the new & improved feed. This is pretty much a required update to CA as some apps / repositories will not show in the prior appfeed. 1st Change in CA brought upon by the new feed is that going forward regardless if the maintainers apply a "Date Changed" tag to their templates, any new templates that are seen will automatically be flagged as "New" and appear in the new/updated list. -

Available now (if you update CA). But, It won't start the service for me. Always shows stopped. Oct 2 19:19:21 ServerA root: plugin: creating: /boot/config/plugins/networkstats/networkstats.cfg - from INLINE content Oct 2 19:19:21 ServerA root: plugin: running: anonymous Oct 2 19:19:23 ServerA vnstatd[32070]: vnStat daemon 1.18 started. (pid:32070 uid:0 gid:0) Oct 2 19:19:23 ServerA vnstatd[32070]: Monitoring: docker0 (1000 Mbit) as0t5 (10 Mbit) vnet1 (10 Mbit) as0t1 (10 Mbit) as0t10 (10 Mbit) as0t8 (10 Mbit) gretap0 (1000 Mbit) veth4967533 (10000 Mbit) as0t4 (10 Mbit) virbr0-nic (1000 Mbit) vnet0 (10 Mbit) gre0 (1000 Mbit) as0t0 (10 Mbit) veth3a83667 (10000 Mbit) veth78066bc (10000 Mbit) as0t7 (10 Mbit) veth3e4db68 (10000 Mbit) as0t3 (10 Mbit) ip_vti0 (1000 Mbit) veth70a7165 (10000 Mbit) as0t11 (10 Mbit) tunl0 (1000 Mbit) br0 (1000 Mbit) virbr0 (1000 Mbit) veth4b0ff1d (10000 Mbit) ... Oct 2 19:19:23 ServerA vnstatd[32070]: SIGTERM received, exiting. Oct 2 19:19:27 ServerA vnstatd[32241]: vnStat daemon 1.18 started. (pid:32241 uid:0 gid:0) Oct 2 19:19:27 ServerA vnstatd[32241]: Monitoring: docker0 (1000 Mbit) as0t5 (10 Mbit) vnet1 (10 Mbit) as0t1 (10 Mbit) as0t10 (10 Mbit) as0t8 (10 Mbit) gretap0 (1000 Mbit) veth4967533 (10000 Mbit) as0t4 (10 Mbit) virbr0-nic (1000 Mbit) vnet0 (10 Mbit) gre0 (1000 Mbit) as0t0 (10 Mbit) veth3a83667 (10000 Mbit) veth78066bc (10000 Mbit) as0t7 (10 Mbit) veth3e4db68 (10000 Mbit) as0t3 (10 Mbit) ip_vti0 (1000 Mbit) veth70a7165 (10000 Mbit) as0t11 (10 Mbit) tunl0 (1000 Mbit) br0 (1000 Mbit) virbr0 (1000 Mbit) veth4b0ff1d (10000 Mbit) ... Oct 2 19:19:45 ServerA ool www[31175]: /usr/local/emhttp

You probably didn't copy over (or inadvertently erased) the contents of config/plugins/dockerMan/templates-user on the flash drive.

Tonight with the CA update switching to the different fees Sent from my LG-D852 using Tapatalk

Which one?

Its there in the apps tab User Scripts plugin

Nope. Sounds like your network is misconfigured somehow

Remind me next weekend

Then change the entry to be /mnt/user/system/libvirt.img

Nothing is stopping you from asking the question in the support thread. The reason for this is so that the people who are able to answer the questions don't have to look through the entire forum and read every post. Every question related to NextCloud (or any docker / plugin app) has its own specific support thread to make life a ton easier for the authors / maintainers.

If you don't plan on running any VM, then just disable the service You need to stop the service and switch to advanced view. But, once again if you're not running any VMs then simply disable the service altogether.

Sep 30 09:09:25 nasmedia emhttpd: shcmd (5821): /usr/local/sbin/mount_image '/mnt/cache/system/' /etc/libvirt 1 Sep 30 09:09:25 nasmedia root: /mnt/cache/system/ is not a file IMAGE_FILE="/mnt/cache/system/" Go to settings, VM Settings and change the libvirt image to point to the actual libvirt.img file instead of just the folder

Your mileage may vary. But, 6 years is an eternity in the computer world. (And the copyright on the manual is 2009 and the earliest driver still available is 2008)

VMs will work on damn near any motherboard / CPU out there. Passthrough of hardware however is highly dependent upon motherboard version, CPU, CPU microcode, Kernel running, etc and it will NOT work properly under every situation. This is completely out of Limetech's control. As others have said elsewhere for similar threads, you may need to update your system. unRaid is not a magic bullet that makes passthrough work perfectly on every piece of hardware out there. To be quite honest, you're lucky that it worked at all on a motherboard / chip that old.

This is one of the apps caught in the weird problems with the appfeed in community applications. Until the next release of CA and it's replacement application feed (next few days), it is unavailable from within CA.

Just a note that currently the application feed is having some weird problems. This has resulted in one entire existing repository being dropped, and a newly added one today not being added. Template maintainers may also on occasion see their templates not updating correctly. These problems have given me the impetus to finally take control of the appfeed and create a replacement, rather than relying upon a 3rd party to host and maintain it. The next revision of CA (due in a few days) will utilize the replacement as a default, with a fall-back to the existing one, and a final fall-back to legacy mode if necessary. As an aside, this also gives me the possibilities for future enhancements to CA that I've been thinking about for the longest time but have been unable to implement due to the design of the current feed. The upshot is that those users who due to their geographic location are blocked from utilizing the appfeed but are able to utilize legacy mode *should* have no problems connecting to the replacement. Downside is that it may take a second or two longer for CA to startup. In the meantime, if you notice that such-and-such application isn't appearing (or FCP is yelling at you), just ignore it (or yell back at FCP if it makes you feel better) - Andrew

It was the plugin manager getting confused (or you tried to update / install it twice). Pretty sure I know how to overcome it, but since it's a fairly rare occurance, it's never been at the top of my todo list due to the testing required.