Jump to content

ken-ji

Members
  • Content Count

    967
  • Joined

  • Last visited

  • Days Won

    4

ken-ji last won the day on June 27 2018

ken-ji had the most liked content!

Community Reputation

123 Very Good

1 Follower

About ken-ji

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Philippines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The entire /mnt/user is a FUSE filesystem called shfs - which is what Unraid uses to merge all the disks together into a single virtual filesystem. Dropbox is being anal by just checking the fs in use and rejecting "unsupported" ones out of hand. Also if Dropbox wasn't being anal, storing your Dropbox files on the array would cause issues unless use cache disk is turned off, else watch Dropbox delete your files when the mover kicks in. The workaround for this is to locate the Dropbox files on a specific disk ie /mnt/disk1/Dropbox or /mnt/cache/Dropbox (like I do). Another workaround, if you must store it on the array, is to create a loopback disk image on the array and format it ext4, then mount it ie /mnt/disks/Dropbox then point Dropbox there.
  2. I think the problem is that the data directory is in the array as there have been known issues with sqlite and the array user shares filesystem. This issue seems to be fixed in the the current RCs. For the time being you can put the docker data in /mnt/cache/Dropbox via the settings and editing the Container Path: /dropbox/Dropbox You might want to show the Host path settings that you have so we can see why yours became /mnt/user/Dropbxox/Dropbox If you do this *changing the location of the Dropbox files*, make sure to either start fresh with empty Dropbox and appdata directories, or move the files in as Dropbiox might decide you emptied your folder and proceed to nuke all your files.
  3. I think the IPv6 setting is just for the UI to allow setting a static address or enable DHCPv6 Perhaps you can file a bug report/ feature request to properly enable/disable the IPv6 address (SLAAC or not)
  4. Its not DHCPv6, but rather SLAAC which built in to the Linux kernel if the IPv6 module is loaded (or compiled in) your router is sending RA (router advertisement) packets, which tells IPv6 devices that support SLAAC what the /64 prefix should be and the (client generates the other 64bits via MAC to EUI-64 or some RNG (privacy address) You could turn it off with the following sysctl tunables net.ipv6.conf.default.accept_ra = 0 net.ipv6.conf.all.accept_ra = 0
  5. I think the error is because when you run Dropbox on the array, it correctly sees the filesystem as shfs which is artificially unsupported. Some users have just created a ext4 loopback image. I suppose with the container working again, you can have it on the cache drive
  6. you'll need to delete .dropbox-dist from the appdata folder - by default /mnt/user/appdata/dropbox the broken versions have left incomplete .dropbox-dist folders which is now screwing it up.
  7. I've rebuilt the docker image. and it seems to be running on my setup (but I have not linked it to my account as I do not have a free slot at the moment) as an FYI, the docker image is built with whatever is the latest dropbox download available. While the container is running, it can upgrade itself (as the dropbox app expects to be able to do so) and the upgrade is stored in the appdata folder. So the container in theory should never become too old (unless Dropbox deprecates the app), but I need to rebuild the docker image to contain a fresh app version. It should be possible to add routines to upgrade the docker container after install, but I'll need to see and test that approach.
  8. Apologies, as I've been busy with a whole bunch of other things, living away from my server, and am considering relegating Dropbox to a lower usage tier - because I don't like their decision to limit the free tier to 3 or less devices. I'm going to rebuild the docker image and see if it still works.
  9. Mine does not. I has the time stamp of the last time ssh service is restarted (or when my server booted up) Unraid (and Linux in general) do not even create /root/.ssh until you've tried to connect to a ssh host from the root account; at which point the ssh host keys need to be saved and the directory and file are created.
  10. Finally took a look and i probably won't be using this thing as a docker - it requires way too many capabilities than what I'd like to limit it too. Its very nature is that the docker needs to be in host mode to create multiple bridges and connect the client to a bridge then mess with the firewall rules to allow whatever you have. I'm sure I was hitting conflicts with my setup but yeah I never go it to work with my LAN at all. This might one of those applications I'd rather it run as a VM. But I might have a better look with this when I have time, hoping somebody else works out the issue. In hindsight just realized the reason I couldn't even get it to work is that I set the thing to routed mode for everything, but OpenVPN-AS does not readily show you all the subnets they generated, which needed to be programmed into my router. Talk about complicated if you are trying to do all of this remotely.
  11. I'm going to have to give this a try. I'm not using the openvpn-as container myself (though I used to) as I've left VPN capabilities to a VPS that my router has an IPSEC connection with - since my provider is slowly rolling out CGNAT and I got selected as an early bird with no way out it seems. (Business grade plans need you to be a real business and no other non CGNAT ISP provider in the area)
  12. This error is typically due to running out of resources, so I'd also try to check the logs first for Out Of Memory issues before rebooting.
  13. Yes, its best to have a range of IPs for dockers that is outside of the Unifi's DHCP range. You can customize the docker network (by default named eth0/br0) and have it use IPs in the desired range (instead of the whole subnet as by default) FYI: Docker assigns containers IPs using a self-contained IPAM which does not coordinate with any external system like DHCP servers, etc. Docker does not attempt to check to see if the IP has been allocated and just picks the next available number.
  14. in syslinux.cfg the i915.alpha_support option is not needed for your case so you can drop that. Try setting Emby Transcoding to Advanced. You should see a list of video codecs and any available HW decoders for them. ie.
  15. Yes, have Emby Premiere and turn on Hardware Transcoding in Emby. Set it to Advanced to see if the iGPU is correctly setup