I just set up a certificate for our main domain using the certbot-auto.
All seems fine with our primary domain.
We have additional iterations of our domain .net, .org… etc.
if a user uses www.domain.net or domain2.net they get stopped by Chrome/Firefox with the
"This server could not prove that it is domain2.net; its security certificate is from domain1.com. This may be caused by a misconfiguration or an attacker intercepting your connection." pop up.
What are we doing wrong?
And in the mean time is there an easy way to reverse what certbot-auto did? as right now traffic has dropped off…