This should be completely transparent to most users except if you've stored a security exception in your browser or email program.
If you access your web site as, say, https://www.example.com, your browser will warn you that the web server said it was not example.com, it was elirion.net. You can tell it you expected that mismatch and store the exception. Similarly, if you get or send email via mail.example.com and use SSL or TLS, your mail program will tell you that the mail server supplied an SSL certificate belonging to elirion.net, not mail.example.com. Again you can say you expected that, and the mail program will not bother you again in future.
Many browsers and mal programs store the expiration date of the certificate, so when we install a new certificate with a new expiration date the program will ask you again if you expected the mismatch.
If you're just accessing https://store.elirion.net or getting/sending mail via mail.elirion.net, your browser or email program should not tell you the certificate changed.
Friday, August 7, 2015
Powered by WHMCompleteSolution