I usually use HTTPS when browsing bungie.net (HTTP now), and a few minutes ago I received this message when trying to connect:
[quote]www.bungie.net uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
The certificate expired on 12-01-08 06:59 PM. The current time is 12-09-29 04:01 AM.
(Error code: sec_error_unknown_issuer)[/quote]
Did their server just start using an old cert? What is happening..
-
YOu can't fix all of our problems.
-
[quote][b]Posted by:[/b] I ColdEmbrace I [quote][b]Posted by:[/b] hdubya Fixed[/quote] It's so awesome having awesome people here to make sure bungie.net is functioning as awesome as it can. Awesome.[/quote] [url=http://www.youtube.com/watch?v=Ue5xgDBAAhI]Because we're not shooting for realism, we're shooting, for awesome.[/url]
-
We're always watching http://www.youtube.com/watch?v=PDZcqBgCS74
-
Daza has failed me for the first and last time.
-
[quote][b]Posted by:[/b] ctjl96 hurry everyone quote the employee and tell him how awesome it is to have the website functioning normally[/quote] as you wish. [quote][b]Posted by:[/b] hdubya Fixed[/quote] it is awesome to have the website functioning normally.
-
[quote][b]Posted by:[/b] hdubya Fixed[/quote] Proof that Bungie is always watching, even during the weekend.
-
[quote][b]Posted by:[/b] hdubya Fixed[/quote] It's so awesome having awesome people here to make sure bungie.net is functioning as awesome as it can. Awesome.
-
hurry everyone quote the employee and tell him how awesome it is to have the website functioning normally
-
Fixed
-
[quote][b]Posted by:[/b] Thrasher Fan [quote][b]Posted by:[/b] Mythical Wolf I'm getting it as well. Must be on their end.[/quote] Same issue here.[/quote]
-
*beats daz* The issue is being caused by an expired security certificate. The certificate currently being used to run Bungie.net in HTTPS expired in January. The "issue" is entirely on the server side of Bungie.net. This could have happened in a number of ways, but one very likely scenario is the primary HTTPS server has gone offline for maintenance and it is now running on a different server that hasn't had its security certificate updated. Solution: Stop running Bungie in HTTPS. Or add an exception to the certificate. [Edited on 09.29.2012 2:37 AM PDT]
-
[quote][b]Posted by:[/b] Mythical Wolf I'm getting it as well. Must be on their end.[/quote] Same issue here.
-
I'm getting it as well. Must be on their end. (Inb4 Daz). [Edited on 09.29.2012 1:43 AM PDT]
-
Well, you're not the only one, as I'm receiving the name message. It must be something on Bungie's end.
-
I've never gotten that, that's weird. *waits for Dazza*
-
[quote][b]Posted by:[/b] funkbrotha10 you herped[/quote]That is a very constructive reply. If you feel I've made an obvious oversight, please point it out.
-
you herped