4 ms·

Back in early 2009, I was launching a file storage web service similar to Dropbox (without the client, but with an API with OAuth 1 support) using AWS Ec2 and S

by henvic 7y ago

Back in early 2009, I was launching a file storage web service similar to Dropbox (without the client, but with an API with OAuth 1 support) using AWS Ec2 and S3. I planned to use HTTPS, but it was expensive for me (as a college dropout), and the website is still online without it. I abandoned the project afterward. Recently, I started to migrate it from AWS to Google Cloud Platform, and one of the goals was to add HTTPS to it. However, I haven't had much time to finish the migration, and it's still not being served as HTTPS (even though it has all other sorts of protection that were the norm back then). I wonder how many other "legacy websites" have a similar issue (which I don't find justifiable for anything 'in production').

bdamm 7y ago
“Let’s encrypt” has pretty much eliminated this problem.
willis936 7y ago
Have you tried let’s encrypt a la certbot? It wasn’t a painless process when I did it but I do have autorenewing “green lock” SSL certs for free.
- henvic 7y ago
  Yes, I have. Let's Encrypt ACME challenge resolved this from now on. However, I'm using a really old machine + OS, and the nginx version I'm running is old enough not to be compatible with it. So, instead of having a hard time updating the server, I decided to migrate the site to a newer machine (even because some AWS technical limitations don't let me migrate to a new instance type). ~10 years ago I slacked in getting an HTTPS certificate as this would have meant a lot of money. ~ Today, I want to use the ACME challenge with Let's Encrypt (no need of OV for a portfolio website), but I never find the time to finish the migration (that should take more 4 to 16 hours).
  - Jenda_ 7y ago
    There are ACME clients written in Python 2 or even pure shell -- should work even on very old systems (but not older than ~2010, you need openssl with TLS1.2 support). I personally prefer them even on current systems, as I don't really like the "automagic" nature of certbot.
- m_eiman 7y ago
  I got tired of manually restarting this or that every two months or so due to failed letsencrypt updates that left my sites inaccessible, eventually I replaced the web server with a new one with more current versions. Hopefully it’ll keep things together for a few years…
  - willis936 7y ago
    I’ve been running it for 3-4 years. After a long initial setup, I’ve only had to touch it once: when some authentication protocol was deprecated. A small price to pay, all things considered.
deleted 7y ago
[deleted]
eknkc 7y ago
GCP load balancers do have lets encrypt support. They will issue certificates automatically if you want. https://cloud.google.com/load-balancing/docs/ssl-certificates#managed-certs https://cloud.google.com/load-balancing/docs/ssl-certificate...
- henvic 7y ago
  Yeah, I already tried this too although not on my own old project, but for a SaaS company I was working for (that would generate a Kubernetes cluster automatically for you with either DNS or HTTP challenge).

by henvic 7y ago

bdamm 7y ago

“Let’s encrypt” has pretty much eliminated this problem.

willis936 7y ago

Have you tried let’s encrypt a la certbot? It wasn’t a painless process when I did it but I do have autorenewing “green lock” SSL certs for free.

henvic 7y ago
Yes, I have. Let's Encrypt ACME challenge resolved this from now on. However, I'm using a really old machine + OS, and the nginx version I'm running is old enough not to be compatible with it. So, instead of having a hard time updating the server, I decided to migrate the site to a newer machine (even because some AWS technical limitations don't let me migrate to a new instance type). ~10 years ago I slacked in getting an HTTPS certificate as this would have meant a lot of money. ~ Today, I want to use the ACME challenge with Let's Encrypt (no need of OV for a portfolio website), but I never find the time to finish the migration (that should take more 4 to 16 hours).
- Jenda_ 7y ago
  There are ACME clients written in Python 2 or even pure shell -- should work even on very old systems (but not older than ~2010, you need openssl with TLS1.2 support). I personally prefer them even on current systems, as I don't really like the "automagic" nature of certbot.
m_eiman 7y ago
I got tired of manually restarting this or that every two months or so due to failed letsencrypt updates that left my sites inaccessible, eventually I replaced the web server with a new one with more current versions. Hopefully it’ll keep things together for a few years…
- willis936 7y ago
  I’ve been running it for 3-4 years. After a long initial setup, I’ve only had to touch it once: when some authentication protocol was deprecated. A small price to pay, all things considered.

deleted 7y ago

[deleted]

eknkc 7y ago

GCP load balancers do have lets encrypt support. They will issue certificates automatically if you want. https://cloud.google.com/load-balancing/docs/ssl-certificates#managed-certs https://cloud.google.com/load-balancing/docs/ssl-certificate...

henvic 7y ago
Yeah, I already tried this too although not on my own old project, but for a SaaS company I was working for (that would generate a Kubernetes cluster automatically for you with either DNS or HTTP challenge).