They are both working for me on my phone. I'll be at a laptop shortly. What are you getting for the https response?
Nothing ~$ wget https://hubski.com
edit2: hubski.com is resolving to 162.243.169.82 here now too, and https works for me again. edit3: Not related, but that wget output gets more and more mangled every time I edit. Tons of extra whitespace gets inserted to the lines starting with four spaces.
edit: But it does work via my office vpn, and further there hubski.com resolves to 162.243.169.82, not 198.211.99.23. Hitting https://162.243.169.82 works here too. -2014-04-28 06:06:35-- https://hubski.com/
Resolving hubski.com (hubski.com)... 198.211.99.23
Connecting to hubski.com (hubski.com)|198.211.99.23|:443...
failed: Connection refused.
Replying to my own comment because of the whitespace thing. Digital Ocean was having network troubles on the east coast around the time https stopped working for me. I have no theory as to why, but I suspect that's related. So, probably not bugski.