MozillaZine

"This Connection is Untrusted" but I want to proceed anyway!

Discussion of general topics about Seamonkey
jeffw_00
 
Posts: 443
Joined: August 23rd, 2003, 3:23 pm

Post Posted September 9th, 2016, 8:05 am

Hi - I use Seamonkey at work, and sometimes get this message accessing INTERNAL, 100% SAFE websites. Seamonkey used to give the option of "I know the risks", but it doesn't anymore, so I have to use a different browser to get my work done :-{

What's up with this? Is there a workaround or fix?

Thanks!!!
/j

therube

User avatar
 
Posts: 16997
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted September 11th, 2016, 10:51 am

Does FF do likewise?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

jeffw_00
 
Posts: 443
Joined: August 23rd, 2003, 3:23 pm

Post Posted September 11th, 2016, 11:03 am

nope, FF does the right thing.

therube

User avatar
 
Posts: 16997
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted September 11th, 2016, 11:27 am

As a test, create a new, clean (SeaMonkey) Profile & see if that also works.


Thoughts...

A/V
SiteSecurityServiceState.txt


IF a new SeaMonkey Profile works, then in the old...

Exit SeaMonkey
Rename SiteSecurityServiceState.txt to SiteSecurityServiceState.txt.NOT
Start SeaMonkey
Test
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

jeffw_00
 
Posts: 443
Joined: August 23rd, 2003, 3:23 pm

Post Posted September 11th, 2016, 11:30 am

why don't I just try "Rename SiteSecurityServiceState.txt to SiteSecurityServiceState.txt.NOT" and see if the problem goes away?

therube

User avatar
 
Posts: 16997
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted September 11th, 2016, 12:13 pm

So, did it?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

jeffw_00
 
Posts: 443
Joined: August 23rd, 2003, 3:23 pm

Post Posted September 13th, 2016, 2:12 pm

Under "Technical Details" it says
---------------
owapp uses an invalid security certificate

The certificate is not trusted because the issuer certificate is unknown
the server might not be sending the appropriate intermediate certificates
an additional root certificate may need to be imported

(Error code: sec_error_unknown_issuer).
---------------------
and the "I know the risks" option is not present - would be nice if it was present.....

therube

User avatar
 
Posts: 16997
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted September 14th, 2016, 10:44 am

Yes, but, did you try renaming the file or with a new Profile?
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

jeffw_00
 
Posts: 443
Joined: August 23rd, 2003, 3:23 pm

Post Posted November 1st, 2016, 7:35 am

Profile didn't help, renaming Site Security didn't help. Problem is specific to owapp. Message is always the same.. So I can't really use Seamonkey at work anymore - is there any way to fix this?
===============================================================
This Connection is Untrusted

You have asked SeaMonkey to connect securely to owapp, but we can't confirm that your connection is secure.

Normally, when you try to connect securely, websites will present trusted identification to prove that you are going to the right place. However, this website's identity can't be verified.


What Should I Do?

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

This sounds bad, take me to my home page instead (only option provided).

Technical Details

owapp uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.

(Error code: sec_error_unknown_issuer)

libertyernie
 
Posts: 130
Joined: January 20th, 2015, 12:29 pm

Post Posted November 1st, 2016, 1:40 pm

I'm using a pre-release build of 2.46 and it looks like the option is back. Maybe it's just an issue with version 2.40.

Return to SeaMonkey General


Who is online

Users browsing this forum: No registered users and 2 guests