Forum glitches while we enable https

Everything Else
61

Looks like there is something with Chrome and Discourse (https calling out non-local components from http). Here is a related issue.

Looking for a resolution (on your behalf).

Edit: https linked to http external content.

1 Like
62

Does this help in troubleshooting?

Or this one?

63

No, unfortunately not. The point Iā€™m at is that I have v55 chrome with no extensions installed, no history, no cache, no cookies. It will only grab some of the js files from the CDN, and the others it throws a 404. Ive seen those pages, and they are asking for solutions as well. They donā€™t provide a fix for the problem.

Im not seeing any reason why chrome is throwing a 404 unless it has either some internal blacklist, or it is checking with some google database to see if that url has been blacklisted.

64

I just tried Chrome on an Android 6 tablet for the first time since the change and, after a short delay, it came up fine.

65

Just noticed that the font style and icons have changed in Chrome.

Just checked IE and Firefox also are showing font changes.

66

@rebecca Iā€™m afraid Iā€™m out of ideas. Iā€™m not experiencing the issue myself, on any machines or OSs. Without having a problemed machine to work with Iā€™m afraid Iā€™ve exhausted basic suggestions.

  • Tom
1 Like
67

Chrome issues here as well, the page itself is loading but no content. Looks like a bunch of missing JavaScript files. Cleared cache and forced reload, nada.

This appears to be the code that was changed:

image.png1247Ɨ420 33.8 KB

In chrome itā€™s still pointing at an old asset folder using /brotli_asset/ instead of the updated /assets/

image.png1141Ɨ243 52.3 KB

2 Likes
68

Hi @thomas.alessi.jr,

Thanks for looking into this. I really appreciate it. It looks like others are having the same issue. Someone will figure it out eventually. :upside_down:

Thanks again!

69

Now Iā€™m trying with my laptop (Windows 10) and I get the White Screen of Doom, using Chrome and Firefox. That little blue ā€œEā€ saved the day (Edge).

1 Like
70

This appears to be a regional cache issue. I just VPNed to the east coast and this popped up like butter in chrome. I am on the west coast and having issues. I donā€™t know enough about the setup to say where to look, but community.glowforge.com is cached somewhere and delivering the wrong script locations from above.

1 Like
71

Yep, I can confirm this. I used a VPN to access the site via Canada and it loaded fine in Chrome. (Whereas without a VPN it doesnā€™t work in Chrome, even though it works great in Safari. I too am on the west coast.)

72

I had the same issue on my work computer in chrome, but was able to get it loading almost normally by clearing my cache and passwords. On all of my home devices, it seems to work fine with no changes necessary in any browser though, so it does seem kind of strange how it so variable.

73

well damnā€¦ I have a couple of VPNs, but all east coast. Well done. What a pain this is haha

74

Well there we have it. Seems like the CDN itself is the issue. Theyā€™re routing something incorrectly. Iā€™m east coast, myself, so no issues.

  • Tom
75

Iā€™m just South of Seattle. Chrome 54 with no issues. Didnā€™t do anything different. The only thing I saw was one slight delay when the change was first made. Iā€™m talking 1.5 seconds instead of .25 seconds to show me my notification list one time.

76

All depends where the siteā€™s CDN servers are located. Sounds like at least 1 is pointing to the wrong place.

  • Tom
77

Why would Chrome behave differently to another browser on the same machine. Do Google mess with the CDN requests?

78

Google has its own DNS name resolution code in Chrome rather than using the library provided by the operating system. This is why Safari or IE/Edge can work when Chrome doesnā€™t. (Iā€™m not sure about Firefox. I havenā€™t used it in years.)

79

No. It wouldnā€™t know the difference between a request for a CDN and anything else in the universe.

The way every browser handles security is really very unique. Up until rather recently, M$ browsers really didnā€™t worry too much about securityā€¦ allowing you to turn off many security features, or annoy you with useless ones they created themselves. Google has always been relatively security-aware. Firefox as well although I havenā€™t used it in years in any meaningful way. M$ has made some really great strides to correct that over the past year. Iā€™m really happy with the security direction theyā€™ve finally taken with their browsers. These differences affect how each browser handles content. There are probably a thousand articles you can read on the differences between all of them if you want details.

Say what now? Iā€™m not aware of any way to set Chrome DNS servers differently from the network connection itā€™s using. I donā€™t even know why one would want to. Chrome will use the DNS servers defined by the connection. If you have some contrary evidence, Iā€™d really enjoy having that knowledge.

  • Tom
80

Others have given some pretty good answers to this question. Here is an article from Wired magazine regarding their long process of converting to https. Since they have all their archives available from magazine and blog, thatā€™s a lot of stuff. It explains the rationale for going secure, but also the logistics.

This is a good and necessary thing whenever logins are required, and for many other reasons, such as ensuring that the forum site we log into is actually the authentic Glowforge site.

5 Likes