blaine07
-
Posts
754 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by blaine07
-
-
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?
-
You do not *need* to do those changes.
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.
-
59 minutes ago, Wolbaz said:
FYI as of the latest version of this you can enable mobile client push notifications (basically live sync to your phone)
https://github.com/dani-garcia/vaultwarden/wiki/Enabling-Mobile-Client-push-notification.
Add the variables to the docker template mentioned above, and restart the container. After that, re-install your phone app. Kind of a pain but well worth it to not have to sync manually any more.
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?
-
You are correct. Wait for lscr.io/linuxserver/nextcloud:version-27.0.1 to be available or switch to lscr.io/linuxserver/nextcloud:latest and let auto update handle it (although we do recommend pinning the specific version and manually updating rather than relying on auto updates).
Simply updating the image will update nextcloud itself. No manual commands should be necessary.
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?
-
1
-
-
37 minutes ago, iXNyNe said:
You are correct. Wait for lscr.io/linuxserver/nextcloud:version-27.0.1 to be available or switch to lscr.io/linuxserver/nextcloud:latest and let auto update handle it (although we do recommend pinning the specific version and manually updating rather than relying on auto updates).
Simply updating the image will update nextcloud itself. No manual commands should be necessary.
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?
-
My first question is does the system eventually recover? But this seems like a topic that will take a bit of back and forth, so I'd suggest creating your own thread and uploading diagnostics. It is very difficult to have a lot of back and forth in a release thread.
I apologize. I’ll open my own thread tomorrow, but yes, it seems at exactly 30 minutes in it “recovers”
-
1
-
-
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?
-
1
-
-
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.
-
14 minutes ago, iXNyNe said:
The latest test image is
lspipepr/nextcloud:27.0.0-pkg-34240624-dev-d151fd013f86933409d88dbdd26222232842031f-pr-325
It has a bunch of small fixes and tweaks, among them the integrity check extra files should be resolved.
Shouldn't be long before this is released as lscr.io/linuxserver/nextcloud:latest for those who would like to wait.
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?;
-
1 minute ago, iXNyNe said:
Changing the image forces docker to recreate (not just restart) the container. That's the trick to solve some problems, such as the core files inside the container (they would not exist if you recreate the container).
It doesn't even have to be the specific image I listed, and you don't have to switch back to the latest image either. You can pin any tag you'd like, and in fact LSIO recommends pinning images whenever possible to prevent surprise auto updates.
Thank you for clarification. I’ve pinned “27” for now - thank YOU!
-
Got an issue after updating the docker. I didn't do an update for a few months, now log shows:Can't start Nextcloud because the version of the data (24.0.3.2) is more than one major version behind the docker image version (27.0.0.
and upgrading more than one major version is not supported. Please run an image tagged for the major version 25 first.
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/ -
49 minutes ago, iXNyNe said:
As for the core files, it actually looks like those are no longer in a user accessible location, but you could recreate the image and those should be fixed. The easiest way to recreate the image it switch the image to lscr.io/linuxserver/nextcloud:version-27.0.0 and then back to lscr.io/linuxserver/nextcloud
For my own curiosity sake why would he change image to “…/nextcloud:version-27.0.0” and then back down to “…/nextcloud”
I am on Nextcloud 27; is it fine to just leave myself locked to “…/nextcloud:version-27.0.0” or after the upgrade are we supposed to change back to “…/nextcloud”?
-
1 hour ago, iXNyNe said:
This is expected. Please read https://info.linuxserver.io/issues/2023-06-25-nextcloud/
tldr; no more manual updates
Oh wow, this is a big deal. I don’t see a tag for 27 that I’m on… I’m just on “latest”m
I am dumb:
-
2
-
-
4 hours ago, dodgypast said:
You could not upgrade from 24.0.12 via the command line.
We're not idiots.I don’t understand why you’d ever let it get 2 major versions behind I guess is where I struggle.
-
Mannnn, you ain't even following the issue here dude, just move on PLEASEEEEE? You are not adding any value nor helping OK.
For you humble information, NextCloud recent update broke everything and people are trying to fix it.
"Should the "occ upgrade" command be executed? [Y/n] y
This version of Nextcloud is not compatible with PHP>=8.2.
You are currently running 8.2.6"
Reading the first post on how to keep Nextcloud up to date is a ton of value. The last 8/12 posts are the same issue(s) over and over.
What version of Nextclouds “…recent update broke everything…?”
-
I just want to say - in the first post of this thread is how to update Nextcloud using the command line. That is the most reliable and successful way to upgrade Nextcloud itself. All these silly back and forth browser button tricks could be eliminated by simply following instructions in first post. Y’all gonna end up with something corrupt and have a real situation you’re stuck in messing around.
-
On 5/23/2023 at 11:49 PM, ich777 said:
On what Unraid version are you?
Did you change something in the template? Have you yet tried to stop the container and then open the Logs?
Please post a screenshot from your Docker template.
EDIT: I've now set up a new instance on my test server and it is working as intended, I've attached the log here: rustdeskserver-aio.log
EDIT2: I've got now confirmation that it works on other machines than on mine on Unraid 6.11.5 and also on 6.12.0-rc6
I figured mine out - but never had to muck with such setting before. In pfSense I had to change Nat Reflection for that port forward group to "Pure NAT".
My default mode for the firewall has always been "NAT + Proxy":
On port forwards for RustDesk I had to change it to ""Pure NAT":
Not sure if this may help some other lost person later but ich777 THANK YOU for your confirmations that it was just something stupid I was up to!
Thanks!
-
1
-
-
I can't seem to get the container for RustDesk working at ALL today. Not seeing anything in docker logs. Forwarding ports to Unraid server from pfSense. A record on Cloudflare with proxy off to home IP/pfSense.
What could I be doing wrong?
Docker requests
in Docker Containers
Posted
Linkwarden?
https://github.com/linkwarden/linkwarden