Wildcard Alias added, but no https

[sfeldkamp]

I've added a wildcard alias to the custom app install for the app that I am packaging. It works, entering an address like test2.[app.domain.com] resolves to the app. However, there is no valid security certificate for it.

I've restarted the app. Is there another step that I need to do? I didn't see anything in the docs.

Also, is it possible to setup a wildcard alias during app installation? I'd prefer not to ask the user to do this, if possible.

[sfeldkamp]

Oh, my domain is setup with a DNS provider of "Wildcard" domain but the "Let's Encrypt Prod" certificate provider. I probably need to switch that around to a programmatic provider instead.

[timconsidine]

@sfeldkamp mine works with those settings

Did you set up AAAA as well as A records ?

[joseph]

Note that your existing wildcard *.blah.com does NOT cover *.foo.blah.com . You have to add another wildcard entry ...

[sfeldkamp]

I switched to my domain registrar as the provider, connected with an API key, regenerated the certs, and then synced DNS records. Everything seems to be working as I need it to.

Can anyone answer my second question... Is there a way to setup a domain alias during app installation so the user doesn't have to configure it manually?