blaine07

Not positive but last few updates have said to update the default.conf. I swear on that I saw some specific things about WebDAV. How old is your default.conf? Very first line should date it.. Maybe your solution though; not positive.

FWIW in browser I click “logs” button and nothing populates.

When I start Nextcloud I see this; any reason for concern? How to fix? (everything seems to be working fine)

A few problems above reported with Hub7/V28 - has any of that been addressed yet? Are we in all clear to 27>28 at this point?

:facepalm: and you'd be right..thank you..sigh. Thanks!

Is it supposed to look like this everywhere now or is it a different plugin? So hard to follow going side to side on entire screen:

https://github.com/OpenSignLabs/OpenSign?ref=selfh.st

Linkwarden? https://github.com/linkwarden/linkwarden

Just came here to say - I’ve been trying to get silly shares available over Tailscale for a few days. My understanding was it “just worked”. Never the less my experience has been frustrating and admittedly somehow likely to be self inflicted. Just wanted to say thanks - some combination of changing “NTLM” group policy in Windows along with advice in this thread about turning netbios OFF and some specific SMB extra configuration(seen below) info I am happy to report success. No idea truly which change was most relative to resolution - but thank you folks - all of you; my remaining sanity can now remain intact. Edit: this:

Is there any reason this no longer shows up in the app store?

Seems like it works fine; just not sure about the port 3012/3 between my two instances. :-)

When converting to client push as explained here: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-Mobile-Client-push-notification Do we delete the "WEBSOCKET_ENABLED" AND "websocket" port 3012 mappings in our Unraid Tempalte? Then just add 3 variables above?

Overview says " Need settings.yaml in appdata directory (Read First)" but doesn't point me anywhere towards what I need to be "reading first"?

Came here with same issue; that button needs to be better identified, somehow.

I have two instances of Vaultwarden on my Unraid. Both use same email as my login. Would I generate ID and KEY one time and use it in both places or "generate it twice"? Also, do we delete "Websocket Port" from container information? Delete the "port 3012" references from our reverse proxy, too?

Updated from 27.0.0.0 > 27.0.1 by changing container tag and waiting for update to “finish.” When I was done I was presented with this: The fix was to run this command: docker exec -it NEXTCLOUD-CONTAINER-NAME occ db:add-missing-indices Does this/can this/should this be baked into upgrade script(s) on startup of container with new tag post upgrade process?

And I just got the github email - thank YOU

My instance is prompting today to update to Nextcloud 27.0.1 - the correct answer is I just want to wait for container to be updated to update it? My container is locked to "lscr.io/linuxserver/nextcloud:version-27.0.0" but I do NOT see a 27.0.1 container release so I just wait and I do NOT upgrade in Nextcloud itself?

I apologize. I’ll open my own thread tomorrow, but yes, it seems at exactly 30 minutes in it “recovers”

On 6.12.2 and 6.12.3 Everytime docker starts it stays like this a substantial amount of time. Do not have plex here; but Jellyfin. Anyone else see this?

Just chiming in to say; I am in same boat as above - cron job is NOT running... Oh and files were "last edited" "in 2 hours" LOL; well some. Some are correct and say XXhours ago or yesterday etc.

So do I need to stay locked onto “lscr.io/linuxserver/nextcloud:version-27.0.0” or what’s recommendation for things like this with fixes and such? Or will the fixes move to “…-27.0.0.”?

Anyone else seeing this issue with most recent iOS app update?; https://github.com/nextcloud/ios/issues/2492

Thank you for clarification. I’ve pinned “27” for now - thank YOU!

How can I change the tagged image to 25? I tried changing "lscr.io/linuxserver/nextcloud" to "lscr.io/linuxserver/nextcloud:25.0.0" but it literally crashes UnRaid.. Have to restart :\ (command for docker and for unraid stops working entirely, hardware stats stop working, etc.) Am I tagging the wrong image? There's the version but also other variants like 25.0.0-ls233 and amd64-25.0.0, etc. I'm on an intel processor, an i5-10600K, latest UnRaid 6.12.1. This might help? https://info.linuxserver.io/issues/2023-06-25-nextcloud/