Website is down

[ynotravid]

I recently adopted material-ui as our component library. It took a lot of effort to win the engineering department over but you guys bring some serious value.

This essentially was my pitch:

CSS Framework Needs

• Native to React
• Theme-able
• Community support / Documentation
• Customizable
• Has library of core components (buttons, modals, etc)
• Interoperable with current applications
• Can be used with modular components for reuse

Material-UI

• React Based
• Very theme-able
• Online documentation frequently unavailable
• 39K stars on GitHub
• Customization built in
• Interoperable with current applications

Nice to have

• Only requires React
• Can be used with non "Material-UI" applications
• Components do not require or create global css. Global css can be optionally consumed.

You can see from above the one problem is that (material-ui.com)[https://material-ui.com/] seems to be down frequently.

Personally, I have cloned the documentation locally but that will not fly with the entire engineering team for what I hope is obvious reasons.

So my question is. Is this a fluke thing that the site has been going down or is that something we need to consider before adopting material-ui?

[oliviertassinari]

Online documentation frequently unavailable

@ynotravid https://www.netlify.com/ is hosting us, we have had this feedback multiple times in the past: #12020, #11894, #11704.

Looking at the analytics data, the website has never been down. What we have, is some users struggling to load the pages. Now, I believe people have been facing two different types of issues:

• a service worker issue. For some reason, service worker brick from time to time. We are using workbox from Google. I'm considering removing the offline support for the docs if we can't get to the bottom of it. Try accessing the docs with a different browser or by clearning the cache of the browser.
• a network routing issue. Try nslookup --type=ns material-ui.com.

So?

[adeelibr]

I have had the same problem in the past.

[oliviertassinari]

What was the root cause?

[adeelibr]

@oliviertassinari I am not sure, I couldn't access it from Pakistan. Since I live here. So initially I had to use a vpn to access it. I never had the problem when there was only version 0.x, I started having this problem for a couple of release when v1 was in alpha. Then it just started working normally. (I am not sure if this is of any help)

[oliviertassinari]

@adeelibr Thank you for providing these details.. v0.x was hosted on GitHub. v1 alpha was hosted on Cloudflare.

[ynotravid]

@oliviertassinari, thanks for the response. I agree it is not a hosting issue. Of course effectively unavailable is the same as unavailable so understanding the issue and resolving would be good.

Interestingly I am able to reproduce this somewhat locally. If I run the documentation locally for more than a day then requests hang indefinitely and I have to restart the server. I haven't looked at the state of memory and service workers when it hangs but I will be glad to provide some details as soon as I get a chance.

Anyhow, thanks again.

[oliviertassinari]

@ynotravid Alright, I'm closing the issue until we can find anything actionable.

[ynotravid]

I understand thanks

[ghost]

I have the same issue and when I open chrome dev tool, there are lots of 404 errors.

Failed to load resource: the server responded with a status of 404 ()

[oliviertassinari]

@vimniky You gonna have to clear your service worker.