The other day I was updating the back-end API I’ve been working on for what seems like forever and got to the point that I needed to enable HTTPS before developing the API any further to allow authorization to function correctly.
One problem though, the shared hosting package we have with our main web hosting provider only offers SSL certificates through their affiliate…and it’s about $30 per domain…per year…and I have around 34 domains registered (only 10 of which I would bother setting up HTTPS, but still)…oh, and our hosting provider doesn’t currently offer a way to import free SSL certificates through Let’s Encrypt… Hooray!!!
It’s not all bad news as this tale of my 2 day trek wading through often outdated and/or mis-information (thank you Google…a rant for another day) does have a happy ending.
I also decided to create a tutorial on setting up Let’s Encrypt & how you can make it work with 1and1 with a little extra work.
LINK TO: Let’s Encrypt Option with 1and1 Hosting plus a Digital Ocean Droplet…Coming soon!
The solution is actually almost an order of magnitude better then the configuration I was going to use after comparing speed tests between various cloud hosting platforms & the shared hosting service.
Now, I want to clarify here since I can already hear the trolls saying “what the hell are you doing trying to deploy any kind of web app on a shared hosting account?!?”
To these trolls I say: “I wan’t going to use the shared hosting account like that!” I mainly use it for it’s storage of media, large digital files and some small brochure websites that see limited locally based traffic.
What was up in the air was the hosting company I was going to use for the cloud server to deploy various projects on.
On one hand, 1&1 offers cloud packages now. They offer similar packages to Digital Ocean, but cost slightly more per month. Now I was willing to look past this because I already have my shared hosting account with them & originally thought the convenience of having 1 dash board to manage the shared account & the cloud servers would be worth the slight increase in cost compared to a comparable Digital Ocean droplet. But like everything, there’s more to the story & as it turns out Digital Ocean has some bangin’ little servers in comparison.
Since this post was intended to just be an update on what I’ve worked on the past 3 days & is already longer than what I intended, I’m going to create another post that shows how I compared the 2 cloud server options I had. I will also show the tools I used along with a list of other considerations outside of just specs & cost to take into account when comparing hosting companies.
LINK TO MORE IN DEPTH CLOUD SERVER COMPARISON (coming soon)
TODO: Finish post, at info & comparison of wide range of connection speed results…
To keep this post shorter & basically provide a context, I could probably base 2 tutorials out of the experisance.
- Setting up LetsEncrypt with Virtual Hosts & sub domains on a Digital Ocean dropplet
- Running & securing MySQL DB server on remote host (need to still figure out how to encrypt connection between the 2 Cloud instances.)