Amigaz

Having some issues updating the container. It says there's an update but it doesn't pull anynthing. When looking and the template I notice there's no repository adress, is this correct?

db-backup Simple question, leave this field black to backup all DB's?

Have encountered the infamous "Step 6 is currently in process. Please reload this page later" problem ... completely stuck 😞 (updating from 20.0.8 to 20.0.9) Thias happened when I used the web updater. I have seen people solve it be removing the .step files which I don't have and running the updater again using the cli instead. None if the OOC commands I've seen people use works either ... just get "Could not open input file: /config/www/nextcloud/occ" occ is missing from this directory. The path is refering to it but instead I can find occ it in the /usr/bin/ folder???? Would really appreciate if some kind soul could lend me some help 🙂 Edit: Managed to find and delete the .step file so I could re-run the updater thru the cli this time but it stil bombs with this: Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4 Current version is 20.0.8. Update to Nextcloud 20.0.9 available. (channel: "stable") Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-20.0.9.zip Open changelog ↗ Steps that will be executed: [ ] Check for expected files [ ] Check for write permissions [ ] Create backup [ ] Downloading [ ] Verify integrity [ ] Extracting [ ] Enable maintenance mode [ ] Replace entry points [ ] Delete old files [ ] Move new files in place [ ] Done Start update? [y/N] y Info: Pressing Ctrl-C will finish the currently running step and then stops the updater. [✔] Check for expected files [✔] Check for write permissions [✔] Create backup [✔] Downloading [✔] Verify integrity [ ] Extracting ...PHP Warning: require(/config/www/nextcloud/updater/../version.php): failed to open stream: No such file or directory in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 PHP Fatal error: require(): Failed opening required '/config/www/nextcloud/updater/../version.php' (include_path='.:/usr/share/php7') in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 Any ideas on how I can solve this?

Same problem here ... or when doing "check for updates" on the docker section it checks for updates forever.

Have ran into an issue. Installed this plugin yesterday to just use it locally. Now this morning I cannot access the web interface .. just get a "404", I don't know what has happened. Is there a way to "remove" this plugin now so I get back access to my server again? thanks The API seem to have contact and all my apps work perfectly

Works here too

Getting the same error after the latest update

Right now it seems like thw qemu system is "running away" on CPU cycles but my two VM's are idle (!!!!????)

Anyone?

For the 2nd time my Unraid server has 100% CPU load and most of my plugins and dockers are unresponsive. Last time (circa a week ago) it happened and I did a clean reboot then because I didn't have time to troubleshoot. This time I tried to troubleshoot but got stuck and would be grateful for help. This is what the top command shows, alkso attached the diagnostics. jj-unraid-host-diagnostics-20200517-1934.zip

Yay! Thanks alot for your help!

Everything is left unchanged like in ED's guide except I have changed Host port 1 and the network which is set to use my Let's Encrypt proxy network like in ED's guide

Hmmm ... there is actually no such thing that I can find. The configs I know of is the Letsencrypt proxy config, the docker template in Unraid. Can you point me in the right direction where I can find what you are looking for, thanks?

Thanks but it didn't work, why should I remove this folder?

Have followed Spaceinvader's guide here to setup OnlyOfficeDocumentServer but the container seem to malfunction, when I https to it via my web browser I'm greeted with this: And the logs: Any ideas?

Have followed Spaceinvader's guide here to setup OnlyOfficeDocumentServer but the container seem to malfunction, when I https to it via my web browser I'm greeted with this: And the logs: Any ideas?

Happy Pro license user here after switching from Hyper-V server 2016 about a year ago. Keep up the good work, guys! [emoji2]

Nope, did’t roll back to 6.6.7 Forgot to mention that I am not running on a Ryzen platform, I’m using Intel platform with a Xeon E5-2697v3

Same issues here with 6.7.0 and with 6.6.7 For me the vnc option to connect to the vm offers the most lagfree experience

eth0 is already a port of the bond along with eth1,eth2 and eth3

Anyone?

After adding a 4-port NIC into my system unraid seem to have decided to create a default route so that all traffic goes thru the built in NIC on the motherboard (eth4). I'd like to have the default route thru my bond .. is this possible? Can't seem to able delete or change anything in the settings (please see the image below)

^bump^

Have been using unraid for about a month now, started with version 6.6.7 and now i'm on version 6.7.0. I have a 4-port network card in my server along with two built in network interfaces on the motherboard so a total of six network interfaces ranging from eth0 to eth5 When I had started running unraid I teamed the four interfaces on my NIC cards to a static LAG (balance xor) and It has a fixed IP address, the two remaining network interfaces are not in a bond and was given fixed IP addresses Yesterday I looked in my router's traffic management interface and see that alot (maybe all?) of traffic from my unraid server seem to go thru one of the NIC's on the motherboard and not thru my NIC with the bond. I was gived the impression that unraid uses "eth0" for all traffic? I've looked at the unraid network settings and there's some odd looking route tables there that has been created by unraid., it almost looks like al traffic is routed thru eth5? Docker config. I'm quite novice when It comes to linux networking. I'd like all traffic (docker etc) to go thru the bond and eth4 and eth5 as management interfaces Hope someone can point me in the right direction, thanks

Interesting, have exactly the same issue here with my 1tb MX500 cache drive