jmztaylor

Is this a public facing server? Do you have issues with other plugins updating or installing? I ask this because that IP returns a hostname and visting that IP in the browser returns a NGINX page. You mentioned china. I am not completely sure how they handle NAT and proxying but is it possible you are sharing that IP with multiple households and that might be why you are getting that error. But if both those questions are no then that assumption is wrong.

To add to this I have this happen every time I reboot my server. It fails the first time but ALWAYS works the second time. Same USB boots on another computer without issue. I don't really care too much about it, so I just let it do its thing. Everything else I have tried on the server boots first time without fail. I have never put enough effort into figuring out why because it always boots the second time. I know this doesn't help you, but thought I would add my experience

Unless you are doing stuff with putting services behind VPN bridge is the best way to go by default

Are your sonarr/radarr containers also on bridge?

Once you get array up and functioning the My servers plugin update will fix that error

edit the file /boot/config/go and above the /usr/local/sbin/emhttp & line, add the touch command like below. This will cause it to create the file every boot. #!/bin/bash # Start the Management Utility touch /usr/local/emhttp/state/flashbackup.ini /usr/local/sbin/emhttp &

Please post diagnostics.

This was enough to get rid of the error touch /usr/local/emhttp/state/flashbackup.ini

Template is setup wrong. You will need to edit the paths like the screenshot below. Delete the first one that is pointing to /mattermost-push-proxy and change the 2 others.

chown -R 2000:2000 /mnt/cache/appdata/mattermost Assuming that is your appdata folder. If not just replace the path with the root mattermost appdata folder.

At some point I got it working and not sure what I exactly did. But simply WHOOGLE_CONFIG_DISABLE set to 1 disables it. I have nuked the container and tried multiple times and it works. I know without a doubt I tried this before but dunno

unraid docker engine uses docker run command not docker-compose with yaml. I misspoke. It needs to go under post arguments. So that line will look like this. /usr/bin/hbbs -k _ And using default appdata paths you would use the pub key at /mnt/user/appdata/rustdesk-hbbs/id_ed25519.pub and put that key into the clients.

It should just go in extra parameters when you hit advanced view on edit container.

In the desktop app its here

https://rustdesk.com/docs/en/self-host/install/#key This key is in the appdata folder. By default its /mnt/user/appdata/rustdesk-hbbs

Yeah I even put it at a ridiculous amount and disks will spin down after 15 mins so it means it just quit working altogether anyways.

Nope that did nothing

Yeah thats why it was confusing. But the contents of /mnt/cache/lxc was not the same as /mnt/user/lxc. /mnt/usr/lxc was emtpy and /mnt/cache/lxc was not. I think the /mnt/user/lxc was created by a mistake or something. And when I rebooted it couldn't link /mnt/cache to user and that caused everything to break.

So I figured it out. Somehow that folder got created on /mnt/user/ It wasn't the lxc plugin. My lxc path is /mnt/cache/lxc. Dunno what happened but nuked the folder /mnt/user/lxc. stopped the array and restarted it. It all came back normal. Not sure what exactly happened with that folder.

No major changes. Just tried to start a VM and it failed to start. Upon reboot all shares are missing but data is on each disk correctly. BTRFS came back clean on the pool. tower-diagnostics-20220712-1139.zip

He is one of the few going around helping most of the members here on his free time. I think he knows what he is talking about. But lets entertain. tg3 is a driver. Which has been said in this thread multiple times wouldn't affect you no matter what. From your diags. 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) [8086:1502] (rev 04) DeviceName: Onboard LAN Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville) [1028:052c] Kernel modules: e1000e The driver being loaded for your NIC is e1000e not tg3. And nowhere is the tg3 driver being loaded for you. So it was shear coincidence that adding the blank tg3 worked for you. Also, 6.9.2 wasn't affected by that bug anyways. So again. tg3 is a moot point.

Yeah its not too big of a deal. I think its just a permissions thing. I can destroy via gui but the folder doesn't get nuked. Even trying to remove the folder from terminal I get device or resource busy. Doesn't seem to be running though. Again not a big deal. But ultimately it work using the command previously posted.

Worked just fine. Another random question. Do you have a suggestion to clone existing container? I dunno if I am reading the man page incorrectly but I am doing lxc-copy -n existing-name -N new-name All it does is return to terminal with no output EDIT: So I was able to make it work via snapshot lxc-snapshot container-name snapshot-name Then restore lxc-snapshot --restore=snapshot-name --name=old-container-name new-container-name EDIT 2: And I guess lxc-copy does work in this syntax lxc-copy --name=old-container-name --newname=new-container-name Creating the containers this way seems to make the GUI unable to destroy the containers also.

Is there a way to set static IP? Adding lxc.net.0.ipv4.address and .gateway has no effect.

I am moving away from Google services and looking for a replacement for google photos. The only feature I need is auto sync. Nextcloud and owncloud apps are garbage so those are not an option. I don't need sharing or galleries or anything. Just straight need sync to my server without nextcloud/owncloud bloat.