On Thu, 26 Mar 2015 08:30:23 +0100 mxb wrote: > > > > Thank you for the suggestion. I was not aware of "pound." > > I’d rather go for relayd. Which is out of the box. No need to install “yet > another port and make sure it is up2date”.
httpd is based on relayd code which would reduce the scope of the test (a cluestick). >> When I try "https://10.0.128.67/index.html" - I get a nice message from >> firefox asking me to accept a problem certificate (this was expected, >> the certificate is the "correct" one), and when I do accept the >> certificate, I get the index page. >> So, I am not sure what is wrong, but it appears httpd is not responding >> to https requests, even with the "listen on tls" line in the >> configuration file. >> Is there anything for me to look at/consider in trying to correct this? I don't understand what you are saying by '"correct" one' but to me this suggests you have issues even with pound and perhaps I would try another browser or firefox on another client and try another certificate perhaps from another CA or install a newer snapshot or re-install a release before wondering if there is an issue with httpd or libressl whilst monitoring the list to see if anyone else has an issue? Thankfully re-install on OpenBSD is super quick but you do have to follow www.openbsd.org/current.html for snapshots and I think www.openbsd.org/plus.html for release upgrades (4.5 -> 4.6 etc.)