Not being one to give up easily and whilst I'm aware that there are widely reported problems on this community regarding SSL and Fasthosts, I went ahead and tried to make the SSL on customer login and checkout pages option work. I requested SSL folders in Fasthost Control Panel and it added an SSL folder at https://secure9.prositehosting.co.uk/your-files. Fasthost returned a new IP address for it which is slightly different to my website IP address but the your-files folder is correctly located in htdocs alongside my acatalog and cgi-bin folders.
I'm using Fasthost's Business Premium hosting on a Linux server and Actinic Business v10. I have managed to set everything up so that there are effectively two CGI-BIN folders on my website, one for normal unsecure files and the other for SSL files (the 'your-files' folder). The Actinic software has correctly loaded the normal and SSL Perl files into the correct folders on my website and the name of the SSL folder I setup in htdocs matches the Fasthost SSL folder name. I can go into Fasthost's File Manager and see the relevant Perl files in the correct folders. So everything seems to be in the right place. I have also provisionally selected SagePay as my PSP although I don't yet have an account with them.
When I tested network settings Actinic reported a SSL certificate error, however, I went ahead and published my webstore to my website anyway and it loaded without any errors. When I go to my website in Internet Explorer and try and do a test purchase, I can successfully go into the shopping cart and checkout but it does not immediately change the web address to https:. However, my McAfee site advisor then steps in and reports a SSL certificate problem and if I ignore it and go ahaead at risk, my https page comes up in IE showing the Perl script, so it obviously gets there but there's a certificate validation problem.
The error message I receive when running the test network settings, on the testing CGI script settings test is: "There is a problem with the SSL certificate:- The host name in the certificate is invalid or does not match."
The obvious next question seems to be, where is the hostname on the certificate located and where and to what does it try and match it?
It seems to be very close to working properly but I can't find out what is causing the SSL certificate error message above. Does anyone have any suggestions as to what might be causing this?
I'm using Fasthost's Business Premium hosting on a Linux server and Actinic Business v10. I have managed to set everything up so that there are effectively two CGI-BIN folders on my website, one for normal unsecure files and the other for SSL files (the 'your-files' folder). The Actinic software has correctly loaded the normal and SSL Perl files into the correct folders on my website and the name of the SSL folder I setup in htdocs matches the Fasthost SSL folder name. I can go into Fasthost's File Manager and see the relevant Perl files in the correct folders. So everything seems to be in the right place. I have also provisionally selected SagePay as my PSP although I don't yet have an account with them.
When I tested network settings Actinic reported a SSL certificate error, however, I went ahead and published my webstore to my website anyway and it loaded without any errors. When I go to my website in Internet Explorer and try and do a test purchase, I can successfully go into the shopping cart and checkout but it does not immediately change the web address to https:. However, my McAfee site advisor then steps in and reports a SSL certificate problem and if I ignore it and go ahaead at risk, my https page comes up in IE showing the Perl script, so it obviously gets there but there's a certificate validation problem.
The error message I receive when running the test network settings, on the testing CGI script settings test is: "There is a problem with the SSL certificate:- The host name in the certificate is invalid or does not match."
The obvious next question seems to be, where is the hostname on the certificate located and where and to what does it try and match it?
It seems to be very close to working properly but I can't find out what is causing the SSL certificate error message above. Does anyone have any suggestions as to what might be causing this?
Comment