this post was submitted on 06 Jul 2023
47 points (92.7% liked)

Selfhosted

40183 readers
646 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] rikudou@lemmings.world 9 points 1 year ago (4 children)

What tutorial have you followed? I followed the official one with docker and it worked flawlessly.

[–] Gamera8ID@lemm.ee 5 points 1 year ago (1 children)

Lemmy Easy Deploy. I didn't know where to find any tutorials for using an Oracle Cloud VM. Did the official have that?

[–] rikudou@lemmings.world 2 points 1 year ago (1 children)

I assume the VM is some kind of Linux server? Ot is there something specific to Oracle Cloud?

[–] Gamera8ID@lemm.ee 1 points 1 year ago* (last edited 1 year ago) (1 children)

Yes, the VM is Ubuntu 22.04.

Edit: Replied out of context. Fixed.

[–] rikudou@lemmings.world 3 points 1 year ago* (last edited 1 year ago)

Then it should work with this: https://join-lemmy.org/docs/administration/install_docker.html

Here are the commands, basically:

Installing docker

From this doc: https://docs.docker.com/engine/install/ubuntu/

  • for pkg in docker.io docker-doc docker-compose podman-docker containerd runc; do sudo apt-get remove $pkg; done
  • apt-get update
  • apt-get install ca-certificates curl gnupg
  • install -m 0755 -d /etc/apt/keyrings
  • curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor -o /etc/apt/keyrings/docker.gpg
  • chmod a+r /etc/apt/keyrings/docker.gpg
  • echo "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
  • apt-get update
  • apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-compose

This series of commands installed an official docker repository in your system so docker itself is always up-to-date, Ubuntu gets updates like this kinda slowly.

Installing Lemmy

From this doc: https://join-lemmy.org/docs/administration/install_docker.html

  • mkdir /opt/lemmy
  • cd /opt/lemmy
  • wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/docker-compose.yml
  • wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/examples/config.hjson -O lemmy.hjson
  • wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx_internal.conf
  • wget https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/examples/customPostgresql.conf
  • Edit all the downloaded files (for example using nano) and change everything that starts with {{ and ends with }}
  • mkdir -p volumes/pictrs
  • chown -R 991:991 volumes/pictrs
  • docker-compose up -d

Installing webserver

I chose Caddy, you can choose a different one but then you'll have to check on your own.

From this guide: https://caddyserver.com/docs/install#debian-ubuntu-raspbian

  • apt install -y debian-keyring debian-archive-keyring apt-transport-https
  • curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
  • curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | tee /etc/apt/sources.list.d/caddy-stable.list
  • apt update
  • apt install caddy
  • Edit the file /etc/caddy/Caddyfile (for example using nano /etc/caddy/Caddyfile)
  • Paste this content (replace domain.tld with your Lemmy instance domain and the 1236 with the port you have configured in the docker-compose.yml file for {{ lemmy_port }}):
domain.tld {
        @http {
                protocol http
        }
        redir @http https://{host}{uri}
        reverse_proxy localhost:1236
}

Hope I haven't forgotten anything, feel free to ask.

Edit: After all the commands, restart caddy with service caddy restart.

load more comments (2 replies)