Last post Jan 21, 2020 08:59 AM by Jorge J Gonzalez
Jan 21, 2020 08:59 AM|Jorge J Gonzalez|LINK
What's the current state?
Docker for Windows running an instance of a Docker (Linux) image that runs a Web API built on ASP.NET Core 2.2 accesible via HTTPS thanks to a self-signed certificate (generated
by Visual Studio).
Currently, Web API is not accesible from other machines due to a SSL verification failure, it's only working on localhost.
I can't make the Web API accesible via HTTP to later provide HTTPS connection using a proxy server because the Web API is using ASP.NET Core Identity and it cannot be executed without a secured connection.
I can't generate LetsEncrypt certificates dinamycally because the domain has restricted access (is only accesible in my organization's network) so LetsEncrypt can't access to my IP to validate ownership.
How did you get the certificates?
DHCP server was changed temporally to relate the domain to an accessible IP
Apache server was mounted on that machine
Certificates were generated with certbot
DHCP server was changed again to point to the desired restricted access IP
I want to use generated files to enable secure connections with trusted certificates on this restricted access IP.
What's the desired state?
Docker for Windows running an instance of a Docker (Linux) image that runs a Web API built on ASP.NET Core 2.2 accesible via HTTPS thanks to a LetsEncrypt SSL trusted
What have you tried?
As Web API cannot be ran on insecure connections, I can't get that insecure connections and turn them into secure connections via Apache/Nginx proxy server
As far as I'm concerned, HTTPS requests with self-signed certificate cannot be turned into HTTPS requests with trusted LetsEncrypt certificate with a proxy server.