Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bamtan

  • Rank
    Advanced Member
  1. the community. snapshots would be cool
  2. Thanks, I'll do that. I'm not configuring Nextcloud so the setup is probably different. Have you had a look at Spaceinvader One's tutorial on YouTube? https://www.youtube.com/watch?v=I0lhZc25Sro It's covered in the YouTube tutorial. Inside the AppData folder of the letsencrypt docker (/appdata/letsencrypt/nginx/proxy-confs)
  3. I managed to get it working. I had to remove the trailing '/' from proxy_pass https://$upstream_znc:6501/; Thanks for the help!!
  4. Over https I changed proxy_pass http://$upstream_znc:6501/; to proxy_pass https://$upstream_znc:6501/; and now i'm able to see the ZNC login (without css, though). Once I log in, I get "403 Access denied POST requests need to send a secret token to prevent cross-site request forgery attacks." Yeah that's all good from me.
  5. No unfortunately it's not working still, even with that extra parameter described in the znc wiki. I still get 502 bad gateway
  6. Could somebody create a NGINX template for Linuxserver.io - ZNC? I've tried but ended up with 502 Bad Gateway server { listen 443 ssl; listen [::]:443 ssl; server_name znc.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_znc znc; proxy_pass http://$upstream_znc:6501/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } I added proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; per https://wiki.znc.in/Reverse_Proxy , without it I still get 502. Thanks!
  7. That did the trick, thanks so much! I also had to change the network model type to e1000-82545em to get the network working Hopefully this helps someone out in the future 🙂
  8. Hi, I'm trying to get Debian 7 to work on Unraid. Currently I am stuck on trying to detect a disk. Here is the XML <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/name/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/debian-7.11.0-amd64-netinst.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> In the VM (I've tried virtio_blk, virtio_scsci options that are available) lspci in VM: Any help would be appreciated, thanks !
  9. Thanks for letting me know! If the issue arises again I will make sure to do this. Glad you found your problem!
  10. I've swapped cables around with drives that have no issues, and the problems remained on the same drive. I've just finished a parity sync with 0 errors, and the array status of Faulty is gone. I'll probably go and buy a new hard drive today, though.
  11. Hello, I have been facing issues with a single harddrive of mine lately, where the UDMA CRC count keeps rising, it is currently up to 4225. I have looked up other users threads regarding the issue, and it all seems to be a physical problem with the data transfer via the cables. I have done what others have said (replace SATA, SATA power cables), though the issue is still happening. Now, Unraid has put the harddrive in error state. Is this a problem with the harddrive itself? No other harddrives have the error, so I don't believe its the SAS controller. I've run diagnostics post-error state, and post-reboot (after adjusting cables again). Unfortunately there are no SMART results for the faulty disk after getting placed in error state. I would appreciate any assistance on this, thank you so much. Faulty drive in question: ST4000VN008-2DR166_WDH31FXE SAS: Fujitsu 9211-8i D2607
  12. It's working for me on the newest update (tag: 156).
  13. I tested with Linuxserver.io's resilio-sync and the timezone is set correctly.. Sorry for that mix up