搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Insecure connection warning

  • 3 回覆
  • 3 有這個問題
  • 3 次檢視
  • 最近回覆由 philipp

more options

We recently moved (redirected) our website domain from BlueHost to Squarespace. Previously, the site had an SSL certificate. We're no longer required to have one with SS, since it's "baked in." However, now when people search for our site using Firefox they get an "insecure connection" warning.

I've had the site recrawled by Google and Bing multiple times. Chrome seems to be working fine, but Firefox continues to give the error. What do I do? This is costing us business!

We recently moved (redirected) our website domain from BlueHost to Squarespace. Previously, the site had an SSL certificate. We're no longer required to have one with SS, since it's "baked in." However, now when people search for our site using Firefox they get an "insecure connection" warning. I've had the site recrawled by Google and Bing multiple times. Chrome seems to be working fine, but Firefox continues to give the error. What do I do? This is costing us business!

所有回覆 (3)

more options

hi, i don't think it is possible to give a general answer in this case. what is the site in question and what's the exact error message/error code that you are getting in firefox?

more options

The website in question is Happy Gymnastics (www.happygymnastics.com)

The message says, "Your connection is not secure. The owner of www.happygymnastics.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website."

To verify on your end, do this:

1. Open Firefox and search for "happy gymnastics" 2. Click on the first search result 3. Verify you get the same error I do.

The problem is that when you follow the three steps I've outlined, Firefox redirects to "https" instead of "http." It's like it won't re-index the new url.

Thanks

more options

hi, i cannot reproduce the issue and land on a http-version of your site on firefox as well. it may be that if a particular firefox version has come across a secure version of your site in the past, it is then upgrading to https by default - this could be the case if your site has served a hsts-header in the past. if you want to work around that i think the only way is to provide a working https configuration of the site - certificate authorities like letsencrypt.org will also provide certs free of charge...