That domain isn't loading. Are you running a site there?

[ennorehling]

I received notification that my proof for wiki.eressea.de stopped working after updating my TLS certificate this weekend. The proof is still in place, but nevertheless, I tried the "Replace" option, and it gave me this error message: That domain isn't loading. Are you running a site there?

The site and proof load fine in a browser from several locations. Something wrong on your end, maybe?

[RoryH]

Seeing the same problem here. Modified TLS configuration on my site recently, and now getting the same symptoms as above.

[etu]

I recently (few months ago) changed email for my TLS certificate using Let's Encrypt, the crypto, webserver and webpage is all the same. Just changed email.

And today Keybase told me that the proof is gone, but I can look at it here: https://elis.nu/keybase.txt

And when doing a replace I get the same message as above: That domain isn't loading. Are you running a site there?

I think my certificate wasn't changed until recently since the lifetime of the certificates lasts "a while".

[RoryH]

For the record, my problem turned out to be badly configured SSL, when I corrected everything keybase was happy again.

[ennorehling]

@RoryH : badly configured how? My site is still "not loading", and I do not see what's wrong with the SSL configuration.

[x2on]

Here the same problem, site works fine with Let's encrypt cert in browser, but on Keybase there is "That domain isn't loading. Are you running a site there?" error...

[maxtaco]

Hey guys. We got hit by a node v8 bug. We will get a fix out hopefully today. Thanks for the report Which urls btw?

…

On Fri, Jan 5, 2018 at 12:10 PM Felix Schulze ***@***.***> wrote: Here the same problem, site works fine with Let's encrypt cert in browser, but on Keybase there is "That domain isn't loading. Are you running a site there?" error... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9662 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA05_4oNO2T-VTXRwxlODWihap3sH06xks5tHldugaJpZM4Qnteh> .

[x2on]

My proof is https://felixschulze.de/keybase.txt

[maxtaco]

Might be fixed, try it now?

[x2on]

Looks like it works now. My domain is back in the keybase portal without any action from my side.

[maxtaco]

Great, glad it's fixed.This was the bug: nodejs/node#16196

[ennorehling]

Still not fixed for me. Site is https://wiki.eressea.de/

[maxtaco]

Doesn’t load in my browser either.

…

On Tue, Jan 9, 2018 at 8:47 AM Enno Rehling ***@***.***> wrote: Still not fixed for me. Site is https://wiki.eressea.de/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#9662 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA05_-gaXt15pG5jIhSDWnEc2DVRGQaxks5tI23qgaJpZM4Qnteh> .

[etu]

@ennorehling I suggest taking a look at your certificate chain here: https://www.ssllabs.com/ssltest/analyze.html?d=wiki.eressea.de&hideResults=on&latest, it seems to be incomplete.

A simple way I use to test if the chain is complete or not is to try it with curl. Desktop browsers tend to compensate for that in some way. But curl, mobile browsers and many others doesn't.

[ennorehling]

You're right, the certificate chain was messed up. That fixed it!