# Automatic HTTPS with lets-encrypt?

**URL:** <https://forums.balena.io/t/automatic-https-with-lets-encrypt/5463>\
**Category:** openBalena\
**Created:** [February 26, 2019, 1:12pm UTC](https://forums.balena.io/t/automatic-https-with-lets-encrypt/5463 "2019-02-26T13:12:57Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![whm](https://avatars.discourse-cdn.com/v4/letter/w/ce7236/32.png) [@whm](https://forums.balena.io/u/whm)\
**Post date:** [March 1, 2019, 5:39pm UTC](https://forums.balena.io/t/automatic-https-with-lets-encrypt/5463/9 "2019-03-01T17:39:24Z")

</div>

> [@richbayliss](#):
>
> I am not sure moving to Caddy would be desirable in this instance, since the issue you would find here is that port 443 is not being used exclusively for HTTPS/TLS traffic; it is also being split off for the VPN traffic which requires certain introspection, which I don’t think is supported in Caddy.

I don’t completely understand, but I’m glad to hear you appreciate the problem and are working on a solution. 👍

I think Caddy and Haproxy could be used together. Haproxy would split off the VPN traffic but Caddy would handle the HTTPS routing.

---

_[View the full topic](https://forums.balena.io/t/automatic-https-with-lets-encrypt/5463)._