Selfhosted

45485 readers

619 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:

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Setting Up Gitea on Proxmox with Cloudflare Zero Trust Tunnels (lemmy.world)

submitted 1 week ago by Cachvza@lemmy.world to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

Hey everyone,

I recently went through the process of setting up a self-hosted Gitea server on a Proxmox LXC and wanted to share the steps I took. A big part of this was securing external access using Cloudflare Zero Trust tunnels for both the web UI (HTTP) and Git operations (SSH).

I know much of the information on Gitea, Proxmox, and Cloudflare tunnels exists separately, but I wanted to try and bring it all together in one place based on my experience. It's also part of my effort to document my own self-hosting journey. 🛠️

The guide covers things like:

Installing Gitea on Proxmox (using helper scripts).
Basic Gitea configuration (web UI, users, keys).
Setting up Cloudflare tunnels for secure HTTP and SSH access.
Configuring the local SSH client and Gitea for tunnelled SSH connections.

It's basically a walkthrough of how I got my personal Git server running and accessible securely from outside my network. Maybe not brand new information for everyone here, but hopefully, it's a useful aggregation for someone looking to do something similar.

You can read the full post here: https://cachaza.cc/blog/03-self-hosted-gitea/

Happy to hear any thoughts or feedback! Cheers.

top 6 comments

sorted by: hot top controversial new old

[–] Pulsar@lemmy.world 10 points 1 week ago (2 children)

There is any particular reason to deploy a new gitea instance instead of forgejo in 2025?

[–] Cachvza@lemmy.world 2 points 6 days ago (1 children)

To be honest, when I set this up and wrote the guide, I wasn't really aware of Forgejo as a distinct option, or at least hadn't looked into it deeply. Gitea came up frequently in my research for lightweight self-hosted Git servers Having had a quick look now that you mention it, while Forgejo definitely looks like a solid project, I'm not immediately seeing any specific features it offers that are essential for my personal use case that Gitea doesn't already cover. Gitea's is meeting my needs perfectly so far. But it's good to know about it, thanks for bringing it up!

[–] Pulsar@lemmy.world 2 points 6 days ago

I have been running a selfhosted gitea instance for many years. However since Gitea Limited as a per profit organization have different objectives than Forgejo and Gitea Source Contributors I will rather not recommend it for selfhosting. Gitea Limited still great for businesses that need access to official support.

[–] possiblylinux127@lemmy.zip 4 points 1 week ago

This

I would go Forgejo all day every day

[–] tVxUHF@lemmy.dbzer0.com 1 points 1 week ago (1 children)

I played with Forgejo recently, but couldn't for the life of me figure out how to get the SSH connections passed to the Forgejo LXC from my Nginx Proxy Manager. No matter what I did, the connection went to the NPM box, not the Forgejo box.

[–] possiblylinux127@lemmy.zip 3 points 1 week ago* (last edited 1 week ago)

You need to forward traffic

SSH is just plain TCP. You probably were trying to use http.