Ignore the require SSL setting. If you have a certificate in place then you should be able to use HTTP and HTTPS interchangeably.
If nothing loads when you use HTTPS, but the same URL works with HTTP, then the secure session isn't being established. That points to a bad certificate.
You could use the selfSSL tool within the IIS Resource Kit to create a self generated certificate for testing purposes, but I wouldn't recommend its use in production. Telling users to ignore certificate warnings is a bad idea.
Simon.