Closed Bug 70537 Opened 25 years ago Closed 25 years ago

Cannot access the secure site - looks like the server doesn't support TLS

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 64561

People

(Reporter: cheng, Assigned: asa)

References

()

Details

When I typed the given URL, I only got Error loading URL https://webbanking.tdaccess.com/: 80004005 I am using 2001022808.
worksforme, with the same Linux build. Reporter, do you have a working PSM? What do you see when you go to Tasks -> Privacy and Security -> Personal Security Manager
I tried to access https://webbanking.tdaccess.com/ using mozilla 0.8 on Debian/unstable and nothing came up. I then disabled TLS as per bug 64561, and was able to access the first page. (I stopped there, having gotten further than before.) So could you try to disable TLS and if that fixes your problem, attach a comment saying so, so the bug can be marked a duplicate. I also changed the summary from "Cannot access the site" to "Cannot access the secure site - looks like the server doesn't support TLS"
Summary: Cannot access the site → Cannot access the secure site - looks like the server doesn't support TLS
Okay, turning TLS off at least got me to the login screen (but I cannot log in, and that's probably some other bug...). In any case, shouldn't there be some informative error message saying that the server doesn't support TLS and suggest the user to turn it off? Better yet, is there any reason not to have it automatically adjust itself?
Actually, Mozilla _does_ automatically adjust itself as far as I can tell. However, it seems that some servers have a broken SSL implementation that interpret this adjustment as a man-in-the-middle attack and drop the connection. See bug 59321.
*** This bug has been marked as a duplicate of 64561 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
ver
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.