- May 13, 2018 at 5:07 pm #96207
edd_user_6228753ParticipantMay 14, 2018 at 8:15 am #96285
usually when this happens it’s because of either an issue with the certificate or server configuration. In this case the certificate seems to be valid for both viatim.nl and *.viatim.nl. When doing a certificate test on the www domain it returns an ‘Failed to communicate with the secure server’ error. It looks like the certificate doesn’t cover the www domain. You can try to add the http://www.viatim.nl domain to the certificate as well to see if that solves the issue. Otherwise you might have to make changes to the server configuration so the www domain also return the certificate.