I'm running

[.] stunnel 5.66 on x86_64-redhat-linux-gnu platform [.] Compiled/running with OpenSSL 3.0.5 5 Jul 2022

on

lsb_release -rd Description: Fedora release 36 (Thirty Six) Release: 36 uname -rm 5.19.15-201.fc36.x86_64 x86_64

it's setup to frontend terminate TLS in front of a bind9 nameserver instance's statistics (http-only) web server backend.

it's a trivial config,

cat /etc/stunnel/stunnel.conf debug = 5 syslog = yes

[bind9-stats] accept = ns.example.com:10000 connect = 127.0.0.1:10001

sslVersion = TLSv1.3 ciphersuites = TLS_CHACHA20_POLY1305_SHA256

requireCert = yes verifyChain = yes verifyPeer = no

CAfile = /usr/local/etc/stunnel/example_CA.CHAIN.crt.pem cert = /usr/local/etc/stunnel/ns.example.com.COMBINED.pem key = /usr/local/etc/stunnel/ns.example.com.server.key.pem

sessionCacheSize = 1 sessionCacheTimeout = 360

and it does provide access, with no apparent/reported *error*, afaict.

but, on initial access, i.e. first nav to the exposed site page, I get a blank page. simply RELOADING the browser page cures the problem. page display, with current/correct data -- as do all (sub)links on the page. this is repeatable behavior in multiple browsers (Firefox, Chromium, Chrome).

so far i've not found any indication of an actual error -- only this 1st-page-visit-is-blank behavior, unique to my stunnel usage. other/heavier frontends have no such issue. odd, but not fatal. or even, apparently, problematic (so far, i think).

is this a pebkac/config issue? or a known issue/bug? other?