Hey there,
I’ve been trying to use BoringProxy to get past my ISP and their private IPs, so I have an exposed Google Compute Engine VM with a public IP that I’ve mapped .nullkid.com to. I did this through GoDaddy’s DNS manager and I selected an A type DNS record which was mapped to that address. However, when I try to use https://.nullkid.com as my Admin Domain, this happens. (Keep in mind I have no idea what I’m doing)
./boringproxy-linux-x86_64 server -admin-domain https://*.nullkid.com 2024/09/17 22:54:26 Starting up 2024/09/17 22:54:26 https://*.nullkid.com: obtaining certificate: [https://*.nullkid.com] Obtain: subject does not qualify for a public certificate: https://*.nullkid.com
What does this mean and how do I remedy it?
Pretty sure the problem here is that you’re trying to get a wildcard certificate *.nullkid.com. boringproxy doesn’t support wildcards for the admin domain. You’ll need to use a specific one like -admin-domain boringproxy.nullkid.com, or just nullkid.com. Note that you shouldn’t include the https://. You can still use tunnels for any subdomain and it will get certs for them on demand.
Thanks, that got it up and running! However, when I try to connect the client to my server, I’m getting this error message (keep in mind I have NOT setup IPv6 and don’t know how to using a Google Cloud Compute Engine server)
2024/09/18 19:46:22 Starting up
WARNING: Failed to access 2600:6c5e:b7f:56b4:b627:be19:bbdb:c714:443 from the internet
2024/09/18 19:46:27 kasm.nullkid.com: obtaining certificate: [kasm.nullkid.com] Obtain: [kasm.nullkid.com] solving challenges: kasm.nullkid.com: no solvers available for remaining challenges (configured=[http-01 tls-alpn-01] offered=[tls-alpn-01 dns-01 http-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/1947014526/306327069766) (ca=https://acme-v02.api.letsencrypt.org/directory)
I’m assuming you have *.nullkid.com pointed at your boringproxy server machine?
Can you try crreating tunnels with different values of “TLS Termination”