<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Https on NerdyNik</title><link>http://nerdynick.com/tags/https/</link><description>Recent content in Https on NerdyNik</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 Mar 2024 11:00:00 -0600</lastBuildDate><atom:link href="http://nerdynick.com/tags/https/index.xml" rel="self" type="application/rss+xml"/><item><title>Unrecognized Name issues with HomeAssistant</title><link>http://nerdynick.com/posts/2024/03/unrecognized-name-issues-with-homeassistant/</link><pubDate>Wed, 20 Mar 2024 11:00:00 -0600</pubDate><guid>http://nerdynick.com/posts/2024/03/unrecognized-name-issues-with-homeassistant/</guid><description>&lt;p&gt;Recently I ran into an issue while trying to create a new instance of HomeAssistant on a K3s install of Kubernetes.
Getting HomeAssistant up and running and connected to an MQTT server within the same cluster worked as expected.
However, the issue came up when I attempted to get it to connect to NabuCasa or make connections out to any TLS/SSL (HTTPS) addresses.
Viewing the HomeAssistant logs from the &lt;code&gt;Settings-&amp;gt;System-&amp;gt;Logs&lt;/code&gt; area, I noticed I was getting a very vague error of &lt;code&gt;tlsv1 unrecognized name&lt;/code&gt;.
Searching around the internet for the issue affecting HomeAssistant just kept turning up people having issues with DNS but no actual &amp;ldquo;What the DNS issue was&amp;rdquo;.
That was until I came across a &lt;a href="https://stackoverflow.com/questions/66630929/kubenetes-pod-curl-works-only-if-domain-name-ends-with" target="_blank" rel="noopener"&gt;Kubernetes StackOverflow Question&lt;/a&gt; where the person was getting the same issue but with a completely different application.&lt;/p&gt;</description></item></channel></rss>