NGINX

btw, DNS is pointed to the right server

I find the DNS option much more consistent and easy to use, personally. You just set a TXT record, wait for the record to propagate, confirm it with https://toolbox.googleapps.com/apps/dig/#TXT/ , and then proceed when ready.

But I'm sure someone smarter than me will me I'm doing it wrong and help you make what you're doing work.

Have you been following the Player Analytics documentation for this?

Yes, but I also need to do for BlueMaps

You can use a single cert for your domain and it will work for both. I imagine part of the problem is that you're running it on plan.domain.com instead of domain.com or *.domain.com

yeah, I'm running it on plan.domain.com

yeah, don't

I have it for panel.domain.com (AMP) and it worked just fine (but it was installed by AMP)

don't run the validation against a subdomain

run it on the domain itself

you can use the same cert for all subdomains

the main domain already have a certificate, but the main domain is parked somewhere else and pointed to another server

I just need the 4 subdomains poiting to this server

play
plan
map
panel

and play connects to your MC server?

yes

it's pointing to the Velocity Proxy

@Connecticut Warbler Requesting assist. I'm not very well versed on this and I don't want the ticket to stagnate without help.

Why not just make a wildcard cert?

I deleted all the certificates, made them over again and now they work

The config file was the issue

I used a simpler version of what I first tried and once it worked I replicated to the other certificates

Nice. Don't forget to mark as !solved