• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

SSL | Gray warning triangle

bee

bee

💖 Chevereto Fan
Hello!
I have two Chevereto installations with SSL. Both certificates are the "same".

At installation 1 everything works fine. I get a Gray padlock when I open the site in FF. But at installation 2 I get an Gray warning triangle, when I open the site.
Everything is the same on both installations: VirtualHosts entries, SSL provider, ...

Any ideas?

Regards
Torsten
 
When using HTTPS, all the resources must be loaded using the https protocol to get the full https ok icon. In your website I see multiple http:// resources, like juiciads and an external storage. Unless you change all those to https:// (working https no just change the protocol) you won't get the ok icon.
 
But when I activate SSL for the external storage (S3) the images are broken (not visible).

I know, why it works on PIXr. without problems. I did the upload of the pictures before I add the external storage. So, the pictures on the startpage of PIXr. will load locally.
At SEXr. the pictures will load directly from the storage.
 
Ok - I figured it out.

You cannot use your own (sub)domain (Subdomain: s3.storage.domain.com | CNAME: s3.storage.domain.com.s3.amazonaws.com) at AWS S3 if you want to use SSL. You must access via "bucket.s3.amazonaws.com" - The bucket name does not have any dots: NO: my.cool.storage.s3.amazonaws.com - YES: my-cool-storage.s3.amazonaws.com

Thanks for your support.
 
You must log in or register to reply here.
Back
Top