assassinmunky

Members
  • Posts

    89
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

assassinmunky's Achievements

Rookie

Rookie (2/14)

4

Reputation

  1. Best thing ? Native dockers! new feature ? Non root shell and ftp access
  2. can confirm this has also fixed the database corruption problem for me for 12hr+ now. what is the long term solution though?
  3. Hi all, I have a windows 10 vm with gpu passthrough that no longer boots after upgrading to 6.4.0 , it just takes about 10 min to start up, then blue screens with the error "VIDEO TDR FAILURE" and something about nvlddmkm.sys error. This is a nvidia gt710 that I'm passing through. I have tried building a new windows 10 host, and everything works fine until I install the driver for the nvidia gt710, then i can no longer reboot the vm with the passthrough enabled. I attached my diagnostics, any help would be appreciated. thanks. tower-diagnostics-20180130-1023.zip
  4. hmm... thats strange... i dont even use webgrabplus... i blew out the xml file, all good now.
  5. These errors just started after a hard reboot... any idea how to fix? Warning: DOMDocument::load(): Opening and ending tag mismatch: Support line 8 and Container in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Premature end of data in tag Container line 2 in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Opening and ending tag mismatch: Support line 8 and Container in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Premature end of data in tag Container line 2 in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Opening and ending tag mismatch: Support line 8 and Container in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Premature end of data in tag Container line 2 in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Opening and ending tag mismatch: Support line 8 and Container in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Premature end of data in tag Container line 2 in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Opening and ending tag mismatch: Support line 8 and Container in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220 Warning: DOMDocument::load(): Premature end of data in tag Container line 2 in /boot/config/plugins/dockerMan/templates/linuxserver.io/webgrabplus.xml, line: 59 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 220
  6. Sure there is, you can "enter" the docker container with this command: docker exec -i -t CONTAINER_ID /bin/bash Get the CONTAINER_ID from the "docker ps" command
  7. what does the usage in /var/lib/docker look like? what is your output of this command? du -h -d 1 /var/lib/docker/
  8. use "docker ps -s" to see where the usage is, and then figure out how to clean it up. mine was in pydio: # docker ps -s CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZE 2d6bc0931a8c limetech/plex "/sbin/my_init" 3 weeks ago Up 6 days PlexMediaServer 377.3 kB (virtual 557.3 MB) ad63faa6b9f5 linuxserver/letsencrypt "/init" 4 weeks ago Up 6 days 0.0.0.0:1180->80/tcp, 0.0.0.0:11443->443/tcp letsencrypt 624.1 kB (virtual 180.2 MB) e22be497a65d linuxserver/rutorrent "/init" 4 weeks ago Up 6 days 0.0.0.0:51413->51413/tcp, 0.0.0.0:6881->6881/udp, 0.0.0.0:51444->51444/tcp, 0.0.0.0:10080->80/tcp rutorrent 4.924 MB (virtual 123.9 MB) c717743877a1 linuxserver/pydio "/init" 5 weeks ago Up 6 days 80/tcp, 0.0.0.0:33443->443/tcp pydio 58.47 GB (virtual 58.66 GB) 83792be00581 linuxserver/mysql "/sbin/my_init" 5 weeks ago Up 6 days 0.0.0.0:3306->3306/tcp mysql 796.8 kB (virtual 533.7 MB) 655e33471cbe linuxserver/sonarr "/init" 6 weeks ago Up 6 days 0.0.0.0:18989->8989/tcp sonarr 22.27 MB (virtual 528.1 MB) 7088b4c76ff3 linuxserver/couchpotato "/init" 6 weeks ago Up 6 days 0.0.0.0:15050->5050/tcp couchpotato 18.56 MB (virtual 164.1 MB) b1aa37b16af1 linuxserver/jackett "/init" 6 weeks ago Up 6 days 0.0.0.0:19117->9117/tcp jackett 12.13 MB (virtual 510.9 MB) 4776efea5f09 linuxserver/plexpy "/init" 6 weeks ago Up 6 days 0.0.0.0:18181->8181/tcp plexpy 89.75 MB (virtual 324.2 MB) da4cf5fb541d linuxserver/plexrequests "/init" 6 weeks ago Up 6 days 0.0.0.0:3000->3000/tcp plexrequests 43.48 MB (virtual 373.4 MB)
  9. that should not be necessary. anything under your specific duckdns subdomain is already owned by you. lets say your subdomain is "mydomain": www.mydomain.duckdns.org tor.mydomain.duckdns.org blah.mydomain.duckdns.org These are all already owned by you. I'm not familiar with the duckdns/letsencrypt setup. Is this all in one docker container? or do you have a separate container for duckdns and a separate container for letsencrypt?
  10. this looks good, means your nginx reverse proxy is working as expected. Now you just have to fix your letsencrypt cert to allow for the new subdomain. Edit your letsencrypt docker container and "tor" to the list of subdomains, see attachment
  11. So the subdomain will be something like "tor.test.duckdns.org", not a new/separate duckdns.org subdomain. I use dyndns.info and adding a another subdomain to mydomain.dyndns.info doesnt require any additional configuration on the dyndns.info site, so i assume its the same for duckdns.org. On the letsencrypt docker, you will need to add "tor" to the list of subdomains, and restart the container. The nginx config i pasted earlier goes on the letsncrypt docker container, not the rutorrect docker. You will need to restart the container after you edit site-enabled/default
  12. Yes, it's possible. you need to use the sub domain -- the url/path doesn't work here. this is my nginx config for "tor.mydomain.com" server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name tor.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES12 8-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-R SA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA25 6:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA- DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.100:10080; # change this to your rutorrent ip/port } }
  13. thanks, this works exactly as i needed. Like mentioned above, easy administration is far more valuable to me than the security of a vpn... fail2ban is plenty of security for my needs. thanks!
  14. Hi all, Is there a way to get the default unraid webui behind a reverse proxy? I have the following config location /Dashboard { proxy_pass http://192.168.1.100/Dashboard; add_header X-Frame-Options SAMEORIGIN; } and it almost works, But I'm still missing some elements on the page, and fastcgi php seems to be broken... 2017/06/01 11:49:33 [error] 335#335: *10 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 20x.xx.xx.38, server: _, request: "POST /webGui/include/Notify.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "myhostname.com", referrer: "https://myhostname.com/Main" any ideas?
  15. i was only able to get this working by changing the vDisk bus to SATA (from VirtIO). This option is available under the advanced settings when creating a VM, see attached image.