-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
badssl.com goes offline due to DNS failure #500
Comments
the IP 104.154.89.105 seem still up and running |
Hmm, I had no trouble accessing a few hours ago, but I can also repro now. |
Hmm, I’m not exactly sure what’s going wrong. I did some DNS changes
earlier while working on getting ACME validation working, but they
shouldn’t have affected the main site. I can investigate more and try to
roll back tomorrow morning.
…On Thu, Mar 31, 2022 at 10:28 PM Lucas Garron ***@***.***> wrote:
Hmm, I had no trouble accessing a few hours ago, but I can also repro now.
—
Reply to this email directly, view it on GitHub
<#500 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3VWEPA2BEJRUHHJ5UQKTVC2CQ5ANCNFSM5SHRRAIQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
There are DNS problems with resolving it that make the tests fail, see chromium/badssl.com#500 Require WX_TEST_WEBREQUEST_URL_SELF_SIGNED to be set to the URL to test instead of hard-coding https://self-signed.badssl.com and don't set this variable for now to let the tests pass.
Confirming site is down for me on various machines with various different HttpClient (Chrome on Mac, linux curl, .NET HttpClient) |
I tried from several locations around the world with different upstream NS and all I got was a SERVFAIL |
It's back for me |
DNS should be back (pending any propagation delays). There might be some further hiccups later today while I work on things, but I'll double check that they're left in a working state so things don't stay down for long. |
It is a short term service interruption or it is going to be offline forever ?
https://who.is/whois/badssl.com
show that some chances recently and the domain itself is expiring soon.
The text was updated successfully, but these errors were encountered: