KingB

Members
  • Posts

    23
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

KingB's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Changed Priority to Minor since there is a workaround.
  2. It worked. Thank you ! So there must be a Bug? Or do you know why the same password is not working as a passphrase?
  3. No there is no non ASCI Chacarter in the passphrase. Just the usual digits, alphabetic and special characters like e.g. `´~+:^^=%[<|
  4. Hello, I just upgraded my Machine from 6.8 RC4 to RC5. After the Upgrade my Machine does not accept the encryption password anymore and the Array is not starting. It is 64 chacters long and complex. It contains quotes as well. After the downgrade to RC4 everything is working again. Does this correspond with the this recent change? Any Information I can provide except for the password ? Management: emhttp: fix improper handling of embedded quote characters in a password
  5. Hello, i just tried to update from RC3 to RC4 and then RC5 got released. When the the update applied and the GUI tells me to reboot, it switches back to default white skin and the docker tab for example is gone. When I reboot i get stuck in the boot menu where I can choose between gui mode, safe mode etc. None of them work. When i choose the regular one, the 5 second automatic boot timer loops. Strange behavior. I restored the the files from the previous folder from the flash drive and now back on RC3. No logs in the log folder. Any logs I can grab? Not many Informations i can provide, I know. Specs: Custom M/B: ASRock - H87M Pro4 CPU: Intel® Core™ i3-4130 CPU @ 3.40GHz HVM: Enabled IOMMU: Disabled Cache: 128 kB, 512 kB, 3072 kB Memory: 16 GB (max. installable capacity 32 GB) EDIT: I did the update again, same behaviour. But this time I downloaded the syslog and Diagnostics before the reboot. The error in syslog? Apr 8 21:34:30 Tower root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Apr 8 21:34:30 Tower root: plugin: running: /tmp/unRAIDServer.sh Apr 8 21:34:31 Tower kernel: usb 4-1: Disable of device-initiated U1 failed. Apr 8 21:34:31 Tower kernel: usb 4-1: Disable of device-initiated U2 failed. Apr 8 21:34:32 Tower kernel: xhci_hcd 0000:00:14.0: Cannot set link state. Apr 8 21:34:32 Tower kernel: usb usb4-port1: cannot disable (err = -32) Apr 8 21:34:32 Tower kernel: xhci_hcd 0000:00:14.0: Cannot set link state. Apr 8 21:34:32 Tower kernel: usb usb4-port1: cannot disable (err = -32) Apr 8 21:34:32 Tower kernel: usb 4-1: USB disconnect, device number 2 Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 07 22 c0 00 08 00 00 Apr 8 21:34:32 Tower kernel: print_req_error: I/O error, dev sda, sector 467648 Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 01 05 2b 40 00 00 02 00 Apr 8 21:34:32 Tower kernel: print_req_error: I/O error, dev sda, sector 17115968 Apr 8 21:34:32 Tower kernel: Buffer I/O error on dev sda1, logical block 17107776, lost async page write Apr 8 21:34:32 Tower kernel: Buffer I/O error on dev sda1, logical block 17107777, lost async page write Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16384) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16385) failed Apr 8 21:34:32 Tower kernel: FAT-fs (sda1): Directory bread(block 16386) failed Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Backup.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/CommunityApplicationsAppdataBackup.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Downloads.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Medien.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/Nextcloud.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/appdata.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/domains.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/isos.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/system.cfg Apr 8 21:34:32 Tower emhttpd: error: put_config_idx, 609: No such file or directory (2): fopen: /boot/config/shares/vdisks.cfg Apr 8 21:34:32 Tower emhttpd: Starting services... Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 8 21:34:32 Tower kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Apr 8 21:34:32 Tower kernel: blk_partition_remap: fail for partition 1 tower-diagnostics-20180408-2137.zip
  6. Hello, I am using the nginx reverse Proxy for my Nextcloud + Unifi Controller and Unifi Guest Portal. It is based on the subdomain. nextcloud.* unifi.* and unifi-gastportal.* The Nextcloud works fine, secure connection etc. The Nextcloud runs in Bridge Mode with Port 444 and 81. (Unraid IP 192.168.4.18) On the other hand the unifi Controller. It runs in the br0 Mode, so that it gets an own IP Adress (192.168.4.2) (otherwise i get STUN Errors). But i cannot proxy_pass to the unifi Controller. It only works if I run the container in bridge mode with the unraid IP. I always get 502 Bad Gateway nginx/1.12.2 I use default config files except for ssl, but with the default one it does not work either. This is what i added to the default site config: (the first works, the second not. Looks like an network error?) server { listen 443 ssl; #root /config/www; index index.html index.htm index.php; server_name nextcloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass https://192.168.4.18:4443; } } server { listen 443 ssl; #root /config/www; index index.html index.htm index.php; server_name unifi.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; proxy_pass https://192.168.4.2:8443; } } What am I doing wrong? Is it a bug? I can reach the controller if I use the static IP instead of the subdomain. from the error.log: 2018/03/22 04:06:11 [error] 379#379: *319 connect() failed (113: Host is unreachable) while connecting to upstream, client: 192.168.4.1, server: unifi.*, request: "GET / HTTP/1.1", upstream: "https://192.168.4.2:8443/", host: "unifi.xxxxxx"
  7. Hello :-) Addind an option to encrypt makes Unraid the perfect operating system for me. Is there any schedule for the feature ? Not Asking for a specific date, maybe for a roadmap or something ;-).
  8. Hey guys, i used the guide to update to NC 11 that was on a few pages ago. Worked perfectly. Since i use keepass and sync my Database with my Nextcloud, i want to use keeweb. But i activated the app (latest Version) and tried to use it. When i click on the app, the pages opens but stays blank. Same happens if i click on the database file. Anyone got it working? It would be a great app to log into my accounts anywhere in the world without downloading anything.
  9. Thank you for that answer :-) I changed it to nogroup and synced the devices with the big files. After that I restarted the container the chmod did its job. So, for now I am fine, since small files and changes in files getting synced without any problem. If the problem occours again, I know how to temporary fix it and that should be enought for now.