Website has no CSS (the CSS file has 503 error)

[ADTC]

The entire atom.io website loads in ugly Times New Roman black text on white background with no CSS styling whatsoever. When I view source and visit the CSS link, I get a 503 error:

https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css Error 503 error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error Guru Mediation: Details: cache-hkg6823-HKG 1478325671 841319046 Varnish cache server

Is this permanent or is it just me?

[sverweij]

Same here. All through yesterday & the evening before (GMT+1) on packages, themes and documentation, but now the front page as well. Occurs in all browsers I've used (on OSX: safari 10.0.1, ff 49.0.2, chrome 54 and on android: chrome dev mobile). The console & network panel show errors for everything from fastly.net - but also CSP violations:

GET https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css 
(index):10 GET https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-3db62b578ebfc39ee871abc91b175302.js 
(index):1 Refused to load the script 'https://static.ads-twitter.com/oct.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://ssl.google-analytics.com https://www.google-analytics.com https://platform.twitter.com https://github-atom-io-herokuapp-com.global.ssl.fastly.net".

(index):265 Uncaught ReferenceError: twttr is not defined(…)(anonymous function) @ (index):265
(index):6 Refused to load the script 'https://js-agent.newrelic.com/nr-998.min.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://ssl.google-analytics.com https://www.google-analytics.com https://platform.twitter.com https://github-atom-io-herokuapp-com.global.ssl.fastly.net".
r @ (index):6

[simurai]

Might be related to http vs https or subdomain?

• http://flight-manual.atom.io/
• http://blog.atom.io/
• http://electron.atom.io/

still work fine.

[csvan]

Confirming

[lee-dohm]

Our CDN has updated some DNS entries in the last 24 hours. At least one person has had luck with rebooting their home router, which I suspect caused their router to update with the latest DNS entries.

We're still investigating.

[lee-dohm]

Another person was able to fix the issue by switching to using Google Public DNS. So it would appear that this is related to the DNS changes and should resolve itself completely soon.

I'll leave this open for now to track things.

[lee-dohm]

Is anyone still experiencing this problem?

[A-Manning]

Yes, I still have this issue.

[lee-dohm]

@A-Manning Have you tried flushing your DNS cache or switching to using Google Public DNS?

[A-Manning]

yes, no effect

[csvan]

Still an issue. I'm connecting via 4G so it has nothing to do with home router settings.

[sverweij]

• Adding the Google's Public DNS resolves the problem for now.
• What did not help was resetting my router - upstream DNS (my provider's, my provider's provider, ...) probably don't have the correct entries yet either - if that is indeed the problem, because ...
• ... Google's DNS and my provider's both resolve to the same IP address (151.101.36.249:443). However, according to my browser's network panel
  • Google is served by cache-lcy1131-LCY, but
  • my provider is served by cache-ams4142-AMS - which reports a cache miss.
• That cache server in Amsterdam seems to have a problem. This might explain why the people having an issue in this thread seem to be in Europe exclusively:

Error 503 error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error

error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Guru Mediation:

Details: cache-ams4124-AMS 1478423859 1915972972

Varnish cache server

URLs hit: https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-3db62b578ebfc39ee871abc91b175302.js

[bastilian]

@sverweij nice analysis! and interesting. Are you in Amsterdam too, because I am. So it may well be a regional problem either with our ISPs or Fastly.

[sverweij]

@bastilian a.t.m. I'm in the neighbourhood of Amsterdam idd.

[yustnip]

The same. Moscow.

[A-Manning]

Same issue, I'm in Montreal

On 6 Nov 2016, at 17:12, Nikita Yustovskiy notifications@github.com wrote:

The same. Moscow.

― You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[diracdeltafunk]

Copying my info from https://github.com/atom/atom/issues/13153:

I am experiencing this issue on Chrome Version 54.0.2840.87 m (64-bit) and Edge 38.14393.0.0. I'm using Windows 10 Pro N, Version 10.0.14393 Build 14393. The response I get in chrome for the CSS file is:

Request URL:https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css
Request Method:GET
Status Code:503 error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Remote Address:151.101.24.249:443

HTTP/1.1 503 error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Server: Varnish
Retry-After: 0
Content-Type: text/html; charset=utf-8
Content-Length: 625
Accept-Ranges: bytes
Date: Mon, 07 Nov 2016 06:36:59 GMT
Via: 1.1 varnish
Connection: keep-alive
X-Served-By: cache-lax8644-LAX
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1478500619.456833,VS0,VE144

GET /assets/application-ba07c5c2889a34307a4b7d49410451d9.css HTTP/1.1
Host: github-atom-io-herokuapp-com.global.ssl.fastly.net
Connection: keep-alive
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36
Accept: text/css,*/*;q=0.1
Referer: https://atom.io/
Accept-Encoding: gzip, deflate, sdch, br
Accept-Language: en-US,en;q=0.8,fr;q=0.6,zh-CN;q=0.4,zh;q=0.2

[olamedia]

Note that i had cache-fra1231-FRA broken, not amsterdam

[frdmn]

Details: cache-fra1230-FRA 1478513820 1315182496

Broken for me as well (from Würzburg, Germany)

[md-shah]

Still same broken page from India.

[eHxBes]

Still broken over here, Montreal !

[denqxotl]

When I connected to TX VPN everything is ok with styles, but when I try to visit it without VPN I have no styles (Lviv, Ukraine)

[coliff]

https://atom.io/ still broken here for me in Osaka, Japan. I'm using Google's public DNS (8.8.8.8 and 8.8.4.4)

[lee-dohm]

Thanks for the updates everyone. We're still looking into this.

[CyberShadow]

Broken for me from Chișinău, Moldova. However, I don't get a TLS error - I get an infinite redirect loop ("The page isn’t redirecting properly").

Example request:

~ » curl -I https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css
HTTP/1.1 301 Moved Permanently
Server: Cowboy
Status: 301 Moved Permanently
Content-Type: text/html
Location: https://github-atom-io-herokuapp-com.global.ssl.fastly.net/assets/application-ba07c5c2889a34307a4b7d49410451d9.css
Via: 1.1 vegur
Access-Control-Allow-Origin: *
Content-Length: 0
Accept-Ranges: bytes
Date: Tue, 08 Nov 2016 00:51:41 GMT
Via: 1.1 varnish
Age: 3435
Connection: keep-alive
X-Served-By: cache-ams4420-AMS
X-Cache: HIT
X-Cache-Hits: 43
X-Timer: S1478566301.817314,VS0,VE0

[iolsen]

I think we may have fixed this, but none of us on the GitHub team were affected so I can't confirm. Are people now seeing atom.io load correctly?

[CyberShadow]

Fixed for me!

[simurai]

👍 Fixed for me too.. ( 🇯🇵 Japan)

[md-shah]

Fixed 😃 (from India)

[gbrayut]

Work here now too.

[A-Manning]

Resolved.

[csvan]

Working in Sweden.

[yustnip]

Correct, Moscow.

[ADTC]

It appears to be working for me now 😄 Tested from Asia.

PS: Shall I close this?

[lee-dohm]

Thanks for the confirmations everyone! I'm going to close this since it appears to be working properly now :grinning: