Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

in-secure site warning inaccurate

  • 1 reply
  • 1 has this problem
  • 4 views
  • Paskiausią atsakymą parašė Wesley Branton

more options

When clients log out from platzermedia.com they get an insecure site warning, even though the URL says https://platzermedia.com if I add a forward slash at the end of the URL or www. in front of the domain there's no insecure site warning. Seems odd that a site would become insecure if a forward slash "/" is removed?!

In other words…

https://platzermedia.com is NOT secure according to Firefox???!!! https://platzermedia.com/ is secure https://www.platzermedia.com is secure

When clients log out from platzermedia.com they get an insecure site warning, even though the URL says https://platzermedia.com if I add a forward slash at the end of the URL or www. in front of the domain there's no insecure site warning. Seems odd that a site would become insecure if a forward slash "/" is removed?! In other words… https://platzermedia.com is NOT secure according to Firefox???!!! https://platzermedia.com/ is secure https://www.platzermedia.com is secure

All Replies (1)

more options

Your certificate is not correct. It's been issued to www.www.platzermedia.com and www.platzermedia.com. Therefore, when you try to connect without the www, it's not covered by the certificate.

The most likely cause is that when you ordered your SSL certificate, you added the WWW part to the domain that you registered. Most SSL authorities want just the domain because they automatically include the www part.

In this situation, you will need to contact the company that issued the SSL certificate so that they can correct the certificate and issue a new one.

Hope this helps.

NOTE: In my response, I'm assuming that you are the web administrator of this website. If not, contact the website administrator. There's no workaround for this issue because it's not a Firefox problem. It's an issue on the website's end.

Modified by Wesley Branton