this post was submitted on 24 Oct 2023
9 points (56.5% liked)

Selfhosted

39980 readers
774 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
 

I've tried to figure some of this stuff out but I really don't know what I'm doing. Most documentation is written with a vocabulary I don't understand. Tutorials assume a high-level understanding of coding, software, CLI and a bunch of other stuff.

So far I've got an old gaming PC with a R7 2700x + 2060 Super and I think maybe it's overkill. I've got TrueNAS running on it but that's about as far as I got...

Thinking maybe we can have an open Jitsi meeting and just anyone who needs help can get it (myself included 🙂)?

Would anyone be interested in something like that?


E: some people have imagined up some things that I said so let me be clear about what I did not say:

At no time did I insist, beg, or demand that anyone help me.

I did NOT ask anyone to help with a specific issue, nor should I be required to.

I asked if anyone would be willing to help myself and possibly others to get some services running, and I asked to do it in a videoconference setting where we can have a discussion and where you can see what I'm doing as I'm doing it, out of respect for both of our time.

If you are not interested, you do not need to come in here and announce it, and you sure as shit do not need to speak for anyone else on whether they will want to. Just keep scrolling.

E2: special thanks to those who actually reached out and offered to help!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 1 year ago

SSH - secure shell. It is a way to connect to your remote machine. On server distributions it is usually open by default. If you're running Windows on your main computer, you can connect with either the included OpenSSH client (terrible experience) or download a utility like PuTTY. Detailed explanation here: https://bitlaunch.io/blog/how-to-connect-to-ssh-with-putty/

Web shell - Likely refers to the admin control panel of the software. I don't run TrueNAS so I can only assume. Likely if you open a browser tab and type in your server's IP and the specified port in the documentation you'll be able to access it (i.e http://192.168.50.2:8080)

“go to system --> advanced” where!? - Likely in the admin panel. Again, don't run the software personally.

Link aggregations - This is more on the advanced side and likely not necessary for you at this stage. The idea is to allow you to connect more interfaces and increase bandwidth, likely not necessary for a home set up, would advise you keep it for later.

VLAN - Virtual Local Area Network. In the past before VLANs we had switches/hubs that when you connected a cable to them they would automatically become a member of the same network. VLAN allows you to split one physical network into many virtual networks. This is good because you can them limit access inbetween VLANs or block traffic for your server VLANs (if for example, you don't want it to collect telemetry and phone home. I personally do it on the IoT VLAN).

Default Gateway - It is the IP address of your router in most cases. If you are on the 192.168.10.0 - 192.168.10.255 network and you're trying to send packets inside that network then your clients will not contact the default gateway, they will instead just reach each other directly. The default gateway is necessary to send packets outside of your network.