WEBVTT 1 00:00:00.040 --> 00:00:03.480 Hey everyone, and welcome back for another deep dive. Today. 2 00:00:03.960 --> 00:00:05.879 We're going to be looking at setup and manage your 3 00:00:05.919 --> 00:00:10.000 Virtual Private server by John Westfall. Sounds good, and we're 4 00:00:10.000 --> 00:00:13.000 going to be talking all about vps's. Yeah, you know 5 00:00:13.599 --> 00:00:16.480 what they are, why you might want one, and maybe 6 00:00:16.519 --> 00:00:17.719 how to pick the right one for you. 7 00:00:18.519 --> 00:00:19.640 Yeah. It's a great topic. 8 00:00:19.839 --> 00:00:22.320 And it's not just about the tech though, right, it's 9 00:00:22.320 --> 00:00:27.559 about understanding the power and the responsibility, right that comes 10 00:00:27.559 --> 00:00:29.199 with having your own little corner of the Internet. 11 00:00:29.320 --> 00:00:31.480 Yeah. And it's a really interesting topic because it's a 12 00:00:32.039 --> 00:00:35.079 It kind of bridges the gap between you know, basic 13 00:00:35.119 --> 00:00:37.679 web hosting that everybody you know kind of starts with, right, 14 00:00:37.719 --> 00:00:40.960 and then those expensive dedicated servers that you know, big 15 00:00:40.960 --> 00:00:41.759 companies are using. 16 00:00:41.840 --> 00:00:44.359 Yeah, like finding that sweet spot, right, Yeah, where you 17 00:00:44.359 --> 00:00:46.119 have more control but without breaking. 18 00:00:45.840 --> 00:00:46.600 The bank exactly. 19 00:00:46.640 --> 00:00:48.719 But before we get ahead of ourselves, let's back up 20 00:00:48.719 --> 00:00:50.439 a little bit. What is a VPS? 21 00:00:50.600 --> 00:00:52.560 Yeah, So think about it like this. It's like an 22 00:00:52.600 --> 00:00:55.719 apartment building. You've got this one big, powerful computer and 23 00:00:55.759 --> 00:00:59.840 that's the server, and it's divided into smaller, self contained units, 24 00:01:00.280 --> 00:01:02.240 each of them running its own operating system. 25 00:01:02.600 --> 00:01:05.840 Okay, and when you rent a VPS, you're basically renting 26 00:01:05.840 --> 00:01:08.519 one of those apartments. Okay, so you have complete control 27 00:01:08.560 --> 00:01:12.079 over what happens inside, but you're still sharing, you know, 28 00:01:12.239 --> 00:01:14.439 the building's resources like electricity and plumbing. 29 00:01:14.519 --> 00:01:16.120 Yeah, so it's like having your own place, but you 30 00:01:16.200 --> 00:01:19.040 still have like a shared gym or laundry room exactly. Okay, 31 00:01:19.120 --> 00:01:21.480 that makes sense. But how is that different from just 32 00:01:21.519 --> 00:01:23.519 regular web hosting. I mean, I'm already paying for that, 33 00:01:23.560 --> 00:01:24.680 so why would you need a VPS? 34 00:01:24.879 --> 00:01:28.879 Right, So, with regular web hosting, it's more like renting 35 00:01:28.879 --> 00:01:32.280 a booth in somebody else's store. You know, you can 36 00:01:32.319 --> 00:01:35.560 decorate your booth, you can display your products, but you 37 00:01:35.680 --> 00:01:39.480 have to follow the store's rules. Oh you can't suddenly 38 00:01:39.519 --> 00:01:41.840 decide to stay open, you know, twenty four to seven 39 00:01:41.959 --> 00:01:45.439 or start selling something completely different. But with the VPS, 40 00:01:45.480 --> 00:01:47.840 you have the freedom to set your own rules. You 41 00:01:47.879 --> 00:01:50.480 could even choose to run your own email server, which 42 00:01:50.480 --> 00:01:52.920 you can't do with most basic hosting plans. 43 00:01:53.200 --> 00:01:56.439 Okay, so more control, more flexibility. What about the downside, 44 00:01:56.439 --> 00:01:58.959 I mean there's got to be a catch, right, Yeah, 45 00:01:59.000 --> 00:02:01.560 there's definitely a trade, and the book actually paints a 46 00:02:01.680 --> 00:02:05.400 pretty vivid picture of the responsibility that comes with a VPS, 47 00:02:06.319 --> 00:02:10.360 imagine waking up one morning and your entire blog, all 48 00:02:10.439 --> 00:02:15.840 your content, it's just gone, oh no boof. With shared hosting, 49 00:02:16.319 --> 00:02:18.800 you know, you'd call tech support and they'd hopefully sort 50 00:02:18.800 --> 00:02:21.599 it out. But with a VPS, you are the tech support. 51 00:02:22.639 --> 00:02:25.000 If you don't have backups or haven't taken the right 52 00:02:25.080 --> 00:02:28.319 security precautions, you could be in big trouble. 53 00:02:28.439 --> 00:02:31.120 That's a sobering thought. Yeah, I mean, it really makes 54 00:02:31.159 --> 00:02:33.800 you realize that it's not just about the cool stuff 55 00:02:33.840 --> 00:02:35.719 you can do, but it's also about, you know, being 56 00:02:35.719 --> 00:02:37.479 prepared to handle the technical side of things too. 57 00:02:37.599 --> 00:02:39.879 Exactly. It's not all fun in games, right, It got 58 00:02:40.039 --> 00:02:41.599 to be responsible. 59 00:02:41.080 --> 00:02:43.159 Yeah, for sure. But that doesn't mean it's out of 60 00:02:43.159 --> 00:02:45.360 reach for regular people, right. I mean one of the 61 00:02:45.360 --> 00:02:46.120 advantages the. 62 00:02:46.080 --> 00:02:49.840 Cost, Yeah, definitely. The book mentions a real world example 63 00:02:49.879 --> 00:02:52.680 where somebody needed more power than shared hosting could offer, 64 00:02:52.719 --> 00:02:55.840 but they couldn't justify, you know, the expense of a 65 00:02:55.879 --> 00:02:58.919 dedicated server. Right, A dedicated server was costing over one 66 00:02:58.960 --> 00:03:01.080 hundred dollars a month, and they found a VPS that 67 00:03:01.120 --> 00:03:02.960 fit their needs for under twenty dollars. 68 00:03:03.199 --> 00:03:06.120 Wow, that's a huge difference. It is so for somebody 69 00:03:06.159 --> 00:03:09.400 who's kind of outgrown basic hosting, but they're not ready 70 00:03:09.439 --> 00:03:11.319 to shell out the big bucks. A VPS seems like 71 00:03:11.319 --> 00:03:13.599 a pretty good middle ground for sure. You know, it's 72 00:03:13.599 --> 00:03:16.000 funny how we talk about websites and servers like they 73 00:03:16.039 --> 00:03:19.520 just magically appear. Yeah, click a link, Boom, there's the page. 74 00:03:19.879 --> 00:03:21.879 But what is actually happening behind the scenes. 75 00:03:21.919 --> 00:03:24.199 It is really easy to take the Internet for granted, 76 00:03:24.319 --> 00:03:26.840 I know, right, But every time you visit a website, 77 00:03:26.840 --> 00:03:31.159 there's this complex dance of communication happening between your computer 78 00:03:31.319 --> 00:03:34.120 and the server where that website is hosted. Okay, So 79 00:03:34.199 --> 00:03:37.120 let's break it down using the books. Example of visiting 80 00:03:37.159 --> 00:03:39.120 the website bapirate dot com. 81 00:03:39.199 --> 00:03:41.439 Okay, take us on a virtual voyage. 82 00:03:41.080 --> 00:03:43.919 All right. So first your computer needs to figure out 83 00:03:43.960 --> 00:03:47.360 where this biro dot com server is actually located, okay, 84 00:03:47.439 --> 00:03:50.639 and it does this through DNS, the Domain Name system okay, 85 00:03:50.800 --> 00:03:54.159 which is like a giant GPS for the Internet. You 86 00:03:54.199 --> 00:03:57.800 type in the human readable address bopirate dot com and 87 00:03:57.960 --> 00:04:01.520 DNS translates that into this verus IP address, which is 88 00:04:02.039 --> 00:04:03.360 the computer friendly location. 89 00:04:03.759 --> 00:04:06.360 So DNS is like looking up an address in the phone. 90 00:04:06.159 --> 00:04:10.000 Book exactly Once your computer knows the server's address, it 91 00:04:10.000 --> 00:04:12.439 needs to find the right door to knock on. And 92 00:04:12.479 --> 00:04:15.080 this is where port numbers come in. Think of them 93 00:04:15.120 --> 00:04:18.000 like specific apartment numbers within that server building. 94 00:04:18.079 --> 00:04:18.439 Okay. 95 00:04:18.560 --> 00:04:21.360 Port eighty is usually the standard door for web traffic, 96 00:04:21.519 --> 00:04:24.439 and port four forty three is the secure door for 97 00:04:24.600 --> 00:04:26.079 HTTPS websites. 98 00:04:26.160 --> 00:04:29.279 Okay, So we've found the building with DNS right, and 99 00:04:29.319 --> 00:04:31.000 then the right apartment with port number. 100 00:04:31.120 --> 00:04:34.560 Yep. What happens next, So your computer sends a request 101 00:04:34.600 --> 00:04:36.600 for the specific web page you want to see. So 102 00:04:36.680 --> 00:04:38.720 let's say the homepage of bpirate dot com. 103 00:04:38.720 --> 00:04:39.000 Okay. 104 00:04:39.879 --> 00:04:42.199 The server now knows exactly what you're looking for and 105 00:04:42.240 --> 00:04:46.519 gathers all the necessary files, the HTML, the CSS, the images, 106 00:04:46.759 --> 00:04:50.160 maybe some JavaScript, and sends them back to your browser. Okay, 107 00:04:50.279 --> 00:04:52.759 and your browser then assembles all of those pieces into 108 00:04:52.800 --> 00:04:55.360 the beautifully formatted web page that you see on your screen. 109 00:04:55.519 --> 00:04:57.439 Wow, it's amazing how much is happening in just the 110 00:04:57.439 --> 00:04:59.680 blink of an eye. Yeah, and to think that this 111 00:04:59.720 --> 00:05:02.600 whole process is triggered every single time we click on 112 00:05:02.600 --> 00:05:04.319 a link or type in a web dress. 113 00:05:04.399 --> 00:05:06.240 I know, it's a lot of work for just opening 114 00:05:06.279 --> 00:05:06.959 a web page. 115 00:05:07.079 --> 00:05:09.439 Yep. That's incredible. But let's say I'm sold on the 116 00:05:09.480 --> 00:05:12.879 idea of getting a VPS. How do I even begin 117 00:05:13.000 --> 00:05:15.439 choosing a provider? Can I feel a bit like picking 118 00:05:15.480 --> 00:05:16.600 a landlord? Doesn't it? 119 00:05:16.600 --> 00:05:18.920 It does? You're absolutely right. It's about finding the right 120 00:05:18.959 --> 00:05:21.319 fit for your needs and for your comfort level. The 121 00:05:21.360 --> 00:05:25.480 book kind of categorizes providers into these three categories, low end, 122 00:05:25.720 --> 00:05:28.560 high end, and cloud providers, and each has its pros 123 00:05:28.600 --> 00:05:29.240 and con. 124 00:05:29.079 --> 00:05:31.639 Okay, can you break those downforce? What are the key differences? 125 00:05:31.800 --> 00:05:34.199 So low end providers are kind of like renting a 126 00:05:34.199 --> 00:05:37.639 storage unit. You get the space, it's affordable, but you're 127 00:05:37.639 --> 00:05:39.120 on your own if something goes wrong. 128 00:05:39.279 --> 00:05:39.600 Okay. 129 00:05:39.879 --> 00:05:42.600 High end providers are more like having a concierge service. 130 00:05:42.920 --> 00:05:45.120 They offer robust support, but you're going to pay a 131 00:05:45.160 --> 00:05:49.040 premium for that handholding. And then you've got the cloud providers, 132 00:05:49.040 --> 00:05:52.519 which are more like renting a flexible workspace. You can 133 00:05:52.600 --> 00:05:55.639 scale your resources up or down as need, paying only 134 00:05:55.680 --> 00:05:57.879 for what you use, but they can be more complex 135 00:05:57.959 --> 00:05:58.560 to manage. 136 00:05:58.759 --> 00:06:03.040 So storage unit, luxury apartment, co working space. I love 137 00:06:03.079 --> 00:06:05.519 these analogies. Yeah, it makes it so much clearer to 138 00:06:05.560 --> 00:06:08.000 actually visualize it. I like that, But what you mentioned 139 00:06:08.040 --> 00:06:11.120 something earlier about Amazon Web Services. Oh yeah, what's the 140 00:06:11.199 --> 00:06:11.759 story there? 141 00:06:12.079 --> 00:06:15.319 So what's fascinating about AWS is that it's not just 142 00:06:15.399 --> 00:06:18.800 some small time hosting company, right, This is a massive 143 00:06:19.000 --> 00:06:22.920 cloud platform that's used by giants like Netflix and Facebook. 144 00:06:23.000 --> 00:06:23.360 Oh wow. 145 00:06:23.639 --> 00:06:28.279 It offers this huge range of services, including VPS hosting 146 00:06:28.319 --> 00:06:29.600 through their EC two service. 147 00:06:29.800 --> 00:06:32.079 So if it's good enough for them, it's probably pretty good. 148 00:06:31.959 --> 00:06:34.240 Right, I think. So it's a pretty good indicator. 149 00:06:34.360 --> 00:06:37.720 Yeah, But I think for most people, the practical considerations 150 00:06:37.720 --> 00:06:40.120 are key. Right. What are some of the things that 151 00:06:40.120 --> 00:06:43.959 we should be looking for when we're comparing different VPS providers? 152 00:06:44.319 --> 00:06:46.560 Yeah, so the monthly fee is just the tip of 153 00:06:46.560 --> 00:06:49.480 the iceberg. You also need to think about things like bandwidth, 154 00:06:49.519 --> 00:06:51.839 how much data your site is going to transfer each month? 155 00:06:52.160 --> 00:06:53.800 And then the cost of domain names. 156 00:06:53.959 --> 00:06:54.160 Right. 157 00:06:54.240 --> 00:06:57.000 Most providers will offer like a first year discount on 158 00:06:57.079 --> 00:07:00.800 domain registration, but those costs can really add up over time. 159 00:07:00.759 --> 00:07:03.759 Right, So factor in those hidden costs. Yeah, And speaking 160 00:07:03.800 --> 00:07:05.959 of things that add up, what about time commitment? How 161 00:07:06.040 --> 00:07:08.759 much time will I actually need to spend setting up 162 00:07:08.800 --> 00:07:10.480 and managing my vps? 163 00:07:10.839 --> 00:07:14.160 Yeah? The book actually includes this really helpful table that 164 00:07:14.199 --> 00:07:17.480 breaks down you know, the time required for each stage, 165 00:07:17.639 --> 00:07:20.560 from you know, signing up for an account to weekly maintenance. 166 00:07:21.040 --> 00:07:23.279 It can really vary from just a few minutes to 167 00:07:23.360 --> 00:07:25.399 several hours for more complex tasks. 168 00:07:25.560 --> 00:07:28.519 Okay, that's good to know. It's easy to underestimate the 169 00:07:28.600 --> 00:07:31.439 time involved in that, especially if you're kind of new 170 00:07:31.519 --> 00:07:34.800 to server management. Yeah, and I know most people probably 171 00:07:34.800 --> 00:07:37.639 skip over the legal stuff. But why should we actually 172 00:07:37.680 --> 00:07:40.240 pay attention to those terms of service in slas? 173 00:07:41.000 --> 00:07:45.600 So these documents they outline your rights and your responsibilities 174 00:07:45.680 --> 00:07:48.160 as a VPS owner. You know, the terms of service 175 00:07:48.199 --> 00:07:50.959 are like your lease agreement with the provider. Okay, and 176 00:07:51.000 --> 00:07:53.839 the SLA the service level agreement. That's their promise to 177 00:07:53.920 --> 00:07:57.120 keep your server running smoothly. It's like they're uptime guarantee. 178 00:07:57.240 --> 00:08:00.120 So it's not just legal jargon. It's actually important for 179 00:08:00.240 --> 00:08:03.240 understanding you know, what you're getting into and what protections 180 00:08:03.279 --> 00:08:03.519 you have. 181 00:08:03.759 --> 00:08:04.319 Absolutely. 182 00:08:04.399 --> 00:08:06.519 Okay, So let's say we've picked our provider, we've signed 183 00:08:06.519 --> 00:08:08.720 all the paperwork, we're ready to roll. How do we 184 00:08:08.759 --> 00:08:12.439 actually use this shiny new VPS? What happens next? 185 00:08:12.600 --> 00:08:14.279 All right, So this is where we start getting into 186 00:08:14.279 --> 00:08:16.959 the world of Linux and the command line Okay. Most 187 00:08:17.000 --> 00:08:19.279 VPS is run on Linux, and the command line is 188 00:08:19.319 --> 00:08:21.040 how you interact with the server. 189 00:08:21.240 --> 00:08:26.839 Linux command line. That sounds a little intimidating, it can be. 190 00:08:26.959 --> 00:08:28.600 It's not as scary as it sounds, though. 191 00:08:28.720 --> 00:08:29.000 Okay. 192 00:08:29.079 --> 00:08:31.560 The command line is just a text based way to 193 00:08:31.600 --> 00:08:34.759 communicate with your server, Okay, and it's actually quite powerful 194 00:08:34.799 --> 00:08:38.240 because it gives you direct access to the server's inner workings. 195 00:08:38.440 --> 00:08:42.000 So no fancy buttons or graphical interfaces. Not really, we're 196 00:08:42.039 --> 00:08:44.600 going old school, we are, all right, But where do 197 00:08:44.639 --> 00:08:47.720 we even begin? What are some of the essential commands 198 00:08:47.720 --> 00:08:48.440 that we need to know? 199 00:08:48.759 --> 00:08:50.759 All right? So the book starts with the basics of 200 00:08:51.000 --> 00:08:55.639 Linux administration. Yeah, you'll learn commands like CD, which is 201 00:08:55.720 --> 00:08:58.799 changed directory and that's for navigating to different directories, just 202 00:08:58.840 --> 00:09:00.600 like clicking through folders on your computer. 203 00:09:00.679 --> 00:09:03.360 Okay, So CD is like moving around. What about seeing 204 00:09:03.440 --> 00:09:05.480 what's actually inside those folds? 205 00:09:05.519 --> 00:09:07.360 So that's where the l's command comes, and it lists 206 00:09:07.399 --> 00:09:10.039 all the files in a directory, just like opening a 207 00:09:10.080 --> 00:09:11.120 folder on your computer. 208 00:09:11.480 --> 00:09:15.559 Okay, got it, So CD kate to move around l's 209 00:09:15.600 --> 00:09:17.799 to see what's there. But what if I want to 210 00:09:17.799 --> 00:09:19.720 actually see what's inside a file? 211 00:09:20.120 --> 00:09:22.679 Not the name for that you would use the cat command. 212 00:09:23.360 --> 00:09:25.759 It displays the entire contents of a file right on 213 00:09:25.759 --> 00:09:29.080 your screen, and it's useful for you know, viewing configuration 214 00:09:29.240 --> 00:09:31.000 files or other small text files. 215 00:09:31.320 --> 00:09:35.039 CAT for peaking inside the files. Okay, I'm starting to 216 00:09:35.039 --> 00:09:37.360 get a little bit more comfortable with this command line thing. 217 00:09:37.679 --> 00:09:40.279 But what if I have a really huge file? You know, 218 00:09:40.320 --> 00:09:42.320 I don't want my screen to be flooded with text. 219 00:09:42.399 --> 00:09:44.679 Don't worry. Lenox has a command for that too. It's 220 00:09:44.679 --> 00:09:47.600 called less and it lets you view large files page 221 00:09:47.639 --> 00:09:49.840 by page, so you can scroll through the content at 222 00:09:49.879 --> 00:09:50.480 your own pace. 223 00:09:50.759 --> 00:09:53.159 Oh, less is more. I like it exactly, But there's 224 00:09:53.200 --> 00:09:55.799 one command that still makes me a little nervous. R 225 00:09:56.039 --> 00:09:57.399 M the delete command. 226 00:09:57.519 --> 00:10:00.440 Yeah, you're right to be cautious with that one. ARM 227 00:10:00.519 --> 00:10:03.159 is a powerful command, especially when you use the adas 228 00:10:03.279 --> 00:10:06.200 R flag, which is for recursive deleution, and that can 229 00:10:06.240 --> 00:10:08.720 wipe out an entire directory and everything in it, just 230 00:10:08.720 --> 00:10:10.799 like accidentally emptying your entire recycle bin. 231 00:10:11.039 --> 00:10:13.480 Yikes. Definitely don't want to do that. Any Tips for 232 00:10:13.519 --> 00:10:15.840 avoiding disaster, Yeah, always. 233 00:10:15.519 --> 00:10:18.240 Double check your commands before you press enter, especially when 234 00:10:18.279 --> 00:10:20.360 you're using ARM, and if you really want to play 235 00:10:20.399 --> 00:10:22.080 it safe. You can use the eye flag and that'll 236 00:10:22.120 --> 00:10:25.519 prompt you for confirmation before deleting each file, so you 237 00:10:25.559 --> 00:10:27.279 have a chance to back out if you made a mistake. 238 00:10:27.399 --> 00:10:31.559 Okay, so double check, use the safety net, and maybe 239 00:10:31.600 --> 00:10:33.120 say a little prayer before you hit enter. 240 00:10:33.360 --> 00:10:34.240 That might help. 241 00:10:35.440 --> 00:10:38.799 But what if I'm not even sure where a file is? 242 00:10:38.840 --> 00:10:40.559 What if I can only remember part of the name 243 00:10:40.720 --> 00:10:43.559 or the data I created it, how do I find it? 244 00:10:43.720 --> 00:10:46.080 That's where the find command comes in. It's like having 245 00:10:46.120 --> 00:10:48.960 a search engine for your server. You can search for 246 00:10:49.039 --> 00:10:52.480 files based on their name, size, modification, date, and all 247 00:10:52.480 --> 00:10:53.919 sorts of other criteria. 248 00:10:54.120 --> 00:10:56.399 So find is like the server's search and rescue team. 249 00:10:56.559 --> 00:10:56.879 It is. 250 00:10:57.440 --> 00:11:00.000 I love it. It's like having a digital bloodhound sniff 251 00:11:00.120 --> 00:11:00.960 out those loss fons. 252 00:11:01.039 --> 00:11:01.720 Yeah. I like it. 253 00:11:02.080 --> 00:11:04.159 But you know, even with these basic commands, the command 254 00:11:04.240 --> 00:11:07.399 line still feels a little bit well old school. 255 00:11:07.480 --> 00:11:08.279 It is old school. 256 00:11:08.440 --> 00:11:11.600 Is there a more user friendly way to manage a VPS? 257 00:11:11.840 --> 00:11:15.679 Absolutely? So. The book introduces us to this fantastic tool 258 00:11:15.720 --> 00:11:18.600 called webmen, and it's kind of a game changer. Webmin 259 00:11:18.720 --> 00:11:21.159 It's a graphical interface that lets you control your server 260 00:11:21.279 --> 00:11:22.320 through your web browser. 261 00:11:22.960 --> 00:11:25.759 So instead of typing commands in a black screen, we 262 00:11:25.840 --> 00:11:29.440 can click buttons and menus exactly. Okay, that sounds much 263 00:11:29.440 --> 00:11:30.080 more my speed. 264 00:11:30.159 --> 00:11:31.960 Yeah, it's much more intuitive for a lot of people. 265 00:11:32.440 --> 00:11:36.000 Webmen organizes task into these logical categories, and so it's 266 00:11:36.080 --> 00:11:39.039 easy to find what you're looking for. You can install software, 267 00:11:39.120 --> 00:11:42.559 you can can figure server settings, monitor performance, all without 268 00:11:42.600 --> 00:11:44.799 having to remember those command line incantations. 269 00:11:45.080 --> 00:11:49.600 Okay, I'm sold. Webmen sounds like a must half. But 270 00:11:49.679 --> 00:11:52.480 before we get too comfortable clicking around, we need to 271 00:11:52.519 --> 00:11:53.480 talk about security. 272 00:11:53.799 --> 00:11:54.240 Of course. 273 00:11:54.759 --> 00:11:56.919 I know we touched on it briefly earlier, but I'm 274 00:11:56.919 --> 00:11:59.960 ready to really lock down my vps. Where do we start? 275 00:12:00.000 --> 00:12:00.120 All? 276 00:12:00.200 --> 00:12:00.399 Right? 277 00:12:00.440 --> 00:12:02.960 So security should always be top of mind when you're 278 00:12:03.000 --> 00:12:05.639 managing your own server. One of the first things you 279 00:12:05.679 --> 00:12:09.600 should do is change the default passwords for all user accounts, 280 00:12:09.679 --> 00:12:12.960 especially the root account. Okay, because those default passwords are 281 00:12:13.000 --> 00:12:16.440 probably as secure as leaving your front door unlocked. 282 00:12:16.039 --> 00:12:19.159 Right, because those are probably sitting in some hacker's handbooks. 283 00:12:18.679 --> 00:12:22.679 Somewhere exactly, And when you create new passwords, make them 284 00:12:22.759 --> 00:12:27.440 strong and unique. The book emphasizes using ungodly long passwords 285 00:12:27.440 --> 00:12:30.360 at least twelve characters, with a mix of uppercase and 286 00:12:30.399 --> 00:12:32.279 lowercase letters, numbers, and symbols. 287 00:12:32.720 --> 00:12:35.039 Okay, so no more password one, two, three, or my 288 00:12:35.120 --> 00:12:38.320 pet's name, No more of that, got it. But strong 289 00:12:38.360 --> 00:12:40.720 passwords are just the beginning, right, Yeah? What else can 290 00:12:40.759 --> 00:12:42.000 we do to beef up security? 291 00:12:42.200 --> 00:12:45.639 So firewalls are essential. They act as gatekeepers, controlling the 292 00:12:45.639 --> 00:12:47.879 flow of traffic in and out of your server. You 293 00:12:47.919 --> 00:12:51.320 can configure your firewall to block certain ports, restrict access 294 00:12:51.320 --> 00:12:55.159 from specific IP addresses, and even log any suspicious activity. 295 00:12:55.440 --> 00:12:57.720 So we're building a virtual wall around our server with 296 00:12:57.799 --> 00:12:59.679 only certain doors open to the outside world. 297 00:13:00.039 --> 00:13:01.120 That's a good way to think about it. 298 00:13:01.200 --> 00:13:03.519 What about those SSH key files you mentioned earlier, how 299 00:13:03.519 --> 00:13:04.639 do those fit into the picture? 300 00:13:04.759 --> 00:13:07.879 Yeah? So ssh key files offer a much more secure 301 00:13:07.919 --> 00:13:10.919 way to log into your server than just using passwords alone. 302 00:13:11.320 --> 00:13:14.120 They rely on public key cryptography, which is like having 303 00:13:14.159 --> 00:13:17.000 a lock and key system for your server. So you 304 00:13:17.080 --> 00:13:19.600 keep the private key safe on your own computer, and 305 00:13:19.679 --> 00:13:23.240 the server has the matching public key, and only someone 306 00:13:23.279 --> 00:13:25.080 with that private key can unlock the server. 307 00:13:25.360 --> 00:13:28.360 It's like having a personalized access key that's way more 308 00:13:28.399 --> 00:13:30.120 secure than a traditional lock and key. 309 00:13:30.200 --> 00:13:31.120 That's a good analogy. 310 00:13:31.240 --> 00:13:35.600 But even with all these security measures in place, strong passwords, firewalls, 311 00:13:35.960 --> 00:13:39.919 sshkey files. What happens if something goes wrong? What if 312 00:13:39.919 --> 00:13:43.519 my server crashes or I accidentally delete some important files? 313 00:13:43.600 --> 00:13:44.879 Well, that's where backups come in. 314 00:13:45.039 --> 00:13:45.480 Ohka. 315 00:13:45.600 --> 00:13:48.799 Backups are like insurance for your vps. They ensure that 316 00:13:48.840 --> 00:13:51.399 you can recover your data if disaster strikes. 317 00:13:51.480 --> 00:13:54.279 Okay, so backups are non negotiable. Yeah, but what's the 318 00:13:54.320 --> 00:13:56.519 best way to go about backing up a VPS? Do 319 00:13:56.600 --> 00:13:59.559 I need some fancy software or a separate hard drive. 320 00:13:59.799 --> 00:14:02.720 There are different approaches, but a common method is to 321 00:14:02.879 --> 00:14:05.720 use a combination of Linux tools like Tar and g 322 00:14:05.919 --> 00:14:09.240 zip lets. You bundle multiple files and directories into a 323 00:14:09.240 --> 00:14:13.000 single archive file, and then g zip compresses that archive 324 00:14:13.080 --> 00:14:13.960 to save space. 325 00:14:14.200 --> 00:14:16.240 So it's kind of like packing your important belongings into 326 00:14:16.240 --> 00:14:18.639 a suitcase and then using like a vacuum sealer to 327 00:14:18.639 --> 00:14:20.440 shrink it down for easier storage. 328 00:14:20.519 --> 00:14:21.840 I like that analogy a lot. 329 00:14:22.039 --> 00:14:24.840 Okay cool. You can then transfer those compressed archives to 330 00:14:25.080 --> 00:14:28.519 a separate location, like an external hard drive or a 331 00:14:28.519 --> 00:14:32.159 cloud storage service. That way, even if something happens to 332 00:14:32.159 --> 00:14:35.240 your VPS, you'll have a copy of your data safe. 333 00:14:34.960 --> 00:14:36.960 And sound exactly. It's like that just in case. 334 00:14:37.200 --> 00:14:40.000 Got it? Backups are like that emergency kit you keep 335 00:14:40.039 --> 00:14:44.759 in your car, just in case. But even with security 336 00:14:44.879 --> 00:14:48.120 and backups in place, managing a VPS isn't just a 337 00:14:48.120 --> 00:14:51.200 one time setup, right What kind of ongoing maintenance should 338 00:14:51.200 --> 00:14:52.000 we be thinking about? 339 00:14:52.159 --> 00:14:54.799 Yeah, so keeping your software up to date is one 340 00:14:54.840 --> 00:14:58.960 of the most important ongoing tasks. Software updates often include 341 00:14:59.000 --> 00:15:02.919 security patches, I'll protect your server from any newly discovered vulnerabilities, 342 00:15:03.000 --> 00:15:05.600 and they'll also have bug fixes that can improve performance 343 00:15:05.639 --> 00:15:06.360 and stability. 344 00:15:06.720 --> 00:15:09.360 So those update notifications that always seem to pop up 345 00:15:09.360 --> 00:15:12.080 at the worst possible time, they're actually our friends. 346 00:15:12.200 --> 00:15:14.559 They are. They're crucial for keeping your VPS healthy. 347 00:15:14.679 --> 00:15:17.799 Okay, good to know, and thankfully, updating software out of 348 00:15:17.879 --> 00:15:21.039 vps is usually a pretty straightforward process, right it is. 349 00:15:21.240 --> 00:15:23.960 You can use package managers like APT, which is for 350 00:15:24.159 --> 00:15:28.120 Debian based systems, or YUM for CentOS based systems, and 351 00:15:28.200 --> 00:15:30.799 they'll handle downloading and installing the updates for you. 352 00:15:31.279 --> 00:15:33.120 APT and YUM the update curus. 353 00:15:34.159 --> 00:15:34.559 Got it? 354 00:15:35.639 --> 00:15:38.080 But how often should we be checking for updates? Is 355 00:15:38.120 --> 00:15:40.559 it a daily thing, a weekly thing, or just whenever 356 00:15:40.600 --> 00:15:41.240 we remember? 357 00:15:41.480 --> 00:15:43.679 So checking for updates at least once a week is 358 00:15:43.720 --> 00:15:45.879 a good rule of thumb. Okay, and some systems will 359 00:15:45.919 --> 00:15:48.320 even let you configure automatic updates so you don't even 360 00:15:48.360 --> 00:15:49.879 have to worry about doing it manually. 361 00:15:50.120 --> 00:15:52.960 Automatic updates Sign me up for that. It's like having 362 00:15:53.000 --> 00:15:55.399 a self cleaning oven, you know, one less thing to 363 00:15:55.399 --> 00:15:58.080 worry about. But what about those server logs that we 364 00:15:58.120 --> 00:16:01.279 talked about earlier. You mentioned they were important for spotting 365 00:16:01.279 --> 00:16:03.759 potential problems. Can you kind of walk us through what 366 00:16:03.799 --> 00:16:05.240 we should be looking for. Yeah? 367 00:16:05.279 --> 00:16:08.320 So, logs are like your server's diary. They record all 368 00:16:08.360 --> 00:16:12.000 sorts of events, from successful logins and software installations to 369 00:16:12.279 --> 00:16:15.960 errors and warnings. And regularly reviewing your logs can help 370 00:16:16.000 --> 00:16:19.519 you identify suspicious activity. You can troubleshoot problems, and even 371 00:16:19.600 --> 00:16:23.159 anticipate potential issues before they turn into major headaches. 372 00:16:23.639 --> 00:16:26.440 So we're putting on our detective ads and combing through 373 00:16:26.480 --> 00:16:29.960 the server's logs for clues. What kind of red flag 374 00:16:30.000 --> 00:16:31.159 should we be looking out for? 375 00:16:31.360 --> 00:16:33.919 Yeah? So, one of the most important logs to monitor 376 00:16:34.039 --> 00:16:37.559 is the authentication log. It records all log in attempts, 377 00:16:37.600 --> 00:16:40.639 both successful and failed. Yeah, and you want to pay 378 00:16:40.639 --> 00:16:43.399 close attention to any failed log in attempts, especially if 379 00:16:43.399 --> 00:16:46.480 they're coming from unfamiliar IP addresses. That could be a 380 00:16:46.519 --> 00:16:48.759 sign that somebody's trying to brute force their way into 381 00:16:48.759 --> 00:16:49.120 your server. 382 00:16:49.200 --> 00:16:50.799 Oh it's a little unnerving, Yeah, it. 383 00:16:50.759 --> 00:16:53.600 Can be, which is why those strong passwords and those 384 00:16:53.840 --> 00:16:57.440 SSH key files are so important. But beyond security, you'll 385 00:16:57.480 --> 00:17:00.000 also want to keep an eye on logs related to 386 00:17:00.399 --> 00:17:03.919 your web server, database and any other software that you're running. 387 00:17:03.799 --> 00:17:07.039 Right, because if something goes wrong, those logs can provide 388 00:17:07.119 --> 00:17:11.559 valuable insights into what happened and how to fix it. Absolutely, Okay, 389 00:17:11.640 --> 00:17:14.440 I'm feeling much more confident about managing the technical side 390 00:17:14.480 --> 00:17:17.599 of a VPS, but I'm still curious about what I 391 00:17:17.599 --> 00:17:20.400 can actually do with this newfound power. Right, what are 392 00:17:20.400 --> 00:17:23.680 some real world examples of how people are using vps 393 00:17:23.720 --> 00:17:25.920 is to create cool and innovative things. 394 00:17:26.200 --> 00:17:29.559 That's where the real fun begins. The world of open 395 00:17:29.599 --> 00:17:33.359 source software opens up a universe of possibilities, and in 396 00:17:33.400 --> 00:17:36.039 the next part of our deep dive, we'll explore some 397 00:17:36.119 --> 00:17:40.039 incredible open source tools that can transform your VPS from 398 00:17:40.039 --> 00:17:43.039 a simple server into a platform for innovation. 399 00:17:43.279 --> 00:17:45.519 Okay, now you've got me intrigued. I'm ready to see 400 00:17:45.519 --> 00:17:47.480 what this open source magic is all about. 401 00:17:47.880 --> 00:17:51.519