blaine07

Locally, on Unraid, I try to download flash backup and it just spins; loading. More discussion: my last post in someone else’s thread - /topic/103766-backup-usb-flash-drive-never-ends/page/2/ I realize backup should happen automatically online with MyServers plug-in enabled but it says certain things maybe be omitted since backup is not encrypted. (What exactly is being omitted anyways?) Is LOCAL usb backup download not supposed to work with MyServers enabled? It just spins [emoji848] Any ideas or thoughts?

Thank you so much!

A google search led me here today. 6.10RC2; doing same exact thing. Spins and loads- nothing ever happens. Flash drive contents is ~290mb. If I log out of MyServers to see if it works is it going to cause me giant headache(I mean logging out, then back in)?

Yes size is there but it never updated we’re I cleared out logs folder [emoji848]

Thank you! (How can I get size shown of thumb drive to update in Unraid UI?)

It’s safe to do that live while server is going, correct? All the thanks mate! :-)

I *think* I know the answer but safe over sorry... Unraid was crashing a bit back and I used syslog server to mirror syslog to flash drive. Now, that I have turned logging off, my flash drive is quite. a bit "larger" than it was. I went to download a copy and it took forever. On thumbdrive is it SAFE to clear out the LOGS folder? Specifically syslog.txt that is taking up an extra ~600mb(I think I am reading that right)?

I know it’s semi subjective but… does everyone else’s Nextcloud instance take a few minutes to start? I feel like it didn’t used to take that long. Not a big deal, just wondering if other folks NC takes a few minutes too?

On linkage I am stuck here - see pic. Any ideas?

Yeah, I got it figured out mucking about. Thanks mate!

I recently had changed from "MACVLAN" to "IPVLAN" network settings for Docker in Unraid to solve some other issues; evidently this was a byproduct... FWIW: I had had static IPs set in pfSense from when I was using MACVLAN in Unraid; once I deleted the MAC address associated with previous static IP assignment(s) this issue went away. I was able to keep static ip, just couldn't have previous MAC Address from MACVLAN associated it with it. No NO Mac Address is associated with static IP assignment in pfSense. tldr; figured it out; my own idiocracy.

FWIW: I had had static IPs set in pfSense from when I was using MACVLAN in Unraid; once I deleted the MAC address associated with previous static IP assignment(s) this issue went away. I was able to keep static ip, just couldn't have previous MAC Address from MACVLAN associated it with it. No NO Mac Address is associated with static IP assignment in pfSense. tldr; figured it out; my own idiocracy.

Pardon my idiocracy... Using AdGuard container - When turning on encryption it has a spot for "Set certificate file path." Is there a way to write certs with SWAG container and point AdGuard to where SWAG stores certs so that they're automatically always up to date? I just don't know what the URL structure would be to go from AdGuard container back to SWAG where certs are kept. Any advice?

Is there further setup required when switching to IPVLAN from MACVLAN? This Unifi Controller… seems to not allow “remote access” to work since I’ve turned IPVLAN on. I change container to anything but BR0 and remote access immediately works. Not sure if container is broke or change from Macvlan to ipvlan and not sure where to start [emoji30]

Long shot: Is anyone aware if changing to IPVLAN would mess with containers being assigned BR0? I have issues with Remote Access with Unifi Docker; changing from BR0 to “Bridge” and issue goes away. It’s possible container is mucked up but is it change to ipvlan could’ve caused an issue unbeknownst to me?

So I have discovered ONLY on Network "BR0" it does not work-- If I temp change container to use "Bridge" Remote Access works fine. BR0 is network for assigning static IP in my normal networks DHCP range. Is there a rule or something that would be blocking that traffic? I did change recently from "macvlan" to "ipvlan" to address some other container issues; could that be my issue? Anyone have any ideas?

Anyone else on 7.0.23 been unable to turn back on/set up Remote Access? I had it on with previous version, but since 7.0.23 it says status is "unknown" so I turned it off and been trying to re-enable it and haven't been able to do so. Any ideas?

Well, as advised, here I am on 6.10 RC2. Server went down again this evening...I even was writing logs to USB and nothing useful there. Like nothing. So crazy. Anyways, I got jammed up on all the MyServers stuff...Everything back up though and changed to IPVLAN Cross fingers for me that this is the stability I need, please? LOL 🙂

It'll get updated soon 🙂

Depending on how this week looks I may see if I can find the time. Do I just need to backup USB drive ahead of time in case things go awry? Change branch to "Next"?

Is 6.10 likely to bring other issues to the table though? 🤔🤔

I’ve been randomly having Docker, I think, crash the last few weeks requiring unclean reboots to recover from. I have started logging, as of earlier today, syslog to USB drive. Server has not went down since I began logging to USB. I have been watching server and came across this though— see attached pic and error below: Feb 27 19:44:35 Tower kernel: traps: php-fpm7[1107] general protection fault ip:1519630a2c88 sp:7ffe596f23a0 error:0 in ld-musl-x86_64.so.1[151963094000+48000] Could this have anything to do with my crashes lately? I was able to find one thread in forum with similar error but seems was radarr specific. Attached is syslog as well as diagnostics. Any help would be greatly appreciated. Hopefully all required info is provided. tower-syslog-20220228-0300.zip tower-diagnostics-20220227-2102.zip

Braved the jump to 23.0.2 over here. All went well. Had to run missing indexes but other than that no issues 🙂

Anyone gone to 23.0.2 yet and had any issues? Looks like No ditched 23.0.1 🤔

Updated container this morning, it's now on version 1.20.1. Everything seems well so far! Thank you, a ton, @dsmith44