How do I allow https through modsecurity?

Hi all,

I installed ISPConfig 3 and then got a StartSSL free certificate for it.
It works fine on port 8080 in https mode and the SSL certificate is recognized.
I access it using:

Before I installed the SSL certificate I had a self-signed certificate which allowed ISP Config to work as above (there used to be a red line diagonally across the word "https" before because the certificate was not related to that domain) but also my domain to load as:

But since I installed the StartSSL certificate, I can only access the ISPConfig but not my normal site anymore.
I believe that sine the self-signed certificate was made out to my FQDN it did not cause any conflicts but now that the new Startssl certificate is made out to it is causing all this.
Now when I access my domain I get this error: Forbidden. You don't have permission to access / on this server.

The culprit behind it all is modsecurity which has the SecRuleEngine On. If I turn that Off everything works fine, but with it on I don't really know how to make the right modifications in the apache.conf, my virtualhost's conf file or any other file that I do not know about.

What should I do? I need the two things to work, with mod-security turned on, as before: -> ISPConfig (working, the https does not have any red line striking through anymore) -> my website (at present not working)

I temporarily tried turning the SecRuleEngine to Off and everything started working again, but that was a scenario which I would not like to keep. I need mod_security to be on and the sites to work at the same time.

thanks in advance
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris GralikeSpecialistCommented:
Hi badwolff,

Could you please post the Apache error and access logs. Do this by:
0. Stop httpd.
1. moving the old logs,
2. configure the logging at INFO level,
3. start httpd,
4. make a request on the erroneous URL.
5. Post the logging results contained in the access and errorlog here.

rgrds, Chris

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
badwolfffAuthor Commented:
Thanks Chris, all sorted. All it needed was a reboot of the system for the new rules I had written to activate. Sorry for the trouble. If I get stuck again I will write back.

And since you are the only one who took the trouble to reply, the points are yours.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.