dreadu

What I am wondering from the linked blog post: Coud a new user use f.e. "Starter" for 1 year, not renew for updates in the 2nd and pay for the updates in the 3rd year, or would he have to "pay" for the updates in the skipped year as well.

+1 would be nice for remote replication with friends- but I can't create an unlimited share for that kind of stuff

6.12.4 to 6.12.6 without a problem 👍

https://github.com/nextcloud/server/releases meanwhile 27.0.2 got releases. It's working now. Just updated mine

I had the same behavior. Updated yesterday(?) to latest (2.0.7 from two days ago) and could not connect to the GUI today. Did not check it yesterday. But it did not work neither with Fire Fox, nor Edge. Went back to 2.0.6 now and it is working again. Log looked exactly the same. Will try again with 2.0.8 I suppose. Regards /edit Due to the update from 2.0.6->2.0.7 it seems the underlying DB got updated -> reverting to 2.0.6 fixed the GUI, but the old version can't run backups with the new DB version already in place. As mentioned in the initial post: the message looks exactly the same: [migrations] started [migrations] no migrations found ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── [custom-init] No custom files found, skipping... [ls.io-init] done. And FireFox, Chrome and Edge all have "Unable to connect", "This site can’t be reached" or " Hmmm… can't reach this page" 😟 /edit #2 further details here https://github.com/linuxserver/docker-duplicati/issues/69

After playing around a bit I think you are fully correct... I changed the default unraid ports and created a new NPM on host network- but I can't create a new certificate, supposedly because the LTE router does use some IPv4v6 mode and does not realy have a decent public ip Also I went with host instead of br0 thanks to @mgutts great work here which I stumbled upon while searching for a solution. I guess my only way out is to await the mercy of my ISP, or hope my extraordinary termination will go through next week, so I can search a new one... Thanks a lot anyways and have a nice rest of the weekend

Hi there way smarter people than myself, I do have problem to which I can't find the solution on my own. Generally speaking my system works totally fine and here is how it is setup: If I access nextcloud.mydomain.com, my domainprovider gets the current IP automatically from my router and directs all requests to my router at my public IP. After that, I have portforwarding to forward all :443 traffic to my nginx docker in my custom "proxynet" network. So basically public_ip:443 -> unraid_ip:1443 (important part for later). Nginx now gets unraid_ip:1443 -> nginx_ip:4443 and in there I have set up a proxy host which forwards the port to unraid_ip:2443 which is the portmapping for nextcloud in "proxynet" again. So unraid_ip:2443 -> nextcloud_ip:443. Everyhing so far so good. I can access everything with nextcloud.mydomain.com and it is working fine, https and everything. Now to the problem... Thanks to my amazing ISP (haha...) I am stuck without internet for almost 2 weeks now. Since a few days, I managed to get my hands on an LTE router with a sim card. That way I do at lease have internet and can work again. But... Unfortunately the LTE router can only forward public_ip:443 -> anything:443 and I can't change it to the port mapping for nginx which is unraid_ip:1443. unraid_ip:443 is ofc already taken by unraid itself. Another problem is, even though I can access the server locally with IP and everything, my phone and desktop clients won't talk to the sever and don't sync files. I can't simply add a local dns record (my dhcp is pi-hole), because that can't change the portmapping as well. So my question is: Is there any way I can get the current work-around setup to work? I did try a second nginx docker in my mcvlan network, with its own IP to forward to. Basically nginx2_ip:443. I did not get it to work yet- maybe because of the same access problem that Joshwaaa described- but I did not yet look too far into that. Is my idea a possible solution at all? Should it work? Is there a way simpler one that I didn't think of? I'd be happy to read suggestions

Thanks for the quick fix! Seems to work again (as well in combination with the user scrip for different shared).

I got exactly the same issue. Same error 6.11.5 as well.

Low importance question here: I just noticed today (did work last week), that the link to the support forum seems to be wrong. It's pointing to https://unraid.net/forum/index.php?topic=50453.0 Would you mind fixing it, when you change the template the next time? As said before: not high prio, but simply convenient 🙂

Additional information from my side: When updating unraid from 6.11.0 to 6.11.1, I did not re-install the plugin and everything worked. When updating from 6.11.1 to 6.11.2 it did not work and after reading this thread, I re-installed it- without resolving the issue as mentioned in my prev. posts. After the provided fix, I updated the plugin without re-installing it + recreated the luns, iqn, etc. -> worked again, but I did re-install it before the fix, don't know if that changed anything

Thanks a lot for the quick fix @ich777! I can confirm, that the "Fix 6.11.2 - added missing libffi7 package" is working. But I can add: DNS vs IP did not change anything for me. I had to re-create everything in the "initiators" tab. I could re-add the existing fileIO images, even though they would not show in the "FileIO" tab.

Just fyi (I don't use it for important data yet, so not a huge deal). It worked fine when upgrating to 6.11.1 Today I updated to 6.11.2 and it does not work anymore. De- and re-installed the plugin, but did not change the behaviour. Both Status and Diags look the same = empty Devices, FileIO and Initiators look good, as far as I can tell, but my PC can't connect to it anymore. P.S. Expanding / shrinking and changeing write-back for existing fileio would be awesome, if possible at all /edit: add the traceback -> looks like he can't import ImportError: libffi.so.7

Hi johnjd, I don't know if you could fix your problem already or not, but I stumpled upon your question while having the same problem. So in case anyone else struggles again, I document what I did. As said in the very first post of the "[Support] Linuxserver.io - Nextcloud" thread (thanks to blaine07) You do have other options to upgrade. Simply use the terminal and it should work. For all steps in detail, you can see https://docs.nextcloud.com/server/latest/admin_manual/maintenance/update.html#using-the-command-line-based-updater . I used it to double check what the "occ upgrade" does. Hope I could help, even though I don't know why the GUI update fails

Thank you very much for that info! I just updated unraid from 6.9.2 to 6.10.2 and could not figure out why at least one CPU core was stuck at 100%! Did check terminal -> top and could only see COMMAND "gunicorn"- which I could not find anything related to unraid with google. And the user was 5050 (and the only process using it, which baffled me). Then I suspected docker (not runninv VMs currently). First test Plex was not successful, but luckily the second try with pgadmin4 did the trick. When stopping the docker the cpu dropped to ~2-7% instead of permanent 40-100% over all 4 cores. Then I checked the community application and found your post- which I find interesting- because I did not have this problem before the update. For anybody reading my post: here is the original pgadmin documentation https://www.pgadmin.org/docs/pgadmin4/latest/container_deployment.html#mapped-files-and-directories After your suggestion with sudo chown -R 5050:5050 pgadmin and starting the docker again, the PID with COMMAND gunicorn and user 5050 did return, but dropped to 0% CPU after a couple of seconds. I assume it tried to access its appdata folder and gut stuck in a loop to try again. Why this did not happen before the unraid os update is beyond me, but not it's fixed. Thanks again 👍