Santatra Steve

Using the docker container, API is working correctly on localhost or when using bare IP address. However, I cannot make it work behind an reverse proxy. There's no mention of API in the docker documentation. From what I understand, we should use the PROXY_HTTP_BIND environment variable and put the certificate in the client, then the container should read the certificate from the SSL_CLIENT_CERT header. However, that doesn't seems to work. What I've already done: * Using PROXY_HTTP_BIND and TLS_SETUP_ENABLED=later...

Using the docker container, API is working correctly on localhost or when using bare IP address. However, I cannot make it work behind an reverse proxy. There's no mention of API in the docker documentation. From what I understand, we should use the PROXY_HTTP_BIND environment variable and put the certificate in the client, then the container should read the certificate from the SSL_CLIENT_CERT header. However, that doesn't seems to work. What I've already done: * Using PROXY_HTTP_BIND and TLS_SETUP_ENABLED=later...

Using the docker container, API is working correctly on localhost or when using bare IP address. However, I cannot make it work behind an reverse proxy. There's no mention of API in the docker documentation. From what I understand, we should the PROXY_HTTP_BIND environment variable and put the certificate in the client, then the container should read the certificate from the SSL_CLIENT_CERT header. However, that doesn't seems to work. What I've already done: * Using PROXY_HTTP_BIND and TLS_SETUP_ENABLED=later...