• Posts

  • Joined

  • Last visited

Recent Profile Visitors

444 profile views

Uncledome's Achievements


Newbie (1/14)



  1. I guess I worded myself wrongly because I was talking about a cloud-app like nextcloud or owncloud. Basically everything I said up there is pointing in the end to a nextcloud docker on my unraid system. I would never expose my unraid server itself. But I'm still afraid that an attacker might get into my unraid server through the docker part of unraid or something like that. Thanks Cherry
  2. Hey guys, kinda question that maybe does not really fit here but I don't know where else to ask. Did a little search but found nothing that could push me to either side (open services to wan or access them through vpn). Basically: is your cloud exposed to WAN? if so, why and how "secure" is it to do that. My current setup would look like this: Three different subdomains handled by cloudflare to hide IP's and proxy them through cloudflare services ending on my ISP router on TCP 443 which is natted to my fortigate firewall on TCP 443. That traffic is checked for source (only allowing cloudflare ips) and then natted on the fortigate to a VLAN in unraid where the letsencrypt docker and the three services reside. So firewall side looks okay I guess but I still worry what will / could happen if someone cracks lets say the nextcloud instance through a security issue of nextcloud / proxy server. Because of this anxiety I have of not knowing if this is secure enough, I've currently disabled the WAN facing side of my setup and access it through vpn. But this kinda sucks because not accessible at work and cannot share files. Thanks Cherry
  3. Thanks a lot for all this information. I've now set it to write to the usb device and will have a look at the server for a few days before disabling it. Yea, I have a daily backup of the drive anyway in case it gives up :). Thank you very much Cheers Cherry
  4. Hey Frank1940, thanks for the fast answer. That is good to know. Do you know if there is a possibility to write that to an unraid share as well? Would like to keep logging 24/7 but not to the flash drive because of the many unnecessary writes that might degrade the lifespan. Does that mean the file won't be overwritten on reboot but rather a new one will be created? Thanks & Cheers Cherry
  5. Hey guys, first of: Sorry if this was already asked, I searched but found nothing. So now to my problem: Yesterday my unraid server just shut itself down. Does not look like it crashed but I can't tell because all the log files were empty. Only thing in them was the boot up process and everything afterwards. So I can't tell why it just shut down. As far as I understand, logs are written to RAM so that would explain why those were empty. Is there a way to have the unraid logs be persistent on my drives? I checked the Syslog Server under Settings but this seems to be for external resources writing to unraid. Maybe I'm just missing something. Would be great if someone could lead me in the right direction so I have the logs the next time this happens. Thanks & Cheers Cherry Ps. Might be that there is indeed a hint I missed for the shutdown in the diag files so I attached them. cherrytree-diagnostics-20191015-1832.zip
  6. We do have a docker. I am currently using a docker with my self hosted license. //EDIT: Ah, I just realized I was using a docker from DockerHub. (The official one from Atlassian) and it works great with updates and so on.
  7. I always used Atlassian Confluence for this and was more than happy seeing the image on unraid docker. But the license is like 10 bucks a year for up to 10 people if I remember correctly.
  8. Had a few issues after updating to rc3 (unraid was telling me partition issues and so on) but this was fixed with swapping usb to another port (had it on usb3 port, now usb2). Since then there were no other issues, docker is running smoothly until now.
  9. Just updated to rc3, currently rebooting. Will let you know if the problem persists.
  10. Sure, I'll forcefully shutdown the server now and will upgrade to 6.5.1-rc2. Should the server hang again, I'll let you guys know.
  11. There are multiple PIDs with status D, Tried the ls -l with one of them: root@Tower:~# ls -l /proc/26457/fd/ total 0 lrwx------ 1 root root 64 Mar 30 11:47 0 -> socket:[811239] l-wx------ 1 root root 64 Mar 30 11:47 1 -> pipe:[857897] lrwx------ 1 root root 64 Mar 30 11:47 2 -> /dev/null lrwx------ 1 root root 64 Mar 30 11:47 3 -> socket:[863915] root@Tower:~# As for the remote mapping, I actually never had any issues but normally (before unraid which I am currently in trial) I used an ubuntu server for my docker (hosted on a XenServer Free Edition Server) where I mapped the remote share in fstab and passed it through to the containers. First time having those issues in my life .
  12. Yea, multiple should have a mapping in their config. From the top of my head those are: Plex, Sabnzbd, Sonarr, Radarr, JDownloader, Deluge and maybe a few others (all my media is stored on the remote share)
  13. Sure, i've attached the syslog file because its too much to quote. syslog
  14. There you go: root@Tower:~# df -t tmpfs Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 32768 252 32516 1% /run tmpfs 16461524 0 16461524 0% /dev/shm cgroup_root 8192 0 8192 0% /sys/fs/cgroup tmpfs 131072 828 130244 1% /var/log shm 65536 0 65536 0% /var/lib/docker/containers/29665f5836321c13963824e87a964e6f041a7654c5d5a56d6878fc35bf8e7760/shm shm 65536 0 65536 0% /var/lib/docker/containers/9f4716af81f9e00f5e94c53ff602c56902e88c05fbd6f22e9e2296c8e43ff7dd/shm shm 65536 0 65536 0% /var/lib/docker/containers/034adf9c55653bb881968ca8d44355d9bdcb91702daabe289ca5fd0ed82a64d3/shm shm 65536 4 65532 1% /var/lib/docker/containers/a3ecdae744a46beea66d9caec718aec884a4b0793f67f5e5fe17a83f1318fa08/shm shm 65536 4 65532 1% /var/lib/docker/containers/dcf1c167e8731cfdeb87f2081e66eff6ec1812f9a5ee3d4c15f3caae0f39906d/shm shm 65536 8 65528 1% /var/lib/docker/containers/68e3ad2825e29640a8d090fe0fd3090a3353d3f66cee11ceb042b7fddad8f7ef/shm shm 65536 0 65536 0% /var/lib/docker/containers/1a2df515f75397057758aad73897792dc94411ac3aa98b7ae0bfe343fb70c366/shm shm 65536 0 65536 0% /var/lib/docker/containers/43349a50c0d6c50d4987fc88996c481cedfce67c2532fe1b44be8d237b4bb380/shm shm 65536 4 65532 1% /var/lib/docker/containers/7e44a412169eee513eafd0523eed2eabf216ce7d578640174a3ccb211b9e7cfa/shm shm 65536 0 65536 0% /var/lib/docker/containers/8294edae393ac797db55b6060f621bc1f9efade4645888c2e4c10f6ddf8bdb93/shm
  15. These are the last few lines before it stops: 0 /var/lib/docker/unraid/ca.backup2.datastore 0 /var/lib/docker/unraid 0 /var/lib/docker/containerd/daemon/io.containerd.content.v1.content/ingest 0 /var/lib/docker/containerd/daemon/io.containerd.content.v1.content 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs/active 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs/view 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs/snapshots 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.overlayfs/snapshots 0 /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.overlayfs 648 /var/lib/docker/containerd/daemon/io.containerd.metadata.v1.bolt 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/734d4b9da9e20a4b96828270d6c3f6d7ffc10e3dcf3c8554247673e76b344dd4 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/19647dee6de0be1ca75840af5a88b29aea3aa6799b455ee1995094b51f83a2f0 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/60ddf788b24a00021d4034e37ec760f34467a1c9179437836e43704ce1e445cc 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/9f4716af81f9e00f5e94c53ff602c56902e88c05fbd6f22e9e2296c8e43ff7dd 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/a3ecdae744a46beea66d9caec718aec884a4b0793f67f5e5fe17a83f1318fa08 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/dcf1c167e8731cfdeb87f2081e66eff6ec1812f9a5ee3d4c15f3caae0f39906d 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/68e3ad2825e29640a8d090fe0fd3090a3353d3f66cee11ceb042b7fddad8f7ef 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/43349a50c0d6c50d4987fc88996c481cedfce67c2532fe1b44be8d237b4bb380 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/7e44a412169eee513eafd0523eed2eabf216ce7d578640174a3ccb211b9e7cfa 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/8294edae393ac797db55b6060f621bc1f9efade4645888c2e4c10f6ddf8bdb93 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby 0 /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux 648 /var/lib/docker/containerd/daemon 648 /var/lib/docker/containerd 0 /var/lib/docker/tmp 0 /var/lib/docker/runtimes 39355848 /var/lib/docker root@Tower:~#