From 90926d3bdf4c164b7ca965e3962cbd89f0abf0b3 Mon Sep 17 00:00:00 2001 From: Brian Cunnie Date: Wed, 15 Sep 2021 10:57:13 -0700 Subject: [PATCH] VMware employees can't get the wildcard The wildcard is expiring, and I'm loath to spend something renewing something I don't use, so I'll let it lapse. (I use Let's Encrypt). --- k8s/document_root/index.html | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/k8s/document_root/index.html b/k8s/document_root/index.html index 6ef2441..c9bacee 100644 --- a/k8s/document_root/index.html +++ b/k8s/document_root/index.html @@ -1,7 +1,7 @@ - + @@ -187,11 +187,8 @@ dig @localhost 127-0-0-1.sslip.io +short # returns "127.0.0.1" *.xip.example.com, you could browse to https://www-52-0-56-137.xip.example.com/ but not https://www.52.0.56.137.xip.example.com/.

-

Unless you're a VMware employee, I can't release the private key for the "*.sslip.io" wildcard certificate - (VMware employees can download the *.sslip.io TLS private key here); however, acquiring wildcard - certificates for "sslip.io" subdomains, e.g. "*.52-0-56-137.sslip.io", is possible but more complicated. For - those interested, the procedure is described if you're interested in acquiring a wildcard certificate for your sslip.io domain, e.g. + "*.52-0-56-137.sslip.io", is possible but complicated. For those interested, the procedure is described here.

Determining Your External IP Address via DNS Lookup

You can use sslip.io's DNS servers (ns-aws.nono.io, ns-azure.nono.io,