Your connection to this site is not fully secure - Issue

Hello,
For some reason, while I’m using chrome, my site is not fully secure.
Everything work fine and I do not understand why on chrome is not fully secure but on
Explorer it is.

How can I fix it ?
Thanks for your help.

Anybody ?

Please help me, I can’t fix it.

noki, we can’t help you if we don’t know which site it is! you need to tell us which domain and also which netlify site name. thanks.

Hey,
my site is - https://www.we-help.co.il
netlify site - (https://we-help.netlify.app/

  • It is not working on Chrome.

Thank you!

hi there did you setup an SSL certificate already for this domain?

Yes, everything seems to work just fine but it is stiil dont work with Chrome

Hiya!

Not a ton of context to go off here but based on a very brief look, my browser console tells me that your page isn’t considered “fully secure” because your form’s action posts to FormSpree over HTTP instead of HTTPS, which is a breach in security to some degree because when a page is loaded over HTTPS, everything about that page should operate on HTTPS

<form action="http://formspree.io/israelwehelp@gmail.com" method="POST">
                  ^

Just change your action url to post to https://formspree.io/israelwehelp@gmail.com instead of the http:// version and you should be fine. Formspree redirects http POST’s to https anyway so there’s no reason not to do this.

Cheers! :grin:


Jon

You might be seeing a local browser caching issue. It loads fine in Chrome for me (macOS) with HTTPS.

my site is not fully secure.
Everything work fine and I do not understand why on chrome is not fully secure but on
Explorer it is.

I think Noki’s issue is that the site isn’t “fully” secure in the sense of getting the browser lock-icon, not that the site itself doesn’t load over HTTPS :slightly_smiling_face:

1 Like

super helpful, @jonsully! thanks.

1 Like

He should have received a warning after build about mixed content, then, right?

So, first of all, you’re serving all linked resources over HTTPS so that’s great! Besides this, have you tried the basics such as clearing your cache?

If this is still a problem, can you share a picture of the error that you’re seeing?