GeoLocation API requires HTTPS in Chrome 50

[tasomaniac]

Location is not asked anymore. This is because insecure origins are blocked now in Chrome stable.

[Splaktar]

Here's the blog post about it:
https://developers.google.com/web/updates/2016/04/geolocation-on-secure-contexts-only

It's a known issue, but there just hasn't been time to finish upgrading Firefly to move off of subdomains and onto paths for routing, see #80.

[Splaktar]

This is related to #58.

[Splaktar]

Spent an hour tonight messing with https://letsencrypt.org/getting-started/ and https://certbot.eff.org/. I got a certificate (good for only 90 days with renewal constantly required). I imported it into GCE and setup the Load Balancer and all of the other bullshit needed to configure the backend/group/etc/etc.

Something isn't working right. It's another GCE networking issue that I'm running into with basically no tools to really debug or deal with it.

Perhaps I should just set up the cert on the VM itself and skip the GCE Load Balancer BS. The https://github.com/Daplie/letsencrypt-express appears like it would be capable of doing this as well as auto-renewing the certificate, which I don't think is possible with the GCE LB configuration.

I'll have to mess around with this some more when I get time. I searched for a GCE LetsEncrypt blog post or something like that but found nothing, only GAE and LetsEncrypt posts.

[tasomaniac]

What about Cloudflare's Universal SSL. It is free.

Here is a blogpost: https://blog.cloudflare.com/introducing-universal-ssl/

Setup would take like 5 min. We have to migrate our DNS setup and it is one click.

[Splaktar]

Solved in #102 via Firebase Hosting.