Thanks genjix, that's exactly the way I have it set up. I figured that my problem lies with the code of my website - it contacts another webpage, which is not SSL-enabled. That more than likely causes the problem, I think? Chrome says the connection to my website is encrypted, but it contains elements, which are not. I will have to get rid of those links - unless I am wrong?
Right. If you pull inline resources (images, JavaScript, CSS, etc.) which are from non-secured websites, the browser will throw a warning. So it's best to serve all such resources from your secure site, or from someone else's secure site.