@dukeart so, removing the TLS block doesn’t seem to change anything and the service is def running as I can pull it up in the browser on “http://192.168.1.63:443”
I realize that’s http on port 443, but for some reason that I can’t recall anymore, we needed to do it that way for tls offloading to caddy…
thanks