Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

My Homelab Setup

bryananthonio.com

Post reply on HN
Print view View original

151–160 of 232 posts

Re: My Homelab Setup

#151

Post by sv0 »

gerdesj wrote: post #112
linsomniac wrote: post #9

>Because all of my services share the same IP address, my password manager has trouble distinguishing which login to use for each one. In Bitwarden they allow you to configure the matching algorithm, and switching from the default to "starts with" is what I do when I find that it is matching the wrong entries. So for this case just make sure that the URL for the service includes the port number and switch all items t…

"Because all of my services share the same IP address" DNS. SNI. RLY?

That's a bit weird to read for me as well. DNS and local DNS were the first services I've been self-hosting since 2005.

On Debian/Ubuntu, hosting local DNS service is easy as `apt-get install dnsmasq` and putting a few lines into `/etc/dnsmasq.conf`.

Re: My Homelab Setup

#152

Post by merpkz »

sv0 wrote: post #151
gerdesj wrote: post #112

Earlier quoted context omitted.

"Because all of my services share the same IP address" DNS. SNI. RLY?

That's a bit weird to read for me as well. DNS and local DNS were the first services I've been self-hosting since 2005. On Debian/Ubuntu, hosting local DNS service is easy as `apt-get install dnsmasq` and putting a few lines into `/etc/dnsmasq.conf`.

These modern-day homelabbers will do anything to avoid DNS, looks like to them it's some kind of black magic where things will inevitably go wrong and all hell will break loose.

Re: My Homelab Setup

#153

Post by ozim »

m463 wrote: post #137
linsomniac wrote: post #9

>Because all of my services share the same IP address, my password manager has trouble distinguishing which login to use for each one. In Bitwarden they allow you to configure the matching algorithm, and switching from the default to "starts with" is what I do when I find that it is matching the wrong entries. So for this case just make sure that the URL for the service includes the port number and switch all items t…

or just use the same password for everything. ;)

If it is like 12 characters non dictionary and PW you use only in your homelab - seems like perfectly fine.

If you expose something by mistake still should be fine.

Big problem with PW reuse is using the same for very different systems that have different operators who you cannot trust about not keeping your PW in plaintext or getting hacked.

Re: My Homelab Setup

#154

Post by Pooge »

Prabhapa wrote: post #133

use cloudflare & cloudflare tunnels for exposing your apps over internet via custom domains. Its free of costs. Tailscale only allows 3 devices i suppose. If we have more devices to be able to connect to , then cloudflare is the best .

> use cloudflare

Please don't

Re: My Homelab Setup

#155

Post by sambf »

firecall wrote: post #127
xandrius wrote: post #55

One thing to consider before doing the same, a computer done for homelab has a much lower consumption. The setup mentioned in the article has an avg 600 kWh/year as opposed to a pretty solid HP EliteDesk (my own homelab) which uses 100 kWh/year. Sure you don't get a GPU but for what it is used for, you might as well use a laptop for that.

One reason to repurpose desktops is that you get a full ATX Motherboard with SATA ports! If you are doing a DIY NAS with HDDs then you want real SATA ports. Or a well supported PCI card with SATA Ports, which you cant sensibly connect to a Laptop or micro PC. Sure, you might be able to use Thunderbolt to reliably hook up an external PCI chassis, but then you might as well buy a NAS at that point or use a full tower c…

M.2 SATA cards are also a thing, I repurposed a NUC in a SuperMicro (SYS-521R-T) mini tower server with 4 drives and it works great.

Re: My Homelab Setup

#156

Post by Semaphor »

tuananh wrote: post #130

*most* of the homelab setup doesn't have much load so it's mostly matter of ram available and then power consumption. many people with setup like this probably needs maybe a 4 cores low powered machine with idle consumption at ~5-10w

Yeah, this is the AI tax. I have several times as many services (28) on a vastly smaller machine (N100 fanless), but besides some very light AI for image detection which runs on CPU, I have no AI there, so I don’t need a desktop PC.

Re: My Homelab Setup

#157

Post by luzionlighting »

Clean setup. It's interesting how much attention people give to cable management and layout in tech setups.

In architectural lighting projects we often think in a similar way about fixture placement, wiring access and maintenance because poor planning becomes very visible once a space is finished.

Re: My Homelab Setup

#158

Post by domh »

avtar wrote: post #71
domh wrote: post #46

Earlier quoted context omitted.

You can use tailscale services to do this now: https://tailscale.com/docs/features/tailscale-services Then you can access stuff on your tailnet by going to http://service instead of http://ip:port It works well! Only thing missing now is TLS

This would be perfect with TLS. The docs don't make this clear... > tailscale serve --service=svc:web-server --https=443 127.0.0.1:8080 > http://web-server. .ts.net:443/ > |-- proxy http://127.0.0.1:8080 > When you use the tailscale serve command with the HTTPS protocol, Tailscale automatically provisions a TLS certificate for your unique tailnet DNS name. So is the certificate not valid? The 'Limitations' section do…

I think maybe TLS would work if you were to go to https://service.yourts.net domain, but I've not tried that.

Re: My Homelab Setup

#159

Post by bjackman »

VladVladikoff wrote: post #118
acidburnNSA wrote: post #14

I have something like this, in the same case. I have beefier specs b/c I use it as a daily workstation in addition to running all my stuff. * nginx with letsencrypt wildcard so I have lots of subdomains * No tailscale, just pure wireguard between a few family houses and for remote access * Jellyfin for movies and TV, serving to my Samsung TV via the Tizen jellyfin app * Mopidy holding my music collection, serving to…

For anyone considering this, it's not a good plan to do it this way, if you have any family members relying on these services, you have to kill them all every time you reboot your workstation. It's really not great to mix destop and server like this. (speaking from experiance and I really need to get a separate box setup for this self hosted stuff)

You are always gonna have some downtime in a homelab setup I think. Unless you go all in with k8s I think the best you can do is "system reboots at 4AM, hopefully all the users are asleep".

(Probably a lot of the services I run don't even really support HA properly in a k8s system with replicas. E.g. taking global exclusive DB locks for the lifetime of their process)

Re: My Homelab Setup

#160

Post by lowdude »

bluehatbrit wrote: post #87
reddalo wrote: post #84

Earlier quoted context omitted.

Me too, I highly recommend Hetzner Storage Box. It's cheap, and it works great (unlike their S3-compatible storage, which has been a huge fiasco since they launched it).

Could you elaborate on the issues with their S3 compatible storage? I've been considering it and haven't seen too many issues in my testing, beyond the lack of identity control.

I cannot say much about the quality, but I am also testing around with it at the moment. As for the identity control, you may be able to achieve this with a few extra steps, if you set up bucket policies for the credentials. For this, it would be a bit cleaner to move the storage box to a project of its own.

I still have to check if this actually works in practice, but I am hopeful. I based it off their documentation here: https://docs.hetzner.com/storage/object-storage/faq/s3-crede...

Post reply on HN