Use wildcard certificate on a public server and on a local server


#1

I have some kind of staging and local develpment setup, where specific subdomains point to different servers. So I’d like to use one wildcard-certificate for *.domain.com on both servers.

Server-A
is on the Google Cloud Computing engine and serves all *.example.com requests. So https://project1.example.com work fine and the certificate is valid.

Server-B
is on my local computer (which has a dynamic public IP). So I’ve set up a DDNS, with an A-record, which points all *.office.example.com requests to my public IP.

I’ve set up my routers port forwarding from 4000 -> 192.168.1.50:443

So requests to https://project1.office.example.com:4000 are served correctly as it’s supposed to be, except that I get an invalide certificate error.
Though I use the same certificates on Server-B as I use on Server-A.

Is it even possible to use Let’s Encrypt in that way?


#2

Hi @ad-on-is

That doesn’t work.

*.example.com works with office.example.com, but not with project.office.example.com

You need a wildcard-certificate for *.office.example.com.

With that it should work.


#3

Aaah… I see… thank you :wink:
I will try get my TXT-records to work properly on my local machine, so that I can issue a new wildcard certificate.


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.