dreadu

As a quick update: Notes app got an update as well. At first glance it seems to work fine now. Mail also got a few updates the last weeks and seems to be stable as well. Only thing still not working is the photos app widget and "on this day". As well as there are a few unnecessary errors that could be warnings or info, not not really an issue- except filling the logs. GitHub[Bug]: Logs filled with A non-numeric value encountered a...⚠️ This issue respects the following points: ⚠️ This is a bug, not a question or a configuration/webserver/proxy issue. This issue is not already reported on Github OR Nextcloud Community Forum (I'...GitHub[Bug]: Make nullable explicit to silence STDERR message ·...⚠️ This issue respects the following points: ⚠️ This is a bug, not a question or a configuration/webserver/proxy issue. This issue is not already reported on Github OR Nextcloud Community Forum (I'.../edit Update #2 With 32.0.3 photos app (esp. "on this day") also works again

I waited for 32.0.1 with my upgrade from 31- but still encountered a log of problems. The notes app floods the log with warning if enabled. Mail app (and others) randomly showed 404 when trying to use them. Phots has a problem with the widget breaking the dashboard. I was using "on this day" on the dashboard and had to remove it. Also "on this day" does not display anything when trying to use it in the app itself. New had a few problems as well. Tried a couple of things. Disablind, uninstalling and re-installing mail + news seems to have solved the 404 issues, but the photos widget and notes are still haveing issues Next time, I'll wait for X.0.3 at least...

Thanks all for the helpful tips. I did change my docker to use explicit tags (same as I did prior with postgres and other containers, but somehow never for NC). Just updated to "linuxserver/nextcloud:30.0.1" and everything seems to work fine. 👍 Regarding the following screenshots: I just noticed the same dirty table reads as well, during the update from 30.0.0 to 30.0.1. No more after the update finished. A bit curious, because they are debug + info entries, but my log level is default = 2 = WARN (did event check my config/config.php) Not really worried by that, if it simply logs more during the update. But there are 2 other issues I still have (in NC30.0.0 + 30.0.1): 1st Setup Warning that I do have for quite some time: If I check my browser though (FireFox) I do get strict-transport-security: max-age=63072000;includeSubDomains; preload I do use https://hub.docker.com/r/jc21/nginx-proxy-manager and as far as I can tell, everything seems to be set up correctly. https://docs.nextcloud.com/server/30/admin_manual/installation/harden_server.html#enable-http-strict-transport-security says preload is recommended, I don't use sub domains. The max age is "at least 15552000, in my case 63072000. I don't realy see why I get this error. Or do I have to dig into the Apache VirtualHost file, even though I run the nginx and my browser has the correct header? 2nd Error: I do get the same "Error occurred while checking server setup" message in the overview. What I don't understand is, that it only happened after I upgraded from NC29 to NC30. Further more I do have 2 separate users. 1x Admin, 1x my own user without admin privileges. The admin user does work fine. My non-admin user gets the error message. I did create a user group called "maintainers", added non-admin user to it and gave administration privileges for "Overview - Secruity & setup warnings" to that groups. That way, I did not have to login with my admin user all the time to get some notifications. Worked since that option was added, until I upgraded to NC30. No idea why it works with 1 user, but not with the other. The second one does not bother me too much tough- I simply removed the administration privilege. I am more baffled by the first one. Apart from that - have a nice weekend everyone

That is indeed a great point. I did have some issues in the past though, because I simply use "linuxserver/nextcloud" -> latest. Potentially not the greatest idea on my side. Before the updater.phar change it did not bother me too much, because I could simply upgrade myself. Now I can't see directly when the new major will be applied if I update my container. F.e. with postgres, I simply use "postgres:16" for the latest minor release in current major and don't worry about it. If I check the NC tags, I can see "29.0.7 as well as "30.0.0". (I don't know though what the additional tags like "29.0.7-previous" do) Is there a best practice like using explicit tags like "linuxserver/nextcloud:29.0.7" instead of "linuxserver/nextcloud" and only changing to "linuxserver/nextcloud:30.0.1" (or as you mentioned .3) when they are available? How do you (in the sense of everybody else) handle your NC upgrades?

Hi all, I just updated to NC30 and had the following issue, which I (hope to) have already resolved and would like to provide a little information for others like me that are not too deep into the background of how everything runs "under the hood": 1st of all- whats the problem: Did get the above error message every 10 minutes. The problem seems to already be fixed in 30.0.1(?) and there is a patch for it https://github.com/nextcloud/server/issues/47275 https://help.nextcloud.com/t/error-after-upgrading-to-30-0-driver-exception/203947/13 I did get the updated file https://github.com/nextcloud/server/blob/2f2394cfa995bba08cdc9f1f945875a437110a9e/apps/dav/lib/CalDAV/Reminder/Backend.php and had to figure out where in unraid / docker it is. It includes only 2 changes So I did change my local file, restarted NC and do not have errors showing in my Log for the last 22minutes, which should have included 2 more already, if the error would not have been solved. Hope it does help somebody else P.S. Also disabled the Usage-Survey app due to some other errors- but not sure on that one.

Sorry for the late reply- I was at work for two days and am bock home just now. I tried to run 'occ maintenance:repair --include-expensive' as stated in: One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command `occ maintenance:repair --include-expensive` to perform the migrations. I did not resolve the message though. After that, I stumbled upon the above link and (because I was away) did intentionally not mess with any files directly. My resulting question is: will the php file be adjusted in the next change and I can simply re-run the repair including expensive, or to I have to adjust the php file anyway?

Stumbled upon this here as well: https://help.nextcloud.com/t/warning-after-upgrading-to-28-0-9-or-29-0-5/201289/13 Seems to be fixed in the meantime https://github.com/nextcloud/server/pull/47378 but I guess(?) it's not jet included in the linuxserverio-image

Thanks for that path. Any idea how long it should take / if anything needs to restart after updating the xml though?

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