<p>I'm trying to install SonarQube onto a bare-metal kubernetes cluster.</p>
<p>All is working except for when the software inside the pod tries to make a HTTPS request.</p>
<p>I've checked using wget (pod doesn't have curl &amp; cannot use ping) &amp; using the kubernetes DNS debugging guide, however whenever I make a call such as <code>wget https://google.com</code> I get the following error:</p>
<pre><code>Connecting to google.com (192.168.1.179:443)
ssl_client: google.com: TLS connect failed
wget: error getting response: Connection reset by peer
command terminated with exit code 1
</code></pre>
<p>The IP address 192.168.1.179 is the address of another server on the host network.
The resolv.conf I have (ubuntu host) is:</p>
<pre><code>nameserver 1.1.1.1
nameserver 1.0.0.1
</code></pre>
<p>I can't figure out why this is happening or how to fix it. DNS is <em>working</em> but not resolving HTTPS.</p>
<p>I'm using Calico, kubernetes dashboard, MetalLB, ingress-nginx &amp; sonarqube</p>
<p>Edit:
After restarting the host the DNS servers successfully changed to 1.1.1.1.</p>
<p>However, now I'm presented with the following</p>
<pre><code>Connecting to google.com (142.250.204.14:443)
ssl_client: google.com: TLS connect failed
wget: error getting response: Connection reset by peer
command terminated with exit code 1
</code></pre>

Brayden
<p>This error went away when I:</p>
<ol>
<li>Disabled my firewall (ufw) and;</li>
<li>Restarted the machine for the DNS changes to take affect.</li>
</ol>
