1
Tutorials and FAQs / Re: Tutorial 2023/04: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating
« on: May 25, 2023, 01:30:14 pm »Shoot. I thought I put a note in there about logs...
Outside of the informational log, there is nothing logged. In the informational, I see connections originating from the outside. Nothing for hitting this particular internal IP/host, no error. Logs accessed from Services/HAProxy/Logs, enabled all. Nothing here is pertinent near as I can tell. When this internal (BMC) resource loads, I see an unsigned cert which tells me it is not hitting haproxy.
When I access plex, it originates from lan IP then hits the public IP and I can see this logging client IP, it loads. This works from inside/outside. My other external service also works inside/outside. An override with plex
I created a backend, server, and map file for internal services.
I've tried with and without unbound. With and without overrides. Right now I am using unbound, opnsense is my DNS. It loads...attempt to access the web service...I get a self signed cert. This is the head scratcher, same result whether I use AD or Unbound DNS so assuming something I've missed.
What I am really after is 'what did I miss in the configuration' because I'll be setting up another HAproxy box targeted at internal only resources as well.
So, AD DNS is not in the picture, in this context, I am in the same spot.
I'll take another stroll through the tutorial.
Sorry I still don't know what your issue is exactly now?
Your text is very confusing to read.
What I took from it is that the internal and external accesses are working but it is not presenting a trusted cert?
External works perfect inside and outside. Get a lets encrypt cert. We're happy, nothing to do.
Internally? I get a self signed cert, nothing is logged in HAProxy.
I went through the tutorial again last night. Step 7.2 for the FQDN rule...I see you have a domain value, but I am unable to save this condition because my domain is not a valid ipv4 address?
I can plug in 'my.test.com', it will accept and tests out OK. If I use 'lan.scobar.pw', it will not accept the value, gives error below. Outside of informational log, nothing is recorded.
[NOTICE] (67194) : haproxy version is 2.6.13-234aa6d
[NOTICE] (67194) : path to executable is /usr/local/sbin/haproxy
[ALERT] (67194) : config : parsing [/usr/local/etc/haproxy.conf.staging:73] : error detected while parsing ACL 'acl_64685bef85c4e2.08714329' : 'lan.scobar.pw' is not a valid IPv4 or IPv6 address.
[ALERT] (67194) : config : parsing [/usr/local/etc/haproxy.conf.staging:78] : error detected while parsing switching rule : no such ACL : 'acl_64685bef85c4e2.08714329'.
[ALERT] (67194) : config : Error(s) found in configuration file : /usr/local/etc/haproxy.conf.staging
[ALERT] (67194) : config : Fatal errors found in configuration.