Skip to content

Commit 4cb95ad

Browse files
committed
updates
1 parent 93c586b commit 4cb95ad

File tree

2 files changed

+4
-72
lines changed

2 files changed

+4
-72
lines changed

_posts/2025-04-22-mintyserver-debian-server-install-guide.md

Lines changed: 4 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -72,80 +72,12 @@ Alright, so our USB drive in hand, we plug it into the computer and reboot into
7272

7373
Once you boot into Ventoy, it's a pretty easy process to pick the ISO file you want to boot up
7474

75-
![ventoy starting](/assets/img/mintyserver/ventoyStart.jpeg)
76-
7775
From there we'll select the Debian image that we saved onto there, and then boot it into normal mode.
7876

79-
After that it's a pretty standard Debian install, hostname was `mintyserver-plex`, to specify that it's the Plex server. We are not going to install a desktop, and instead keep it only as an SSH server. The last notable thing we are going to do is manually partition the server out. Since all the media is being stored on an external drive, we can afford some more swap space than normal.
80-
81-
Now, I am aware that a general convention for swap is 1.5x the amount of RAM the system has installed, but seeing as the server only has 8GB of RAM I decided to allocate a whole 24GB of swap for any transcoding issues that occur.
82-
83-
## Testing... Testing...
84-
Sweet, so let's go back to our computer and connect right in!
85-
86-
```terminal
87-
┌─[slavetomints@parrot]─[~]
88-
└──╼ $ssh slavetomints@plex.mintyserver.lab
89-
ssh: connect to host plex.mintyserver.lab port 22: No route to host
90-
```
91-
92-
> Note: for now all the domain names are a result of `/etc/hosts` shenanigans, once we install some more services, I plan to get a DNS server up and running on the lab to organize all of this.
93-
{: .prompt-info }
94-
95-
Hm, seems like it's not connected to the network, which would be correct. Since we haven't run any ethernet cable to the server, and it has a WLAN card, let's go ahead and set up Wi-Fi for the server temporarily.
96-
97-
### Wireless Access
98-
Alright, so on the server, we don't have `nmcli`, or `nmtui`, which are both very popular network managers used. For this we'll be using `wpa_supplicant` to connect to the network. First off, we'll need to configure the `/etc/wpa_supplilcant.conf` file:
99-
100-
```plaintext
101-
ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev
102-
update_config=1
103-
country=US
104-
105-
network={
106-
ssid="SSID"
107-
psk="PASSWORD"
108-
}
109-
```
110-
{: file="/etc/wpa_supplicant.conf"}
111-
112-
Alright, so line by line let's go over this.
77+
![](/assets/img/mintyserver/debianInstall.png)
11378

114-
1. `ctrl_interface=DIR=/run/wpa_supplicant GROUP=netdev`
115-
This line allows it to work with CLI tools, and also allows those in the `netdev` group to edit the file without needing `root` access.
116-
2. `update_config=1`
117-
This line allows those other tools to edit this file and save configs.
118-
3. `country=US`
119-
This is included for regulatory compliance
120-
4. `network={...`
121-
This is where you throw in the SSID and password of the wireless network to connect.
79+
After that it's a pretty standard Debian install. We are not going to install a desktop, and instead keep it only as an SSH server. The last notable thing we are going to do is manually partition the server out. Since all the media is being stored on an external drive, we can afford some more swap space than normal.
12280

81+
Now, I am aware that a general convention for swap is 1.5x the amount of RAM the system has installed, but seeing as the server only has 8GB of RAM I decided to allocate a whole 24GB of swap for any transcoding issues that occur.
12382

124-
Once all of that is done, lets run the command `sudo wpa_supplicant -B -i wlp0s20f3 -c /etc/wpa_supplicant.conf`. The `-B` flag specifies background mode, so we can still use the CLI without having logs pollute the terminal. `-i wlp0s20f3` specifies the interface, and `-c /etc/wpa_supplicant.conf` specifies the configuration file we're using.
125-
126-
Now remember, this is only a temporary solution until I can run Ethernet down to the server, and we won't be using it for the long term.
127-
128-
After that, we need to get an IP from the router, so the command `sudo dhclient wlp0s20f3` will do just that. Now running `ip a` we see:
129-
130-
```terminal
131-
slavetomints@mintyserver-plex:~$ ip address | grep 192
132-
inet 192.168.1.75/24 brd 192.168.1.255 scope global dynamic wlp0s20f3
133-
```
134-
135-
Heck yeah! we got an IP. Let's try that SSH connection again
136-
137-
```terminal
138-
┌─[slavetomints@parrot]─[~]
139-
└──╼ $ssh slavetomints@plex.mintyserver.lab
140-
slavetomints@plex.mintyserver.lab's password:
141-
142-
The programs included with the Debian GNU/Linux system are free software;
143-
the exact distribution terms for each program are described in the
144-
individual files in /usr/share/doc/*/copyright.
145-
146-
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
147-
permitted by applicable law.
148-
slavetomints@mintyserver-plex:~$
149-
```
150-
151-
We did it!
83+
And thats about it, once we're here, make sure you can get an IP address and then you can SSH in and remotely work with the server!
-1.89 MB
Binary file not shown.

0 commit comments

Comments
 (0)