Nyghthawk

Okay I am going to need a bit more help. This whole time I thought I was setup properly for reverse proxy, and low and behold, it ONLY works when I am on my LAN....of course right!?!??! So i have nginx proxy manager installed. http 1880 https 18443 On my router, I have Ports 80 forwarded to ip (my unraid server) 192.168.0.133:1880 Ports 443 forwarded to ip (my unraid server) 192.168.0.133:18443 On my domain I have A Record Host * (to allow all subdomains) Value: My IP (its static) TTL Automatic On NGINX setup I would have Source: subdomain.mydomain.com Destination: 192.168.0.133:PortToService So when I go to subdomain.mydomain.com it would load up. Thinking this worked Tried from outside, and got buttsquatt. When I go to http://mypublicip:80 or http://mypublicip I get the 404 error nginx (that I setup with the proxy) So I tried Source: subdomain.mydomain.com Destination: publicIP:PortToService And get a 502 Error. Please help? EDIT: to add. When I go to http://mypublicip or http://mypublicip:80 I get the 404 error code I setup with the proxy manager.

So i had this long post about things not working. And I got it working. However, need a bit of help on this last one. Trying to get my unifi controller accessible. When I am local and i type http://localip:port to access the login, it lets me log in, then gives me an error on the certificate, etc. When I type in http://unifi.domain it asks to log in like normal, but then does not log in giving me an error. is this a setting I am missing, do i need to customize my commands for this one? So far I think everything else is working. (crosses fingers) also, I did a blanket wildcard record on my domain, so all subdomains will point to "proxy manager has not been setup yet" is this ok? also tried to add SSL, and i get an "internal error", and nothing works, any help with that? apparently creates an SSL but then i get a cipher mismatch or something like that error.

thank you, will get on that!

so if i just buy a domain name from <insert provider> I just create subdomains there and nameserver it to my static ip? or sonarr.mydomain.com points to 111.222.333.444:1234 ? or should i still use this to hide the ports? so then its sonarr.mydomain points to sonarr.mypublicip

have static ip....but then need to remember my IP for each "subdomain"? sonarr.##.##.##.## etc?

do i still need like duck dns to give it a name or something?

Thanks for the replies!

im on 5.9.29 or the 5.9.x release, and the docker image is showing an update. is this correct?

Having issues like many others. Installed following the video. Changed to br0, custom IP different than unraid ip. matched server ip to custom ip tried interface as eth0 and br0 both failed. have --dns 127.0.0.1 or whatever it is in the custom are, including --dns 1.1.1.1 and 8.8.8.8 Issue: Blocklist = 0 and I cannot get gravity to update, nor access pi.hole/admin. so i know something is going wrong here. Pi-hole blocking is enabled Neutrino emissions detected... [✗] Pulling blocklist source list into range No source list found, or it is empty Number of domains being pulled in by gravity: 0 Nothing to whitelist! Number of regex filters: 0 [✓] Parsing domains into hosts format [✓] Cleaning up stray matter [✓] DNS service is running [✓] Pi-hole blocking is Enabled any help here? i dont want to just add in lists if gravity wont update. EDIT: Did a pihole -d said could not find IPv4 on the config file, it had the same ip but it said could not find 192.168.0.132/24 and in the config file it only had 192.168.0.132, so i added the /24.... this still didn't fix the issue. then tried a pihole -r, selected the first option, this did NOT work tried pihole -r selecting the second option, did NOT change any settings, and it seems to work now.

Got this running without much of a problem, and for some reason, just decided to check my logs. Wondering, what this is..... [22;36m:0 webRtcId 9 connected in 0.229 seconds! This is STUN from 172.17.0.11:53157 -> 192.168.0.114:57726[22;37m [01;33m:0 TURN channel binding 0x4003 failed[22;37m [01;33m:0 TURN channel binding 0x4000 failed[22;37m [01;33m:0 TURN channel binding 0x4004 failed[22;37m [01;33m:0 TURN channel binding 0x4001 failed[22;37m [01;33m:0 TURN channel binding 0x4002 failed[22;37m [01;33m:0 STUN timed out: STUN id: 3; fd: 204 172.17.0.11:34508 -> 192.168.0.114:52817 (eth0) DTLS id: 8 (192.168.0.133:34508) (PEER)[22;37m [01;33m:0 webRtcId 10 terminated with code: (-2147090409) WebRTC connection interrupted from far side[22;37m [01;33m:0 read() failed on a timer FD. Error was: (9) Bad file descriptor[22;37m this continues on from different PORTS but the same IP.... 192.168.0.114 is my iphone that I occasionally run the unifi app on to check on things. Is this just the controller trying to further communicate with the ios controller/app too? also second question. I am currently NOT updating every time, because I don't know how to revert back to a different version. So if i end up updating, how can I revert back to the previous version?

Not sure what happened, I think cause I have apps on auto-update. Had access to webui for a while. Have done updates in the past no issues. Now when I go to access the webui, it either loops back to the login as if it didn't login, or logs in with "Error: Unknown" The log only shows ******** Information ******** To control qBittorrent, access the Web UI at http://localhost:8080 The Web UI administrator user name is: admin Tried stopped and restarting the docker. Same issue. Tried different browsers and computers. This is in my config WebUI\Address=* WebUI\AuthSubnetWhitelist=@Invalid() WebUI\AuthSubnetWhitelistEnabled=false WebUI\HTTPS\Enabled=false WebUI\LocalHostAuth=true WebUI\Port=8080 WebUI\ServerDomains=* WebUI\UseUPnP=true WebUI\Username=admin Noticed it does not have Password=?

and if i don't have a domain but just an IP? lol

Two questions here: 1) I have a VFS mounted Gdrive with Rclone on my Unraid. When I transfer from this mount I get about 100-150mbit/sec download (10-15MB/sec). This does not matter if it is to the array, or using my win10 PC (on the same network accessing the shared mount). Tested drag and drop of the two folders, tested with a simple rclone --progress in CLI on the UNRAID and also with Teracopy on the windows machine. I had figured this was just the speed I get with GDrive. After talking with others on rclone forums, they get up to 1000mbit (1Gbit) downloads) (950MB/sec). So then i ended up being archaic and installed rclone on my windows 10 machine and mounted directly, by passing UNRAID mount. I used the EXACT same mount options between the two. On my windows rclone mount transferring to a local windows drive, I get speeds of about 200-300mbit/sec (my internet MAX speed which is what I should be getting). So I had figured something is going on with my UNRAID network. I then installed speedtest on the UNRAID and did several tests, all of which equal to my internets MAX speed. I then test another transfer from the rclone mount, and sure enough, back to the 100-150mbit/sec (half of my max). At this point I think there is something funny going on with either 1) my mount/rclone 2) my network settings. Can anyone help? and Qestion #2 You talk about setting up CloudFlare CDN, as I do plan on having a remote PLEX at some point, do you have a guide for this?

Had rclone installed for a while. Survived many reboots. Today it failed to survive a reboot. In the plugins directory I get /boot/config/plugins-error/rclone.plg ERROR With no other information, I tried viewing the log, nothing. do I just reinstall it? what? found out rclone.org is down, so after a reboot, rclone plugin will NOT reinstall....

Errr, its part of my motherboard, not a separate controller lol! Intel Corporation - S2600CP

New one also didnt pick up my drives, anyway I can help?

Glad you got it, hopefully it can update, cause the drive(s) that I think is the problem drive(s) are the ones that arent being found lol!

I willl start there. ty

Not that I am aware of. 14 SATA connectors on the Motherboard is all I have. I think its split up in 10 and then 4

I went from 79%, found this thread, Did a few commands to see the sizes of my container folders refreshed, 83%, Refreshed 89%. Wow. Where do I start? du -h -d 1 /var/lib/docker/ 7.4G /var/lib/docker/containers 69G /var/lib/docker/btrfs 35M /var/lib/docker/image 52K /var/lib/docker/volumes 0 /var/lib/docker/trust 108K /var/lib/docker/network 0 /var/lib/docker/swarm 2.5M /var/lib/docker/unraid 0 /var/lib/docker/plugins 16K /var/lib/docker/builder 0 /var/lib/docker/tmp 76G /var/lib/docker/

Installed this is what I have. and this is what is "found" even after re-scans. Missing a few drives there. (3 total) 1 3tb WD 1 2TB WD 1 5TB Seagate any advice?

Thanks for the quick reply, i was hoping it was more due to 1) than 2)..... any way to kind of install it anyways to test? I really just want to see how the front-end handles 40-50k torrent files.

I realized I had made a request for the Flood Docker to be made, and when I looked over your repository, it shows that it is in process but not released to the public. Is this due to 1) Flood not quite being in a released state or 2) that the docker is not working correctly yet?

EDIT: added tower-diagnostics-20180118-1124.zip Trying now Aprox. How long should I wait for this to collect before I tag it into the "unreasonably" slow category? ~8 mins still here Also tried to shut down array, download diagnostic from webgui, and shutdown the system, all would not run. Next option is hard power at the actual hardware. These are at the end of the "log" file in Tools--->SysLog Jan 18 08:45:10 Tower login[100967]: ROOT LOGIN on '/dev/pts/1' Jan 18 08:52:20 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 08:52:23 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 08:54:20 Tower nginx: 2018/01/18 08:54:20 [error] 9775#9775: *124825 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.102, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower.local", referrer: "http://tower.local/Settings/FixProblems" Jan 18 08:54:23 Tower nginx: 2018/01/18 08:54:23 [error] 9775#9775: *124659 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.102, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower.local", referrer: "http://tower.local/Settings/FixProblems" Jan 18 09:18:20 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 09:19:49 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 09:20:01 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 09:20:06 Tower root: Fix Common Problems Version 2018.01.18 Jan 18 09:22:01 Tower nginx: 2018/01/18 09:22:01 [error] 9775#9775: *126675 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.102, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower.local", referrer: "http://tower.local/Settings/FixProblems" Jan 18 09:22:06 Tower nginx: 2018/01/18 09:22:06 [error] 9775#9775: *126995 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.102, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower.local", referrer: "http://tower.local/Settings/FixProblems" Jan 18 09:29:04 Tower login[87910]: ROOT LOGIN on '/dev/pts/1' Jan 18 09:35:06 Tower nginx: 2018/01/18 09:35:06 [error] 9775#9775: *129157 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.102, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "tower.local", referrer: "http://tower.local/Main" Jan 18 09:41:38 Tower shutdown[124016]: shutting down for system halt Jan 18 09:42:09 Tower shutdown[125495]: shutting down for system halt So I did the unthinkable and just hard shut it off at the system. It has rebooted and started a parity check. I will see how this turns out. Thought id just try and open a folder while going through this check to see if its better. Nope, still unreasonably slow just trying to open a single folder. My normal parity check speed is about 80-100+mb It has been going 2.2mb/sec since starting otal size: 8 TB Elapsed time: 18 minutes Current position: 17.4 GB (0.2 %) Estimated speed: 1.7 MB/sec Estimated finish: 55 days, 2 hours, 43 minutes Updated Speed!!! Total size: 8 TB Elapsed time: 30 minutes Current position: 17.4 GB (0.2 %) Estimated speed: 881.3 KB/sec Estimated finish: More issues: I can restart it. it will parity check fast, then all of a sudden slow back down at RANDOM times. All Dockers/VMS disabled I am able to access data for the time the parity check is running fast then it hits a snag and this slowdown happens (can be 5 seconds 5 mins or 50 mins) I reseated all my drives, will try reconnecting every SATA port next Here it as after a reboot, will not try anything else to it at all right now Total size: 8 TB Elapsed time: 3 minutes Current position: 25.0 GB (0.3 %) Estimated speed: 110.3 MB/sec Estimated finish: 20 hours, 6 minutes Sync errors detected: 0 Waiting to see how long this lasts ONe thing to note, when the parity check is working the drives show activity But when the parity slows down (back to the original unable to access anything) the drives show 0 read/0 write And its done Itll just keep going down and down in speed and not do anything more. watching the log as this happened, this is what i gathered was new Jan 18 12:34:02 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jan 18 12:34:02 Tower kernel: IP: isci_task_abort_task+0x18/0x334 [isci] Jan 18 12:34:02 Tower kernel: PGD 0 P4D 0 Jan 18 12:34:02 Tower kernel: Oops: 0000 [#1] PREEMPT SMP PTI Jan 18 12:34:02 Tower kernel: Modules linked in: xfs nfsd lockd grace sunrpc md_mod bonding igb ptp pps_core i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ipmi_ssif ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd isci libsas intel_cstate intel_uncore intel_rapl_perf ahci libahci i2c_i801 i2c_core scsi_transport_sas wmi ipmi_si button [last unloaded: pps_core] Jan 18 12:34:02 Tower kernel: CPU: 0 PID: 29155 Comm: kworker/u264:3 Not tainted 4.14.13-unRAID #1 Jan 18 12:34:02 Tower kernel: Hardware name: Intel Corporation S2600CP/S2600CP, BIOS SE5C600.86B.02.03.0003.041920141333 04/19/2014 Jan 18 12:34:02 Tower kernel: Workqueue: scsi_tmf_8 scmd_eh_abort_handler Jan 18 12:34:02 Tower kernel: task: ffff880c05881c00 task.stack: ffffc90023394000 Jan 18 12:34:02 Tower kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci] Jan 18 12:34:02 Tower kernel: RSP: 0018:ffffc90023397ce8 EFLAGS: 00010296 Jan 18 12:34:02 Tower kernel: RAX: ffffffffa00b4cbb RBX: ffff880bd77bf9a8 RCX: 0000000000000000 Jan 18 12:34:02 Tower kernel: RDX: ffff880c0d020420 RSI: 0000000000002100 RDI: 0000000000000000 Jan 18 12:34:02 Tower kernel: RBP: 0000000000000000 R08: 000000942cd7ac00 R09: 0000000000000000 Jan 18 12:34:02 Tower kernel: R10: ffffffff81c03ea8 R11: ffff880c05881cc0 R12: ffff880c030f1800 Jan 18 12:34:02 Tower kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000 Jan 18 12:34:02 Tower kernel: FS: 0000000000000000(0000) GS:ffff880c0d400000(0000) knlGS:0000000000000000 Jan 18 12:34:02 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 18 12:34:02 Tower kernel: CR2: 0000000000000000 CR3: 0000000001c0a001 CR4: 00000000001606f0 Jan 18 12:34:02 Tower kernel: Call Trace: Jan 18 12:34:02 Tower kernel: ? __freed_request+0x34/0x86 Jan 18 12:34:02 Tower kernel: ? freed_request+0x31/0x4b Jan 18 12:34:02 Tower kernel: ? __blk_put_request+0xed/0x131 Jan 18 12:34:02 Tower kernel: ? blk_put_request+0x38/0x4b Jan 18 12:34:02 Tower kernel: ? scsi_execute+0x168/0x177 Jan 18 12:34:02 Tower kernel: ? scsi_test_unit_ready+0x45/0x99 Jan 18 12:34:02 Tower kernel: ? cpuacct_charge+0x2c/0x6b Jan 18 12:34:02 Tower kernel: ? __accumulate_pelt_segments+0x1d/0x2a Jan 18 12:34:02 Tower kernel: ? dequeue_entity+0x49a/0x4bf Jan 18 12:34:02 Tower kernel: ? pick_next_task_fair+0x227/0x3d9 Jan 18 12:34:02 Tower kernel: ? put_prev_entity+0x21/0x2d9 Jan 18 12:34:02 Tower kernel: sas_eh_abort_handler+0x2a/0x3c [libsas] Jan 18 12:34:02 Tower kernel: scmd_eh_abort_handler+0x35/0x8f Jan 18 12:34:02 Tower kernel: process_one_work+0x146/0x239 Jan 18 12:34:02 Tower kernel: ? rescuer_thread+0x258/0x258 Jan 18 12:34:02 Tower kernel: worker_thread+0x1c3/0x292 Jan 18 12:34:02 Tower kernel: kthread+0x10f/0x117 Jan 18 12:34:02 Tower kernel: ? kthread_create_on_node+0x3a/0x3a Jan 18 12:34:02 Tower kernel: ? do_group_exit+0x95/0x95 Jan 18 12:34:02 Tower kernel: ret_from_fork+0x1f/0x30 Jan 18 12:34:02 Tower kernel: Code: e8 5d 41 5c 41 5d c3 b8 05 00 00 00 c3 b8 05 00 00 00 c3 41 57 41 56 41 55 41 54 55 48 89 fd 53 4c 8d 75 08 48 81 ec 68 01 00 00 <48> 8b 07 c7 44 24 10 00 00 00 00 c7 44 24 18 00 00 00 00 48 8b Jan 18 12:34:02 Tower kernel: RIP: isci_task_abort_task+0x18/0x334 [isci] RSP: ffffc90023397ce8 Jan 18 12:34:02 Tower kernel: CR2: 0000000000000000 Jan 18 12:34:02 Tower kernel: ---[ end trace 8b38e50124b0ffca ]--- Trying two things.... Seemed FixCommon Problems would stall everything (it randomly started prior to the previous error) Removed that Also started in maintenance mode to do a full parity check. Crossing Fingers, I have currently passed my longest "check" so far. Total size: 8 TB Elapsed time: 14 minutes Current position: 91.3 GB (1.1 %) Estimated speed: 112.1 MB/sec Estimated finish: 19 hours, 36 minutes Update: Got 4 hours + in parity check and was still averaging 80-100mb/sec which is NORMAL. Stopped parity check. Stopped maintenance mode. Started Array, Started parity check again. Seemed to be running fine. Turned VM back on. Turned ONE docker (the last docker img I installed). Plex. So far Plex Running. VM Running. And Parity check going strong. Will enable docker(s) one by one and let run to see if any of the dockers are causing this problem, else seems like its the Fix Common Problem thing.

Hopefully that topic covers the jist of everything. About 3-5 days ago, maybe less, these issues started. No hardware change. No power failures, my system had been up for 40+ days at that point. Prior to this, there was ONE folder that would sometimes take 10-30 seconds to load, and that was because it has 30-40k FILES/FOLDERS in its main directory. Other than this, never really had trouble unless I was trying to do like 30-40 things to the server at one point. Issue now: Lately when I try and open ANY folder on the server, it takes 40-50 seconds + (up to 2-5 mins) to just open a simple folder that would take half a second prior (like normal). So i tried just a simple restart. Same thing. So then I said, let me update to 6.4. Restarted. Same Thing. So i have tried "Fix Common Problems" Scan. This normally would take 1-2 mins to run. I am at 10 mins and it is still saying "Scanning" I have tried to look at the log, and it just tries to load the log over and over and over. I have a VM on the server, (ubuntu) I log into that, and use the command line to access these same directories, and it lists everything for me instantly. I am trying to figure out if its a particular drive, file system, maybe a windows thing? I cannot troubleshoot this. I can access the terminal, so please help me with some command lines to get this diagnosed. Anyone?