Yeah, I checked multiple validators as well. Obviously the issue is not universal. YMMV.
Good News! Symantec has fixed it and it is starting to propagate across the internet.
1 Like
Unfortunately (in general), the forums are NOT SSL (https://).
I would like to see that changed since people are using the same username (and probably the same password) as your account on the secure https://glowforge.com website account.
Normally, most companies have any site that has a username and password will use https: I think it got overlooked on community.glowforge.com
1 Like
Agreed. I suspect it’s rather far down on their todo list atm though 
Thanks all! We got it sorted out. I would tell you what the problem was except I have no idea and I am out of the office today. 
7 Likes
Hope everything emailed to you was either helpful or not distracting.
I wonder how this would affect a working Glowforge itself.
1 Like
I wouldn’t think that data sent to the Glowforge would need to be encrypted, but obviously it would depend on how the Glowforge authenticates to the cloud.
!!!
Come on guys…
Ok, in my defense I’m on my 3rd glass of scotch. I’ll read it again tomorrow when I’m a bit more sober. 
1 Like
Even if the traffic is encrypted it could be a self-signed certificate not relying on a certificate authority. I would actually assume the traffic to be encrypted as its best practice and requires little effort. Each glowforge would then be configurered with a list of CA’s. I guess that the Glowforge is simply the client/consumer of some web API.
Do anybody know what chip it’s running? Wonder if it’s some tiny Linux distribution or something more barebone.
1 Like
All data sent to and from the Glowforge is encrypted end to end via SSL.
4 Likes