gshlomi

Members
  • Posts

    338
  • Joined

  • Last visited

Everything posted by gshlomi

  1. Thought about it. I'm in the process of creating a Win10 VM with GTX1060 passthrough for NVIDIA Gamestream to my Shield TVs, but haven't seen the Teslas support Gamestream or even Steam in-Home streaming... If you're from Israel, I've got a gift for you
  2. Hi folks Received three used Tesla C1060 as a gift. Any thoughts on usage scenarios for these in a VM? Thanks Sent from my iPhone using Tapatalk
  3. I'm currently running CrashPlan, ResilioSync & Nextcloud on my unRAID server. Have used to backup a few computers (parents &a family) to my server, and backup my server to CrashPlan central. I'll probably switch all the computers to sync to unRAID (using Nextcloud or Resilio Sync, haven't decided yet) instead of backup, and start backing up their data folders to CP Central using the Small Bussiness account... Am I missing anything I'll lose by doing that? Thanks
  4. How about stopping Docker, deleting the image file and recreating the containers (without removing your appdata folder)? I know it's a must in case you replace your cache drive. Thanks
  5. Thanks. I'll check my SAS2LP when I'll be home again. Sent from my LG-K430 using Tapatalk
  6. Yep. Does it have any known bugs? Sent from my LG-K430 using Tapatalk
  7. Got the same problem, but mine finds 5 errors constantly. Tried dropping to single parity, everything checked allright. Precleared the spare drive again successfully, added as a second parity and rebuilt it. Next parity check - same results - 5 errors again even with write correction. Is the dual parity feature ready for production?
  8. Hi folks. I'm trying to understand the correct way to utilize VLANs on UNRAID. My scenario - I want to create an Active Directory Domain test environment, seperated on a different VLAN than the rest of my network, so I can practice on DHCP as well. The servers on the test VLAN need to have access to the internet (at least in the beginning). Enabled VLANs and added a VLAN using static IP assignment (see attached screenshot), installed a VM on the 192.168.2.0/24 VLAN and assigned it a static IP address manually. The problem I'm having is that the VM can easily connect to the unRAID server (using the IP I've assigned the VLAN interface, 192.168.2.1) but can't connect to the WWW (pinging 8.8.8.8 fails). What am I missing? Do my switch must support VLANs, or are the VLANs been managed in a vSwitch inside the KVM visor? Hope my question makes sense
  9. Thanks That's what I've been looking for...
  10. Doesn"t it have to be based on an unRAID container template for that?
  11. Does it enables auto-updates for the container?
  12. Anyone? Or can anyone point me to a starter guide to creating container template for unraid?
  13. Hi guys. I've follow the instructions on https://nextcloud.com/collaboraonline/ to integrate Collabora Online with Nextcloud, using LinuxServer's Nextcloud & LetsEncrpyt containers as the basis. Had to follow https://icewind.nl/entry/collabora-online/ for NGINX instructions (configured on the LetsEncrypt container, adding "office" to the list of my subdomains). The only things I had to change from the instructions in the links is: replacing "127.0.0.1" to my unRAID IP on the docker command line replace "localhost" to my unRAID IP on the NGINX configuration Is there someone who can create an unRAID compatible template for the CODE container? I really like it to be managed like all my other containers, but dunno where to start. Thanks
  14. OK, so I've scrapped everything and started over... Removed Nextcloud, MariaDB & LetsEncrypt containers and config folders under appdata, reinstalled them "by the book": Installed MariaDB, verified that "\appdata\MariaDB-Nextcloud\custom.cnf" includes "binlog_format=mixed" (appears to have changed in the default installation, didn't have to change it by myself). Installed Nextcloud (11.0.3 was pulled), went through the web configuration phase using InternalIP:Port (ignoring certificate error), Accessing the "Server settings" page internally, everything looks great: Installed LetsEncrypt (1.10.3 was pulled), moved all SSL related stuff to "\appdata\LetsEncrypt\nginx\ssl.conf", edited "\appdata\LetsEncrypt\nginx\site-confs\default" to contain: # redirect all traffic to https server { listen 80; server_name _; return 301 https://$host$request_uri; } # Nextcloud server block server { listen 443 ssl; server_name nc.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.100:444; } } Accessing the "Server settings" page externally (after a popup of trusted domain), getting security warnings: Following @johnsanc advice, found out I've got the following duplicate settings at "\appdata\Nextcloud\nginx\site-confs\default" and "\appdata\LetsEncrypt\nginx\nginx.conf": add_header X-Content-Type-Options nosniff; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; So now that I've found the exact problem, what would be the better way to fix it? Which file should I edit and will survive a container update? I'm tending towards changing "\appdata\Nextcloud\nginx\site-confs\default", because I want the added security headers for all of my reverse proxied sites... Thanks (especially if you've read it all )
  15. I know, already checked it, but don't know why I'm the only one with this problem and where should I fix it...
  16. But isn't passing htpasswd for one site (using brute, social eng, whatever) opens up all your sites to the attacker? Using every specific app built in authentication enables different passwords to different systems. Or am I missing something? Sent from my LG-K430 using Tapatalk
  17. If you access Nextcloud from outside, and go to the Admin page, doesn't it alert of some security warnings?
  18. Security question - what is more secure - using .htaccess for authentication or using each app built-in authentication? Sent from my LG-K430 using Tapatalk
  19. You were correct. It seems the headers are added in LetaEncrypt's nginx.conf and in Nextcloud's default. What's the correct location to remove it? And how come I'm thr only one with this problem? Just installed both containers from the Community Applications... Haven't done any customization except the reverse proxying in LetsEncrypt default. BTW - is there a way to combine both dockers into one, using the nginx built into Nextcloud for reverse proxying with LetsEncrypt? Sent from my LG-K430 using Tapatalk
  20. 10x I'll check it out as soon as I'll get home... Sent from my LG-K430 using Tapatalk
  21. Anyone? Sent from my LG-K430 using Tapatalk
  22. Sorry, but don't know how to check the headers. LetsEncrypt logs or Nextcloud logs?
  23. Hi guys. Need some help understanding where my problem lays. Just installed Nextcloud (based on MariaDB), using LetsEncrypt container as reverse proxy. Accessing NC internally (using https://XXX.XXX.XXX.XXX:444, ignoring certificate error) shows all checks passed. Accessing NC externally (using my domain name), I receive the following: The "X-XSS-Protection" HTTP header is not configured to equal to "1; mode=block". This is a potential security or privacy risk and we recommend adjusting this setting. The "X-Content-Type-Options" HTTP header is not configured to equal to "nosniff". This is a potential security or privacy risk and we recommend adjusting this setting. The "X-Robots-Tag" HTTP header is not configured to equal to "none". This is a potential security or privacy risk and we recommend adjusting this setting. The "X-Frame-Options" HTTP header is not configured to equal to "SAMEORIGIN". This is a potential security or privacy risk and we recommend adjusting this setting. I've tried adding the appropriate parameters (as found in https://docs.nextcloud.com/server/11/admin_manual/installation/nginx_nextcloud_9x.html): add_header X-Content-Type-Options nosniff; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; but getting the same results after restarting LE container. Any help would be appreciated.