<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssl on Cristian Livadaru's Blog</title><link>https://cristian.livadaru.net/tags/ssl/</link><description>Recent content in Ssl on Cristian Livadaru's Blog</description><generator>Hugo</generator><language>en-us</language><copyright>Cristian Livadaru</copyright><lastBuildDate>Wed, 24 Jul 2024 18:39:11 +0000</lastBuildDate><atom:link href="https://cristian.livadaru.net/tags/ssl/index.xml" rel="self" type="application/rss+xml"/><item><title>Postfix complains about Cannot start TLS: handshake failure</title><link>https://cristian.livadaru.net/postfix-tls-error/</link><pubDate>Wed, 24 Jul 2024 18:39:11 +0000</pubDate><guid>https://cristian.livadaru.net/postfix-tls-error/</guid><description>Ok, this was a huge waste of time going down this rabbit hole. Postfix complains about handshake failure when trying to send emails over TLS. Non TLS works fine, receiving mails via TLS works fine, what gives?</description></item><item><title>Generating let's encrypt wildcard SSL certificates with INWX and DNS challenge</title><link>https://cristian.livadaru.net/npm-wildcard-ssl-inwx/</link><pubDate>Fri, 19 Jul 2024 12:39:11 +0000</pubDate><guid>https://cristian.livadaru.net/npm-wildcard-ssl-inwx/</guid><description>Using INWX as a DNS provider for the DNS challenge with nginx-proxy-manager and Let&amp;rsquo;s Encrypt wildcard SSL certificates is easy, but what the hell is that shared secret?</description></item><item><title>Generating let's encrypt wildcard SSL certificates with ISPConfig and DNS challenge</title><link>https://cristian.livadaru.net/npm-wildcard-ssl-ispconfig/</link><pubDate>Thu, 18 Jul 2024 11:07:11 +0000</pubDate><guid>https://cristian.livadaru.net/npm-wildcard-ssl-ispconfig/</guid><description>Generating wildcard SSL certificates with Let&amp;rsquo;s Encrypt and DNS challenge is a bit tricky with ISPConfig. It could be very straight forward but there is a little bug in the ISPConfig API or the nginx-proxy-manager that calls the API. Here is how you can work around it.</description></item></channel></rss>