ken-ji

Sadly I don't have any. Probably should document it for my own peace of mind.

You can probably check your router to see which port does these mac address appear. Also have you tried shutting down everything (VMs, containers) on your Unraid to see if the issue occurs? It seems like you'll need to really check your network to see where the craziness is coming from.

This sounds like you have a docker container running in bridge mode and its somehow announcing itself on the LAN with the incorrect internal IP But I don't remember seeing anything like that in your diagnostics file

so I took a look at the ipmi plugin and plugin package it installs is badly built. Granted when the package is installed and doesn't have a derekmacias user or group, they will fallback to the numeric value which happens to be 1000 hence admin:1000 for @elkaboing. This will break SSH access and maybe a few other such things. The plugin author @dmacias probably doesn't use ssh (and neither do the other IPMI users, hence they haven't seen this issue)

In my experience, this means you probably have a plugin that installed files owned by the user id 1000 (this is assigned to the first user created in any Unraid/Linux system) and group id 1000 So when you have a chance to reboot, try so to make sure its not an accidental chown. And if it did comeback, you'll have to inspect each of your plugins to determine if any is incorrectly built.

You actually want to be using private keys and the builtin background capability of SSH I'll assume you known how to generate private+public key pairs else see this for a primer When you are sure the keys are working correctly (generate them without passphrase encryption) and can ssh to the other server without being prompted for anything, Try the ssh command below (which will be exact command you stick into your script or go file) #!/bin/bash ssh -f -i path/to/ssh/private.key -R 8000:xxx.xxx.xxx.xxx:8000 root@xxx.xxx.xxx.xxx

Here's what I did in my own system (also behind CGNAT). Spun up a Mikrotik CHR (virtual router) on Linode (but any other VPS with completely unblocked ports is also fine). Made a site-to-site VPN between my home networks (3 different houses) and the VPS. then port forwarded port 80 + 443 to an nginx container (kinda like SWAG - but I prefer to roll my own). This could be done with a Linux VPS, but I wanted to play with a Mikrotik router (all of my edge routers are Mikrotiks) and have less issues with the rather performant IPSec site-to-site vpn This means I can access my Emby serve

I have rclone plugin installed and run this using the User Scripts plugin #!/bin/bash #argumentDescription=Backup Location #argumentDefault=/mnt/disks/VMs/appdata/backupFlash BACKUPDIR=$1 [ -z ${BACKUPDIR} ] && BACKUPDIR=/mnt/disks/VMs/appdata/backupFlash mkdir -p ${BACKUPDIR} tar -C /boot -zvcf ${BACKUPDIR}/`hostname`-flash-`date +%Y%m%d%H%M%S`.tgz --exclude config/super.dat --exclude 'previous*' --exclude 'bz*' --exclude "System Volume Information" . #cleanup - leave upto 14days worth of backups find ${BACKUPDIR} -ctime +14 -delete if [ -x /usr/local/bin/rclone ]; then # rc

Your going to have to provide examples/screenshots and probably logs regarding this bug report as anybody trying to replicate this would just ignore it as there's nothing in here to follow

Self-signed certs are the CA themselves... unless you are using self-CA signed ones? and I think the browsers will now warn on self-signed certs - even if they were trusted?

Haven't done this myself - but is there any reason why importing the OVA into LibVirt/KVM/QEMU not working for you?

This is exactly how networking works. When any process decides to access something, the network stack consults the routing table and determines what interface and router to use. If your untagged interface (regardless of IP) does not have a gateway defined then it will not get used to reach the internet. A lot of times before people had multiple VLANs with gateways configured (statically or dhcp), this would make it so the lastest interface to come up and be added to routing table would get used as the internet connection - even if the last interface to come up doesn't have a working internet.

@theruck for #1, by default the Dropbox data is shared over SMB. the defaults assume you are using Unraid in the default public share mode If this is not the case (you are using user accounts, set User and User ID to the appropriate user) refer to this for more details For #2. Just set the autostart button to on on the Dockers page

I'm afraid I have no idea what's going on here. and as you can see from your logs, it contains nothing useful. Only the Dropbox devs probably know what's going on and I don't think they are going to be helpful at all . This headless client is something they are still supporting but they seem to be veering people away from it as its not too easy to find on the site anymore.

Correct This whole stopping to sync is something I haven't encountered and I have no Idea what's causing it. I only have 3.5G in my Dropbox account and I've never seen it stop syncing. Losing the linked account data yes, but never the hanging on the sync.