№7267[Quote]
We are stupid -and- homeless edition
previous: 404: Not Found
READ THE WIKI! & help by contributing:
https://wiki.installgentoo.com/wiki/Home_server/hsg/ is about learning and expanding your horizons. Know all about NAS? Learn virtualization. Spun up some VMs? Learn about networking by standing up a OPNsense/PFsense box and configuring some VLANs. There's always more to learn and chances to grow. Think you’re god-tier already? Setup OpenStack and report back.
>What software should I run?Install Gentoo. Or whatever flavor of *nix is best for the job or most comfy for you. Jellyfin/Emby/Plex to replace Netflix, Nextcloud to replace Googlel, Ampache/Navidrome to replace Spotify, the list goes on. Look at the awesome self-hosted list and ask.
>Why should I have a home server?De-botnet your life. Learn something new. Serving applications to yourself, your family, and your frens feels good. Put your tech skills to good use for yourself and those close to you. Store their data with proper availability redundancy and backups and serve it back to them with a /comfy/ easy to use interface.
№7270[Quote]
Cheap disks:
https://shucks.top/ https://diskprices.com/PCIE info:
https://files.catbox.moe/id6o0n.pdf>i226-V NICs are bad for servers>For more SATA ports, use PCIe SAS HBAs in IT modeWiFi fixing: pastebin.com/raw/vXJ2PZxn
Cockpit is nice for remote administration
Remember:
RAID protects you from DOWNTIME
BACKUPS protect you from DATA LOSS
№7308[Quote]
Trying to get Foreman Host Provisioning to work.
I made an image with packer for ubuntu 24.04 and userdata, if I could set up that image for use in foreman, I can get foreman's userdata provisioning template to configure puppet with itself as puppetmaster along with auto registration if I set up the autosign domain.
3.14 has a UI bug that fucks up the image selection
https://community.theforeman.org/t/image-based-provisioning-on-foreman-3-14/42841/3 .
I did initially put the fix in the webpack js file (which should also be gzipped again which the forum didn't mention), but the proxmox compute resource is not that well supported (lots of nill objects). I managed to get it working on 3.10, but the created VM refuses to let go of PXE boot in favor of the packer image.
Hoping I can fix that today.
Katello seems interesting as well, I wonder if you can mirror packages to S3 storage with juicefs, otherwise I might try aptly on a different VM and use puppet to propagate the mirrors.
№7316[Quote]
>>7314That's a good idea, thanks for the link
№7466[Quote]
File: IMG_7362.jpeg 📥︎ (4.84 MB, 5712x4284) a5f2071ec1dfe8a15473a81ac5ec5a8487f0ac2b4ad7d6aba5547e7a581c55540ImgOps
this board sucks compared to 4chins
i just want to to home bros :(
№7476[Quote]
>>7308Got a bit closer, don't quite understand what's up here, I do see that foreman usually creates a cloud-init iso and dumps it to pve local store (probably would want that on a shared store in cluster setup).
Also 3.10 has a UI problem where you need to reselect KVM by toggling between LXC and KVM types, otherwise it messes up the VM creation API request for PVE.
№7477[Quote]
>>7466you suck, i hope you spill that water on top of your rack
№7478[Quote]
>>7466Nigger if this was 4chan half of the thread would be raisin bait
№7480[Quote]
>>7476Ah damn I think I see it now, for some reason foreman creates the cloud-init iso on pve3's local storage and then asks pve2 to fetch it.
№7486[Quote]
I have missed you bros.
№7493[Quote]
>>7480It was, but now Foreman just throws a 'fuck you' error
siiiiiggghhh stack trace is equally nothingburger, might have to go cry on the Foreman forum or on the proxmox plugin github.
I feel like it's the latter, this probably wouldn't happen on VMWare cause that's a first class citizen and foreman is community dependent.
№7494[Quote]
> foreman is community dependent
foreman-proxmox plugin* is community dependent
№7725[Quote]
I'm probably moving to Foreman 3.13, looks like it got its first stable-release update with some UI jank resolved
https://github.com/theforeman/foreman/commits/3.13-stable/ №7726[Quote]
>>7725nvm, none of the repos (deb or yum) are updated
№7733[Quote]
>>7466fucken rich bastard you have to have those beefy UPSes
№7746[Quote]
what are yall niggas even running on them servers?
№7769[Quote]
Okay I'm steering clear from foreman until after they released 3.13.1 in the hopes that it resolves the generic bugs while still allowing me to get the latest proxmox plugins without manually adjusting the bundler.d
https://community.theforeman.org/t/foreman-3-13-1-release-process/42878 Got some minikube raisin on the agenda, I know fuck all about k8s except that the orchestration and multi node setup can be interesting for my proxmox cluster. Had hoped to setup easy host provisioning before trying k8s, but I already have a packer template so I'll stop being lazy.
Gonna follow this tutorial and report back in a couple of hours, I already watched the architectural explanation part and she's got it across pretty well without baby terms.
https://www.youtube.com/watch?v=X48VuDVv0do №8316[Quote]
>>7769Okay, some hours later, good tutorial. Think I can start migrating some basic containers I have scattered on my VMs to my k8s cluster now.
For databases I am considering setting up a separate patroni and mariadb clusters instead of letting each service run its own db connections.
№8351[Quote]
Retard question of the day: how would one go about running a url command through an ssh connection? I'm trying to figure out how to do headless plex updates but it seems I'm required to run commands in the form of
>http://myserver:plexport/blahblahblah….I have a hunch there's a simpler way of going about this than trying to graphically emulate a browser, right? Because doing that over ssh spits back:
>Error: no DISPLAY environment variable specifiedWhat are my options here? Both devices are running xubuntu
№8520[Quote]
>>8351they dont have a cli? anyway you can run any commands via ssh, maybe look into curl
ssh "user@192.168.0.1" "your command"
№9296[Quote]
>>7732what do you run on em
№9382[Quote]
File: Capture.PNG 📥︎ (2.26 KB, 571x26) 3afff043f0273efb06531124eda0065807580da499a47e5a1fe3f9a7f0d370530ImgOps
If your uptime is less than 177 days, lower your tone when speaking to me.
№9408[Quote]
>If your uptime is less than 177 days, lower your tone when speaking to me.
ur using a linux kernel that many versions behind? fucking retard ur just asking to be hacked
№10249[Quote]
>>9408Only forwarded port is plex. I will be fine.
№10269[Quote]
>>9382only 177?
>>9408LTS kernels are a lot more secure than whatever buggy new unstable garbage linus keeps raisinting out, plus grsecurity and live patching exist
>>10249plex is proprietary malware, you are just asking to get cracked
>>8351this is X11 complaining about you trying to launch an X11 client on your server over ssh, you can do DISPLAY=:0 somecommand
but this will probably not work. if you run some webraisin UI on a local port on your server but want to access it from somewhere else without port forwarding, you can use ssh reverse tunneling
tl;dr, make sure sshd is running, set GatewayPorts to yes in your sshd_config and restart it, make sure you have port 22 (or any other port if you want) forwarded on your server, and forward some port (ideally 22) on your client as well, because you'll need to ssh into that from your server.
on your server, run this:
ssh -NR 1212:localhost:1234 user@1.2.3.4
this will tunnel port 1234 from your server to port 1212 on your client, replace 1212 with the port you want to open in your web browser, i.e. as localhost:1212, replace 1234 with the port plex exposes on your server (the one you'd curl on your server, i.e. curl
http://127.0.0.1:1234/something, and user@1.2.3.4 with your client's username and ip
№10556[Quote]
>>10269>make sure you have port 22 (or any other port if you want) forwarded on your serverA few questions regarding port forwarding:
If I want to send plex's web UI [localhost:32400/blah] from server 1.2.3.4 to some specified port on client 1.2.3.5, say localhost:32500 for simplicity's sake…
Would my router configurations for port forwarding for the server's IP (1.2.3.4) be:
>external port: 32500>internal port: 32400And by extension of that, would my ssh command be
>ssh -NR 32500:localhost:32400 user@1.2.3.5?
№10808[Quote]
Thoughts on techhut (youtube) ? Was thinking about following a guide of his for a baby's first home server on my t480
№10818[Quote]
>My dusty beauty of a homelab and my colocation server
fiber patch panel is pretty gangster, gotta say
№10825[Quote]
>>10556you'd do this on your server:
ssh -NR 32500:localhost:32400 user@1.2.3.5
and no, you literally don't have to forward anything other than port 22 for ssh, thats why ssh reverse tunneling is nice
you actually don't even need port 22 forwarded on your server if you were physically there and have some other way of controlling your server, you only need port 22 (or another port for ssh) forwarded on your client (which you ssh into from your server)
so if you can port forward and want to help some guy who doesn't want to (or can't) port forward, he can ssh reverse tunnel into your machine (you can create a new user and set its login shell to nologin, you NEED -NR to let anyone connect without getting kicked out, and you can't run commands or get a shell), and let you ssh into localhost:1337 or something (his machine)
>>10600i had a power outage 270 days ago, i had 400 days uptime, RIP.
>>10808don't fall for fancy "easy setup" framework crap, you'll have to deal with nginx yourself if you want to actually do something
№11111[Quote]
>>10825Okay now that I've had several looks at this I think I understand.
ssh reverse Tunneling is exactly what it sounds like - Instead of a client initiating an shh connection to some random ssh server to access stuff on the server, this is the reverse, wherein the target server starts the ssh connection, which ultimately allows the client to access some port via a regular browser, without even necessitating CLI?
And by extension of that fact, it makes some sense why a normal ssh connection doesn't need port forwarding, as you are getting permission to access the port by virtue of signing in as a user of the server. Where with the reverse, the client needs to be able to accept this specific type of ssh connection, which by extension requires you to actually set up port forwarding on the router? Did I get all that right?
And from that, the next logical query: what are the functional differences and importance of the external vs internal ports selections when setting up port forwarding in the router settings? For this application (lan stuff), and in general usage?
Thank you for your wisdom, I think I recognize you from our old, obliterated home.
№11246[Quote]
I want to build a home cloud to save a small amount of valuable information, I need the build to be as cheap, energo-effficient and data-persistent as possible. What are my choices?
№11312[Quote]
Bumoe
№11439[Quote]
>>11395Nevermind - the original thread was accidentally killed by the mods, /g/ was replaced by /a/ and posting is blocked so we're still…stuck here…
№11786[Quote]
>>10825>ssh -NR 32500:localhost:32400 user@1.2.3.5Just wanted to report back that this worked perfectly even without any sort of router port forwarding! Everything's local and both devices have a signed cert regarding each other's SSH creds so I guess we're good to go. Love you king.