Today I decided to get an inexpensive custom domain from Namecheap and try self-hosting Lemmy. A few bucks later I was thinking, “Hey, this is going to be cake.”
I’d read some of the warnings about Oracle Cloud free tier, but figured I’d still give it a shot for hosting. I found a simple how-to for quickly getting an Ubuntu instance spun up with Docker and Portainer. A few minutes later I’m thinking, “This is so easy!”
Then I try to access Portainer using HTTPS and see my first “Your connection is not private,” warning. “No worries,” I think. “Advanced>Proceed. I’m in.”
So I run Lemmy Easy Deploy. “The lights are green, the trap is clean! Boom. Here we go!”
Nothing.
Ports seem to be open on Oracle, but no Lemmy at either 80 or 443.
“Maybe Lemmy is more particular about SSL certificates and such?” I think, for the first time getting worried.
"Err, I think that if I change my nameserver to Cloudflare I can destroy my Lemmy containers, re-run Lemmy Easy Deploy with a Cloudflare API token, and maybe fix it?
Four hours later, after repeatedly starting over, clearing my browser cache every 5 minutes, switching back and forth between nameservers, even deleting the whole Oracle Cloud VM and starting from scratch, I realize that an HTTP connection to port 443 is returning “Client sent an HTTP request to an HTTPS server.”
“Were you there before, message?” I wonder.
Lemmy friends, can you help me? Or am I better off just deleting the VM and giving up the whole idea?
I just went to copy the error message I saw before and… it’s working.
Maybe because I switched back to Namecheap’s nameserver? Or maybe because I cleared my cache again? Or maybe because I game it some more propagation time?
That was my exact experience too when I first started out.
Things that should have worked didn’t, and things that shouldn’t have worked did
And then eventually the things that should have worked started working, with no clear indication of why they weren’t working, or why they suddenly started working.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Now I feel dumb.
That didn’t work earlier.
I just went to copy the error message I saw before and… it’s working.
Maybe because I switched back to Namecheap’s nameserver? Or maybe because I cleared my cache again? Or maybe because I game it some more propagation time?
Or maybe magic?
Each potential reason seems equally likely to me.
Thanks
DNS can take 4 to 24 hours to replicate out. Next time, you can adjust you hosts file temporarily to test while it does it’s thing.
Welcome to the world of web administration
That was my exact experience too when I first started out.
Things that should have worked didn’t, and things that shouldn’t have worked did
And then eventually the things that should have worked started working, with no clear indication of why they weren’t working, or why they suddenly started working.
All I can say is that it gets easier with time