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?
Trying do https://YOUR-DOMAIN-HERE
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
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
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.
yea it might just be missing a proper http -> https redirect, not sure how to do that in Caddy cause I only know nginx.
Caddy auto redirects to https as long as you don’t add “http://” to the domain.
That sounds more like your browser, not caddy.
No, most browsers will do what they’re told. At least with nginx, you have to set up a server to listen on port 80 and send a 301 permanently redirected message with the https URL.
Ah, maybe I wasn’t clear enough, caddy doesn’t need a configuration to redirect traffic from port 80 to port 443, it does it automatically: https://caddyserver.com/docs/automatic-https
If you want to configure an http only site you need to specifically configure it in your Caddyfile.
Here’s an example for a reverse proxy
# We don't specify the protocol so Caddy assumes HTTPS and redirects any HTTP to secure. secure.example.com { reverse_proxy :<port> } # HTTP is specified so Caddy won't redirect to port 443 nor generate a certificate. http://insecure.example.com { reverse_proxy :<port> }Yeah, I figured that’s what you meant after rereading it. Chrome at least does automatically switch to HTTPS in some cases, like where it’s seen HSTS.