mod_net_proxy does currently not support Direct TLS ports.
This is listed as a limitation which is not trivial to solve in mod_net_proxy's README, so this issue should simply serve as a milestone for this feature.
Motivation:
Currently we're using HAProxy to proxy towards our Prosody instance, which works without further hoops for the StartTLS ports and https/5281 (the latter without mod_net_proxy).
For the Direct TLS ports (5223 and 5270) I currently have to use go-mmproxy running on the Prosody instance, which then proxies to the locally running Prosody. This works because go-mmproxy supports the PROXY protocol, but I would really like to get rid of that extra layer and let prosody/mod_net_proxy handle the connection itself.
mod_net_proxy does currently not support Direct TLS ports. This is listed as a limitation which is not trivial to solve in mod_net_proxy's README, so this issue should simply serve as a milestone for this feature. Motivation: Currently we're using HAProxy to proxy towards our Prosody instance, which works without further hoops for the StartTLS ports and https/5281 (the latter without mod_net_proxy). For the Direct TLS ports (5223 and 5270) I currently have to use go-mmproxy running on the Prosody instance, which then proxies to the locally running Prosody. This works because go-mmproxy supports the PROXY protocol, but I would really like to get rid of that extra layer and let prosody/mod_net_proxy handle the connection itself.