So you have created your Letsencrypt certificate using certbot, and now wish to import the generated certificate to your already existing server such as Wildfly or Tomcat that makes use of a Javakeystore, and where you were previously using your self signed certificate that comes along with each tutorial.
Since I’m running iptables modifications via ansible inside docker containers, with Ubuntu as my Host OS, I’m frequently hit by being unable to do something like, when defining iptables rules in init.d :
So in our previous post Haproxy ssl termination for Jekyll we learned how to create a docker container capable of creating self-signed certificates or use previously created certificates to create our haproxy ssl termination to our backends, and always make sure our certificates were re-evaluated by haproxy on each change....
For this blog’s first post I described a simple start for people getting into Jekyll blogging by using docker and how to start a blog using a Jekyll docker based image with a ready to use theme.
So recently while working on some ansible automation, and in my testing container I realized I created by hand a symbolic link I could not remember. By hand I mean I did not automate the creation inside an ansible task.