Hello, I've been trying to navigate a way of using the docker version of Gluu server on my host that's already got a NGINX/Apache system in place. Therefore I remapped NGINX docker exposed port to something else and used a reverse proxy rule to map port 443 on the host to port 80 (internal) on NGINX docker. Alas I am getting a number of errors relating to LDAP server not being reachable. However, from what I've read, Gluu systems all use and share certificates from the docker NGINX server? So terminating TLS looks like it would be problematic? I was watching a video by your founder and in the comments someone asked if it supported reverse proxy and he said yes. So surely there must be a best way of doing this? From what I've read so far it appears very, very messy with many rewrites etc... Simply, I am wanting to integrate the Gluu system on a web server that also supports docker-compose. Since I already have a wildcard certificate being produced and managed for the domain on the host server whilst also taking advantage of mod_sec ect... for traffic and just offload non-TLS traffic to the Gluu NGINX docker. Any other port traffic can be exposed if needed. Is this really not achievable? I hope that some more clarity can be definitively shed on what is or isn't supported with using an external reverse proxy. Thanks