I don’t know why I’m having so much trouble with this - especially after watching Tom’s video on this. Although his examples weren’t exactly what I’m working with, the principles should still be the same.
So, I’ve got a FQDN - myhost.mydomain.com. I’m trying to hit my PLEX server through that FQDN. My PLEX server is running on a VM and I can access it within my LAN at 192.168.1.10:32400. Further, from another machine on my LAN, “nslookup myhost.mydomain.com” shows:
This tells me that my domain resolver in pfSense is operating correctly, right?
Now, here at my house, I’m running pfSense as a VM. On that same physical machine exists a Linux VM from which I run all of my dockerized media apps. The IP of said VM is 192.168.1.10. If I SSH into that VM, then enter the same nslookup query, it returns:
I replaced those numbers with x’s, but that’s my WAN. Is this normal behavior? Shouldn’t the output of nslookup be the same?
Anyhow… I’ve got ACME set up just like in Tom’s video and the cert appears to have gone through and is valid. On to HAproxy.
Here is my front and back end. Keep in mind, I can reach PLEX from within my LAN at 192.168.1.10:32400 and that is an http, not https.
What have I overlooked?