# Https with let's encrypt behind a vpn?

**URL:** <https://meta.discourse.org/t/https-with-lets-encrypt-behind-a-vpn/112726>\
**Category:** Self-hosting\
**Created:** [March 27, 2019, 3:16pm UTC](https://meta.discourse.org/t/https-with-lets-encrypt-behind-a-vpn/112726 "2019-03-27T15:16:07Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![tbeaudry](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@tbeaudry](https://meta.discourse.org/u/tbeaudry)\
**Post date:** [March 27, 2019, 4:46pm UTC](https://meta.discourse.org/t/https-with-lets-encrypt-behind-a-vpn/112726/13 "2019-03-27T16:46:21Z")

</div>

I’m the sysadmin of the server, so i created the CSR, and I will get a certificate signed in a few hours.

@Stephen To be honest, this is the first time I’ve heard of SAML. Everyone else here uses LDAP, so that is why I installed the plugin: [GitHub - jonmbake/discourse-ldap-auth: Discourse plugin to enable LDAP/Active Directory authentication. · GitHub](https://github.com/jonmbake/discourse-ldap-auth) , which i got to work already. Single-sign on is working on our workstations, so switching to SAML makes sense, I’m going to see if’s supported elsewhere at my University.

---

_[View the full topic](https://meta.discourse.org/t/https-with-lets-encrypt-behind-a-vpn/112726)._