We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

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

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

Swalife websight doesn't operate correctly on one of our computers and works fine on the other

  • 1 cavab
  • 2 have this problem
  • 3 views
  • Last reply by cor-el

larryskwikcolor
larryskwikcolor
more options

We have two Dell laptops. For explanation of this problem, I will refer to them as #1 and #2. I have used Firefox on #1 for 3 years now. Our other computer, #2 has been using IE, but because of IE issues, we decided to switch it to FF also. It is necessary for us to use swalife.com website for work. When I log in to swa life on #1 it works fine as it always has. We downloaded FF 18.0 on #2 and the swalife site only has partial functionality. We can log in to the site on #2 and it recognizes the names and passwords, but will not open the default opening page. The default page has 4 tabs, news, need to know, swa pics, and profiles. The only tab out of the three that works correctly is the need to know tab. The other three have a window that opens that displays the following message:

This Connection is Untrusted 

        You have asked Firefox to connect

securely to blog.swalife.com, but we can't confirm that your connection is secure. 

         Normally, when you try to connect securely,

sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. 

       What Should I Do?
         If you usually connect to

this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. 

  blog.swalife.com uses an invalid security certificate.

The certificate is not trusted because no issuer chain was provided. (Error code: sec_error_unknown_issuer)

Yesterday I contacted Norton security. They took control of #2 and said that it wasn't a security problem and that they couldn't fix it. He suggested using Chrome, since swalife.com operated fine with chrome on #2. That is not the solution I wanted. We also contacted Tech Support at swalife and they had no idea what the problem could be. My question to you is...if swalife.com operates correctly on#1 with FF18.0, why can't #2 operate on FF18.0? Both computers are in the same room, using the same router, and are on the same Insight cable connection. I have checked and compared security settings on both computers and both appear to be identical. Please note, that in the Untrusted window it says that "You have asked FF to connect securely to blog.swalife.com but we can't confirm that your connection is secure." We are not asking to connect to blog.swalife. We never use it. The site sends us to this window directly from the log on page.

Please Help Larry Krauss larryskwikcolor@yahoo.com 614-448-8035

We have two Dell laptops. For explanation of this problem, I will refer to them as #1 and #2. I have used Firefox on #1 for 3 years now. Our other computer, #2 has been using IE, but because of IE issues, we decided to switch it to FF also. It is necessary for us to use swalife.com website for work. When I log in to swa life on #1 it works fine as it always has. We downloaded FF 18.0 on #2 and the swalife site only has partial functionality. We can log in to the site on #2 and it recognizes the names and passwords, but will not open the default opening page. The default page has 4 tabs, news, need to know, swa pics, and profiles. The only tab out of the three that works correctly is the need to know tab. The other three have a window that opens that displays the following message: This Connection is Untrusted You have asked Firefox to connect securely to blog.swalife.com, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. blog.swalife.com uses an invalid security certificate. The certificate is not trusted because no issuer chain was provided. (Error code: sec_error_unknown_issuer) Yesterday I contacted Norton security. They took control of #2 and said that it wasn't a security problem and that they couldn't fix it. He suggested using Chrome, since swalife.com operated fine with chrome on #2. That is not the solution I wanted. We also contacted Tech Support at swalife and they had no idea what the problem could be. My question to you is...if swalife.com operates correctly on#1 with FF18.0, why can't #2 operate on FF18.0? Both computers are in the same room, using the same router, and are on the same Insight cable connection. I have checked and compared security settings on both computers and both appear to be identical. Please note, that in the Untrusted window it says that "You have asked FF to connect securely to blog.swalife.com but we can't confirm that your connection is secure." We are not asking to connect to blog.swalife. We never use it. The site sends us to this window directly from the log on page. Please Help Larry Krauss larryskwikcolor@yahoo.com 614-448-8035

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The blog.swalife.com server doesn't send a required intermediate certificate.

You can inspect the certificate chain via a site like this:

You can Copy and Paste the certificate text of the intermediate certificate (COMODO High-Assurance Secure Server CA) to a .cer text file and import the certificate in the Certificate Manager or use Firefox > New Tab > Open File.

DO NOT set any trust bits, those are only required for root certificates and should never be set for intermediate certificates.