blaine07

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:

I don’t understand why you’d ever let it get 2 major versions behind I guess is where I struggle.

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.

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!

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?

Seems to have worked; thank YOU!

So stop container, delete them ALL(inside log folder), start container and they’ll all re-create?

Can you please provide more context about adding to your "/boot/config/go" file? I ran this: https://github.com/NginxProxyManager/nginx-proxy-manager/pull/1140 And it said nothing needed rotated as not older than 7 days, BUT in my log folder I have a *lot* of logs not edited in more than 7 days. I wonder if I could just delete all those from say last year for example with no ill effects?

I may have to resort to Github but any ideas on Logrotate timer issues: Seems as it's not purging as it should be: Some logs back all the way to March of 2022. Anyway I can safely purge these myself if nothing else? https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2938

Currently mine is operating with these parameters: Last few weeks/month have been extremely difficult with all the container/permission changes he's been toying with. I am finally on 2.10.3 all seems to have "settled down". I realize it isn't the containers doing/Unraid but I REALLY wish there was a export all hosts option so that some of the burden of "starting over" could be reduced.

Thank YoUUUU for the prompt response, as usual! Can’t wait to give it a whirl!

In Unraid is their a trick/way to get the time to report correctly as far as in the AUDIT Log? When I have a log the time stamps do NOT match; about 5 hours off.

Seeing it again here today, too, FWIW. Several may be "LSCR" containers..

Honestly, just gave up on the Docker Container and moved to a Ubuntu 22 VM.

Did you figure this out? I have been messing with getting Passbolt to work for two days. I really want to try it. Seems astounding that his entire thing working/being setup hinges on a Chrome plugin, of all things. Never the less, they keep mentioning health check - I guess I can't figure out correct syntax to run that in unraid. Anyone have any ideas? Okay, figured out health check but NO idea how to navigate all these issues: pbhealth.txt

Anyone have experience getting the Allow list for WOPI Requests? Both my Nextcloud and Collabora are behind Reverse Proxy - not sure what to set this as? I found this, but when using a reverse proxy I still don't know what I should be setting it as: https://help.nextcloud.com/t/in-nextcloud-office-i-can-t-make-wopi-allowlist-work/152004/8 Any ideas?

There is a manual fix; but find the information about the plugin. The plugin is what you want: EDIT: Found it:

How does one recreate docker.raw? My docker tab is horrendously slow to do anything. Similarly, I have a TON of containers.

Just proceed with caution; someone mentioned too cert prune needed updating but I think for what you'd need it would still work - id hate to be wrong make sure to back things up please mate 🙂

The other day JC21 mentioned he was working on/considering making it a variable. I guess at some point the old certificates pileup and slow it down and it times out. It was discussed that using using very prune helped. Maybe here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2713 or here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2708 poke around though; I know I just saw others Fussing about same thing recently 😀

Good work figuring it out; about the story of my life too — I make a post and wham it hits me lol

Yes, I have had to do this the last several updates to. Not quite sure why but it's kind of a nuisance.

Thank you for sharing! Not sure if just myself or...once I set ENV Variable in the container settings and rebooted container I did NOT have to go into Vaultwarden admin panel and set Admin_Toke again. On my first of two instances I did that and I ended up having to delete the ENV variable in container settings. On my second instance, i just set the ENV variable in container settings, rebooted container and all picked up fine and didn't fuss about "ADMIN_TOKEN" being set in config file AND with a ENV. Never the less works great, thank you! EDIT: I lied; on second instance I had to do same as far as set in admin panel and delete the ENV in container settings. Kept getting: [2023-03-28 06:26:59.295][vaultwarden::api::admin::_][WARN] Request guard `AdminToken` failed: "Unauthorized". In the logs until I did

There was some way jc21 was telling them, on github, to enable a "debug" type mode that provided more logging but not sure if he was kicking it off with a ENV or what.