Goofed Home

I was scared off a couple years ago when I attempted to host it myself. I took a break from selfhosting, but now I’m back, and from what I learned in the past, I know now not to torture myself swimming upstream when there are far easier downstream currents to follow.

I’m looking at conduit but I’m currently writing up a doc to plan out the process, and understand it before I actually deploy anything. I don’t want to open ports, don’t need federation and don’t need encryption, since I’ll be using tailscale to host a private server to only members of my tailnet.

I’ll report back, either here or in the main community, because I don’t want to expose ports, rent a VPS or use ansible for a simple private server for less than 10 people.

Basically looking for an all in one program similar to the Arr stack that’s easy to use. If it needs to / can be set up with an NBZ or Debrid service beforehand it’s fine, it’s mostly on the daily usage part that it should have a somewhat friendly GUI. Also helps if it has or can be paired with an app for remote streaming what’s on the server.

Ideally works on Cosmos, but if it can’t for any reason, then CasaOS or Yunohost might be fine too.

I’m trying to set up something rather easy to use for my two partners, who are not the most tech savvy, and one of which who really dislikes clunky menus.

Technically, you don’t really need to touch those Arr applications once you set them up. As others have mentioned, Seerr (merged from Jellyseerr and Overseerr) is probably the only thing you use on daily basis.

You mentioned an app for remote streaming, I assume you know about Jellyfin already. If not, it’s like Netflix but you watch your own videos.

HugOP wants remote streaming - that’s a no for jellyfin, especially for people who couldn’t handle the sonarr/radarr UI.

I started setting up longhorn today. My hardware is a little it beefier, but I still am curious: what performance problems did you run into exactly?

What CPUs are you running exactly? I was under the assumption my greatest bottleneck would be an 1Gbps LAN

Just don’t go below 4 cores of x86 and you’ll be fine

Hey,

have you ever wondered how to search the web while staying in your browser and eating your cereals in the morning?

This is a free solution that you can host yourself and also sell (if you want to, everything is included):

https://github.com/qubit999/voice-browser.git

You can host it locally on your computer but you need access to the API services.

It’s in its early stage and heavy vibe-coded, so I don’t guarantee anything but it’s a fun tool to play around with.

Browser that’s vibe coded 💩
No fucking way I’m hosting this

AI app written using AI. What could go wrong?

I set up a community on midwest.social (because I’m in the midwest) !homelabsales@midwest.social

Oh sarcasm, I am an idiot

Docker compose is how you can define a set of services and then run them. Those services are defined in a yaml file. Most programs provide their own way to be ran through docker compose. Env is a shorthand for environment, basically values you pass to customize the services.

I know this isn’t “selfhosting” as most people imagine it, but it is about hosting services on own hardware, hence why I’m posting in this community.

I’m supposed to help a teacher set up a networking exercise where pairs of computers are connected directly on a crossover cable and can access services (echo, HTTP, SSH, FTP) on each other. Every computer is identical: Windows 10 host, one VirtualBox VM running Linux Mint with a bridged adapter in promiscuous mode. Each host and VM has its own static link-local IP address.

The problem is, the VMs can’t talk to each other, and I don’t know why.

From one VM, I can ping itself, its host, and the remote host, but not the remote VM. Each host can ping itself, the local VM, the remote host, but not the remote VM. I’ve tried connecting both hosts to a layer-2 switch, with the same result.

Can someone point me at the one thing that I’m obviously doing wrong?

https://lemmy.world/pictrs/image/29119389-18af-4b95-9019-6b44902c0460.png

Running Linux on metal isn’t an option. In the past, the classroom computers used to dual boot Windows and Ubuntu, but the Windows install got so bloated (the software too, not just Windows) that it needs the full SSD.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

[Thread #104 for this comm, first seen 19th Feb 2026, 11:31] [FAQ] [Full list] [Contact] [Source code]

Thanks for the follow-up. Of course you would have some kind of mass-deployment, it didn’t think of that. I thought you’d maybe copy the Windows MAC to Linux, but… then you’d remember doing that.

Next up, they will also all have the same ssh host key ;-) (Which may be an advantage actually, but still confusing.) Those are the kind of problems cloud-init is solving, I guess.

Ha, I have a N95 box. Didn’t know they make those with 6 Lan ports. What routing container do you run? Something like Openwrt or pfsense?

I love it, have serial (rj45), no more need for monitor/keyboard setup in my “server room”. I have some raspberry-pi in my “family”-vlan, so i can always ssh/serial on to my proxmox. considering my secret superpower is “locking myself out from my firewall” this is really comfortable.

I’m just running debian trixie. I really don’t like openwrt and pfsense. I deal a bit with openwrt from time to time on embedded devices, APs or the like… just incredibly complicated to configure the firewall, which comes with like 28 default policy I would not know why I need those :D

I like the many ports. Internally I have everything over one port with plenty of VLANs, but I like my ISPs directly connected to cut out the switch and leaves my firewall as sole single point of failure. at least for internet reachability of my services.

my current project is integrating the multi homed wan and vpn choices into my home assistant. sadly it seems to be complicated to to route specific traffic (like .*bbci?.co.uk) via specific tunnels. sni detection is broken thanks to ech. Not sure if ech is even employed by bbc (akamai/amazon/fastly), but if i try to policy-route this traffic i cant watch :-( have to set the whole device to the VPN and it works fine.

Hello all,

I figured that a chunk of the selfhost community is using Caddy, so decided to post my query here. I am a novice in Caddy, so I might be saying some incorrect terms.

Some information - The router and the host running Caddy, are different machines - The router page is running HTTP, but I am accessing it via HTTPS through Caddy - Caddy is running via Docker.

I have a couple of services running on a host, so I access them via Caddy’s reverse proxy. Now I am also trying to access my router login via the same reverse proxy. This is what the router entry in the caddyfile looks like

.
.
{
    local_certs
}
login.router.lan {
	reverse_proxy 192.168.1.1:80
}
.
.

With this entry, I can access the login page. However, when I enter the password, I feel like it’s attempting to login but then it just comes back to the original login page. When I access it directly, the login is successful. I also have Pihole running and the Pihole login process works fine. So I suspect that the router login page is expecting some extra information from Caddy to forward it to the login page.

After some searching online and some LLM wrangling, I figured it’s some cookie issue or my login page is expecting a certain host.

What should I add to my Caddyfile so that the login redirect works?

Semi related, you can check the validity of Caddy entries into the caddyfile:

• sudo caddy fmt --overwrite /etc/caddy/Caddyfile
• caddy validate --config /etc/caddy/Caddyfile

Where /etc/caddy/Caddyfile points to your caddyfile.

I have tried this, but unfortunately, it did not work. I have tried this suite of commands

login.router.lan {
    reverse_proxy 192.168.1.1:80 {
        # Preserve original host and scheme
        header_up Host {upstream_hostport}
        header_up X-Forwarded-Proto {http.request.scheme}
        header_up X-Forwarded-Host {http.request.host}
        header_up X-Forwarded-For {http.request.remote.host}

        # Keep cookies intact
        header_up Cookie {http.request.header.Cookie}
        header_down Set-Cookie {http.response.header.Set-Cookie}

        # Preserve Origin/Referer for CSRF tokens
        header_up Origin https://{http.request.host}
        header_up Referer https://{http.request.host}{http.request.uri.path}
    }
}

Info: My caddy uses HTTPS but the router login page is HTTP. Not sure if this is relevant.