is down?

Well, I found the answer myself before posting, so I’ll post the answer for posterity.

Rust By Example is now at

Mentioned in

Currently, is failing to resolve, but I assume it will be changed to redirect to the new site soon.


Sigh, thanks. I was going to check this this morning; i tried to redirect, but maybe it didn’t work. I’m pretty terrible at DNS…

Don’t get frustrated, Steve! We love you nevertheless! :heart:

1 Like

An update: I haven’t seen it properly resolve yet, but the support person i talked to said it’s working on their end, so I guess it’s down to DNS propagation at this point.

Thanks a lot for this post! :heart:

I was slowly going insane because downforeveryoneorjustme said “It’s just you.”.

The DNS appears to be resolving correctly now, but Firefox and Chromium both hang on "Performing a TLS handshake to" and finally time out. This happens regardless of typing http: or https:.

It works with curl with http but not https.

1 Like

Hey guys, just throwing in another anecdote, been unable to open it still!

Please let me know if I can help!

Meanwhile, for anyone who absolutely needs it,

rustup docs

And then follow the link to Rust By Example.

This is very strange; I can see it as “up” on my phone, but “down” on my computer. Tons of people are seeing it up, some down.

I have no idea what’s going on…

I can ping it, but I can’t pull it up in Firefox.

I can, however, pull it up in lynx.

I cannot open it in firefox, but ping and curl.

With curl I get

<a href=''>Found</a>.

@steveklabnik, there’s an HTTP server doing redirects on 80, but nothing listening for HTTPS or 443. (Or at least nothing responding.) The problem with that is that is in the HSTS preload list, so Chrome & Firefox will only try connecting on HTTPS.

Although, I’m not sure why it’s working on your phone…


Okay so, I’ve decided that rather than use my host’s apparently terribly broken redirect feature, I’ve pushed a tiny index that will do the redirect, and i’ve pointed the domain back at gh-pages. Sorry again, everyone, hopefully this takes care of it.

So i learned something new today; HSTS prevents me from manually creating HTTPS exceptions for websites.

I get the following error at the moment for
Looks like the server provided a wildcard certificate for
Will this fix itself within the next hours?

1 Like

Unfortunately it won’t fix itself because GitHub Pages doesn’t support TLS with custom domains.

A workaround is to put Cloudflare in front of it:

There are other ways, like not using GH pages, but those other solutions probably cost money.

1 Like

Sigh. Thanks both of you; I forgot about this for Reasons. I’ll get on CloudFlare soon.

1 Like

Glad people are on this. :slight_smile:
Security is an annoyingly good thing.


Hey all! Sorry again about the delay here, RBE should be back up now.

1 Like

Not convinced I’m afraid. From here it looks like no DNS records for that domain.

1 Like

Hmm, very odd. It worked yesterday… I’ll investigate.

1 Like

GH pages recently introduced TLS with custom domains, by the way. . You may no longer need an external service.