jthacker48

Ditto! LinuxServer rocks!

I saw that you've got glauth and OpenLDAP containers. Did you replace OpenLDAP with glauth or are you using them together? When I've tried to get glauth working, I keep getting an error in line 64 of conf file regarding sha. The container doesn't end up installing so I'm not able to remove the error in appdata. Any ideas on how to get glauth working?

What's the benefit of OpenLDAP vs FreeIPA? I've also seen Guauth. Any suggestions? This seems like the next progression in my home network setup.

You're the man! That worked for me. Although, Unraid won't allow you to enter the ip range without assigning a network address to the server...at least not through the GUI. This is how things look at the moment. It's working but if you're saying I'm going to run into issues, I'm open to making changes.

Unraid 6.6.7 Dell T20 w/ 6 NIC I've got pfsense 2.4 running as a VM in Unraid. I've passed through a quad NIC to pfsense with the following: Domain - mypersonaldomain.com WAN LAN - 192.168.1.0/24 (Secure LAN) IoT - 192.168.2.0/24 (Unsecure LAN) DMZ - 192.168.3.0/24 (Docker Servers) In addition, I'm running HAProxy as a package in pfsense for my Docker usenet servers (i.e. nzbget.mypersonaldomain.com). Unraid has 2 NICs: eth0 - br0 - 192.168.1.0 (Unraid) eth1 - br1 - 192.168.3.0 (Docker) I have assigned static ip addresses for my Docker servers using 192.168.3.X but am not able to access them. In my Docker settings, it doesn't show a gateway for br1 despite it being assigned in the Network settings. Most of the documentation that I've seen is discussing vLANs which is what I'm trying to avoid. BTW, I don't believe it has anything to do with my pfsense settings as all of this was working prior to me implementing the DMZ and eth1/br1. HAProxy was working and everything was communicating when it was running on br0 alone. As of right now, I have allowed DMZ to pass any traffic through pfsense so it's not blocked at all at the moment. Any input on which settings I need to change would be appreciated.

I was able to accomplish this scenario by changing the domain in both pfsense and unraid (under "identification" setting) to mypersonaldomain.com. I've also setup alternative names in pfsense in DNS Resolver under Host Overrides. I'm able to access Unraid by entering tower.mypersonaldomain.com.

I copied the config folder to the new usb and it caused the same issue. No bootable disk when I tried to boot. It looks like I'm going to have to start with a fresh USB. Is there any likely culprit in the config folder that would be causing this? Like I said, I'm hoping to not lose my Shares, Docker, and VMs.

Unraid 6.6.6 Dell T20 I upgraded the Psu on my Dell T20 yesterday. I had an Ultra 650 modular from an old build that wasn't in use. I ordered the 24 to 8 pin cable from moddiy and all went well except Unraid wouldn't boot after replacement. I could access bios. I then created a tiny Linux USB and was able to boot to it. I then created a new Unraid usb and it booted as well. I'd like to transfer as much information as possible from the old USB to the new but am unsure which are likely to be corrupt and which aren't. Primarily, I'm interested in preserving Shares, Docker, and VM. Or should I just replace the syslinx folder only on the old USB? Any suggestions would be appreciated. I've already moved the keys to the new USB.

Please help! Here is my setup that was working: Dell T20 Unraid 6.6.6. 16MB RAM (4x4) 2 Port Sata Controller - Slot 2 (pcie) Cache & Parity (connected to sata controller) 4 HDD (connected to MB) Quad Port HPE NC364t (only 2 ports were working) - Slot 4 (pcie) I was running pfsense on a VM with Acme Certs and HAproxy. All was working without issue except for the 2 ports on NC364t which never worked. In an effort to fix that, I had an extra single NIC laying around so I put it in Slot 4 and moved the quad to Port 1. After doing this, I couldn't get the server to post. It was getting power but no video and not able to get to bios. After a little research, I removed all extra components and the server posted again. I added back each component to identify the troublemaker. When I added the sata controller, it stopped posting. I tried a different pcie slot and still it wouldn't post. I assumed that was the culprit. I then reattached the quad NIC to port 4 with no sata card and it wouldn't post either. After more testing, it seems like anytime that I put a component into any of the pci/pcie slots, the damn server won't post. I've tried every setting possible in the bios (enable/disable pci slots; UEFI/Legacy; etc). I feel like it might have something to do with passthrough of the NIC to the VM but I have no idea if that is the case. I'm stuck and without the sata working, I can't even start the array because too many disk are missing. Ohh..I ran diagnostics at startup and everything turns out fine although it doesn't seem to test pci slots. But memory, gpu, and cpu are all fine according to Dell's pre-os diagnostic.

I recently put a HP NC364T Quad NIC in my Dell T20 running Unraid 6.6.6 with the goal of running pfsense in a VM. While I've got pfsense working now, I've only been able to see 2 of the 4 ports. They didn't show in Unraid before I passed them through to pfsense in VM and they don't show now either. I'm not sure how to test the physical ports of the NIC to determine if this is a hardware issues or whether I'm just missing something in configuration. I should preface this with I bought the NIC for $1 from a recycle shop and it was missing the heatsync. I couldn't believe it worked at all. With that said, I'd love all 4 ports if I'm able. Here is what shows in my System Devices: 07:00:0 and 07:00:1 are passed through to my pfsense VM and 00:19:0 is my onboard LAN. Any guidance is appreciated.

Here are the docker ps results: Here are the logs from LetsEncrypt docker:

I am having issues failing the cert authorization. I believe it is due to my domain host (Google Domains) but I'm unsure. Router: Google Wifi Domain: mydomain.com Subdomain: server.mydomain.com (directed to my ip address) Port Forward http: External 80 to Internal 180 Port Forward https: External 443 to Internal 1443 When I check the logs, I get a "can't connect" error that is likely due to port forwarding or dns. I do not believe it is a port forwarding error as I've changed the port forwards to (80 to 80) and (443 to 443) just to see if I can access the Unraid server from outside my network using server.mydomain.com and that works fine. When I have the ports forwarded to 180 and 1443 and go to server.mydomain.com, it automatically tries to use https. Is it possible that Google Domains is automatically directing traffic to https and in turn not allowing my certs to be authorized? If so, is there a way around it?

I may have to resort to another case but I'm hoping I can fix it with some additional fans (usb or with special adaptors to work with Dell proprietary). If I can't get the temperatures down, I'll look at a case with better air flow.

Life got crazy and I've had my server turned off since this post last year. I'm getting into a new house and trying to make this server usable without overheating. Does anyone know if I could transfer the guts of this server to a rack-mounted chassis with better cooling?

Thanks for the recommendation. Running it now.