kriddles

Yes, it's all working now.

My installation For the docker I created a new port container port 80 host port 446 since Apache is not ssl I followed instructions here https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ The only difference was since this apache instance that is created does not use ssl in my letsencrypt proxy_pass must be http:/ not https:/ That got me up and running however I had an issue with the ONLYOFFICE document editing service address When I tried to edit a document I saw an error that said "onlyOFFICE cannot be reached. Please contact admin" Go to your settings -> ONLYOFFICE (under Administration) Make sure the address is correct. Currently it's all up and running.

I'm noobin... how do you assign it to another port?

I'll look into this a bit more but as I am refreshing my Unraid installation I found this docker setup. https://github.com/slydetector/simply-nzedb Seems pretty new and maybe a good source to make a docker instead of setting up an ubuntu VM?

Agreed! I've been using Unraid for a very very long time and it's awesome to see all the changes that have occurred to make it better. The community has been amazing from the get go working on improvements to help out just like this pluggin which I will use for the first time this week. (been using the preclear from Joe L since he wrote it)

I am doing a huge overhaul of my server and this is app is great. I haven't figured out what the Homepage Settings does though. How do I enable Homepage? Is it a tab I can make available somehow? I just found homepage.php which does display my Plex settings that I enabled. Is there some other way that I should be seeing that other than the host:port/homepage.php?

Nice build! I may end up going with your configuration. Thanks for posting this! I have never jumped into using Plex but considering if this would work well enough for transcoding.

Another update- After setting up the plop bootloader the issue is still occurring. Ive got some time this weekend to double check my work and continue to troubleshoot the issue. Im going to probably attempt to use the last unraid version i remember that worked. Or/and get a new usb drive set up.

Just an update- I pulled my pci sata card and the cache drive. Still had the issue. I updated my mobo bios and checked all of the settings. Still had the issue. After more extensive searching I found an issue with some linux kernals and ehci_hcd for usb 2.0. The same error "device descriptor read/64, error -71" is occurring. It is possible that I just have not noticed this issue since updating to 4.5.4 a few months ago which did include a kernal update. I went ahead and updated to the new unraid 4.5.6 rc5 release but still had the issue Next steps I am going to attempt to use the plop boot manager as is described here http://lime-technology.com/forum/index.php?topic=4379.msg39250#msg39250 This would allow me to bypass using ehci_hcd on boot and disable the mobo bios usb legacy support

Thanks for looking Joe Ill check out the bios and go ahead with pulling the sata controller and cache drive then restart to see if the same errors occur. One other thing- I did switch the flash drive to 2 different usb ports thinking maybe the initial mobo usb port was bad. Any other suggestions on what to do to troubleshoot the possible conflict?

Hi I've been enjoying using stock unraid pro for a few years now but would like to jump in with some of the add-ons that this community has worked hard on. I'd appreciate any help as I work through troubleshooting some issues. Right now- I am trying to install the sabnzbd package but whenever I try to installpkg it goes through the process and then everything in /boot disappears. The same thing occurs if I just boot up unraid and copy my syslog to the /boot folder. I pull the flash drive and run a chkdisk on it in windows and it fixes corruptions, then safely remove it and restart unraid but the issue occurs again. This leads me to think the flash is getting set it to read-only but I do not see that occurring in the syslog which I have attached. I recently upgraded my unraid to include a cache drive which I had to also install a new sata 2port pci card. I bought the 2port card from monoprice- but I have not updated the firmware for it. I just need one port on it and it appeared to be working when I successfully set up the cache drive. parity checks run successful but since the /boot is disappearing so anytime I restart the server it runs through another parity check. Unraid version 4.5.4 I'm not sure if my flash drive is possibly failing? or if this is from the hardware upgrade. Any suggestions on next steps? I'll probably remove the cache drive and sata card this evening and restart unraid to see if I see the same issues. And run through a memtest After I telnet in I believe these are the errors occurring: Dec 1 12:53:24 Tower kernel: usb 1-5: reset high speed USB device using ehci_hcd and address 2 Dec 1 12:53:24 Tower kernel: usb 1-5: device descriptor read/64, error -71 Dec 1 12:53:24 Tower kernel: usb 1-5: device descriptor read/64, error -71 Dec 1 12:53:25 Tower kernel: usb 1-5: reset high speed USB device using ehci_hcd and address 2 Dec 1 12:53:25 Tower kernel: usb 1-5: device descriptor read/64, error -71 Dec 1 12:53:25 Tower kernel: usb 1-5: device descriptor read/64, error -71 Dec 1 12:53:25 Tower kernel: usb 1-5: reset high speed USB device using ehci_hcd and address 2 Dec 1 12:53:26 Tower kernel: usb 1-5: device not accepting address 2, error -71 Dec 1 12:53:26 Tower kernel: usb 1-5: reset high speed USB device using ehci_hcd and address 2 Dec 1 12:53:26 Tower kernel: usb 1-5: device not accepting address 2, error -71 Dec 1 12:53:26 Tower kernel: usb 1-5: USB disconnect, address 2 Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] Unhandled error code Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 00 00 d2 b3 00 00 70 00 Dec 1 12:53:26 Tower kernel: end_request: I/O error, dev sdb, sector 53939 Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] Unhandled error code Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00 Dec 1 12:53:26 Tower kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 00 00 08 24 00 00 01 00 Dec 1 12:53:26 Tower kernel: end_request: I/O error, dev sdb, sector 2084 Dec 1 12:53:26 Tower kernel: Buffer I/O error on device sdb1, logical block 1985 Dec 1 12:53:26 Tower kernel: lost page write due to I/O error on sdb1 Dec 1 12:53:26 Tower kernel: FAT: Directory bread(block 2296) faile My hardware specs. 256 mb sandisk cruzer usbdrive mobo ECS A740GM-M Crucial Ballistix Tracer 2GB AMD Athlon X2 4050e Brisbane 2.1GHz Antec 380w earthwatts SATA2 Serial ATA II PCI-Express RAID Controller Card (Silicon Image SIL3132) 5 sata drives 1 cache drive a few fans and fan controller in a centurion 590 case syslog_120110_105.txt