Welcome to the homelab show. Is this episode 32 already? That's amazing. Wow. Yeah, it is episode 32, and 32 is one of those numbers that SIT people we remember. 32, 64, 128, and so on. Oh, yeah. I think we're one of those. Yep. Absolutely. While we're on that topic, it's important that you patch your system, so we decided that we definitely need to have a talk about patching. I've seen some myths. I've seen some unusual things. People have said like, I don't patch my system. I'm afraid it'll break. Linux isn't Windows, and we'll spend 30 seconds in the beginning talking about Windows patch management and what a nightmare it is. But before we do that, we do want to get a little housekeeping all the way and thank a sponsor of this show, and that is Linode. Linode is literally, if you're downloading this, how you got this show, especially because a couple weeks ago, Jay increased the bandwidth on his server because so many people are downloading the show, so that's a great thing to hear that so many of you like it. And many of you signed up for Linode and seen the stats, but it's a great service if you haven't, if you're curious. I mean, it's kind of a no risk. We have an offer code to get you started with Linode. It's a great place to start some of the projects that we've talked about, and it's not just something we recommend, it is something we use. I want to thank Linode for being a sponsor of the show, and let's talk about keeping it patched. That way, if you put something Linode, it's patched. Yeah, absolutely. I think that's one of the first places to start is that some things are more important to patch than others. I mean, obviously you should patch everything, but if you have something behind a firewall that's not exposed to the public internet, it's not as important to patch it as it is something on a cloud provider, or maybe if you've exposed something to the internet, obviously those things are the most important. But one of the things we'll be talking about today, too, is that for human, unfortunately or fortunately, depending on how you look at it, and we often forget things because we have things going on in our lives, and we can't always remember to do the thing, and then sometimes we're reminded we should have done the thing when everything goes downhill. So it's important to keep up. Starting to keep up with it. Now, I said I'd briefly talk about Windows patching. I think listening, because I was able to catch up on the latest Security Now podcast, and I tweeted the other day that Microsoft has done more to get people thinking about paperless offices than any of those little emails that say, hey, don't print this paper because they can't get patching right. So we're not gonna do all much on Windows patching. Basically turn it on, yes, do it, brace for impact every time. It's the thing you have to do that you don't wanna do that'll probably break something and probably has become the mantra for 2021 when it comes to Microsoft patching. There's nothing good about Microsoft patching. I mentioned Steve gets in Security Now, he's ranted about it, bleeping computers, got a collection of articles on how hard it is to keep printers up and running on it. And it's also one of the challenges that you face as IT. It's like Windows is just the beast you rest with. Nothing does amazing patch management, not Windows and not third party software is supposed to manage it for Windows. I see that as an IT professional who's been using and managing Windows service for over 20 years. So it is downhill. But that's the reason the enterprise world runs on things like Linux and BSD. We're gonna keep it a little bit more. Linux focused here, but it just patches better. It's a better system from the ground up than the way Microsoft currently handles their patching system. It's just, it's a lot less broken, but there's still some nuance to it. But I don't, what happens is, and the reason it's important to mention the Windows one is I think there's so much carryover where people have the same fear of things will break when I patch something in Linux because they have that same taste in their mouth from managing Windows servers. And like, oh man, every time I hit update on this, it's something else goes wrong, but that's definitely not the case. Windows is problematic, but Linux is pretty smooth in patching overall. I think so too. Yeah, I mean, there's some edge cases every now and then, but there is with everything. So I mean, there's probably nothing I could say that's ever 100%. But yeah, absolutely. I mean, Windows is kind of weird. It's just one of those things that hasn't really changed all that much. It seems like with Windows Vista, it became orders of magnitude worse. Coming off of Windows XP, Windows 7 was a little bit better, but it kept just being the same, which is kind of like, okay, we're in 2021, shouldn't we do things differently now? Then again, there's quirks in every operating system like that in Linux. As great as it is, has some pros and cons too that we'll be getting into. Yep, but the first thing is important that especially public facing things, and this is where I always have them on unattended updates. We make sure that is completely constantly patched when something is public facing, because well, with very few exceptions, the Apache one was actually interesting because this is a good thing. They found that when there was a recent Apache vulnerability found that people patched really fast. So fast though, that new version of Apache actually had the vulnerability, but it didn't take long for people to find it, mitigate it and patch these subsequent patches. But of course, it took a couple of iterations, but because there's not a patch release cycle, you don't have to wait until next month to do it. These patches pretty much get pushed out as soon as they're available for you to apply for most of the major operating systems. Yep, yep, absolutely. And one of the first things to bring up, I guess is the elephant in the room, which is uptime. We Linux people like to brag at the uptime. You could run the uptime command on any Linux server, tells you how long it's been running since the previous time it was started. And someone might brag, oh, I've been up for two years straight. Well, great, but you've probably had updates sometime in there that you probably needed to reboot. We'll get into why you might need to reboot or not in a minute, but uptime is just one of those things that I think people are obsessed with and don't really understand why. I mean, yeah, it is kind of cool, but at the same time, does it really matter? I mean, if you have to reboot, if it's not going to, I mean, it's not like we're running a business in our house, so I guess I am here, aren't I? But not everyone is doing that. So a little bit of downtime and rebooting isn't really that big of a deal, but going back to your point, yeah, I mean, if it's public-facing, you definitely have to do whatever you have to do to keep it patched. Still no guarantee that it's going to be hack-proof. Actually, there's no such thing as that, but I think the minimum that you could do is keep everything patched. Yeah, and for the most part with Linux, you don't deal with as many rebooting issues. The only time you reboot is the kernel pretty much. I don't think there's really any other thing that's going to cause you to reboot. So it's only when there's new kernel availability and that's not something that's happening on a daily basis versus the patch is a great example because it runs a lot of web servers. So as the Apache one rolled out, you'd run the update and then you just quickly restart the service. Like it would grab, hey, look, here's the new version of Apache now that we're restarted the service. And that is almost unnoticeable to the users. A quick restart of Apache maybe breaks a couple sessions. Generally provided you don't have an ancient system, it takes a long time to restart the service, you have a very minimal amount of disruption when you do that. And this applies to actually most services in Linux. Yeah, exactly. So I think one of the biggest differences between Windows and Linux is that Windows is going to keep bothering you over and over and over again until you give it a restart. That's it. I mean, it's just going to keep bothering you about it. And some versions will try to just pick a time by default to reboot, you could change it but they really want you to reboot. Now, when you update a Linux system, you can very well get a message that says you should reboot your machine but you are free to ignore that. You're free just to not do that. So you can just say, no, thank you, I don't want to reboot because maybe as the Linux administrator for your own systems, you understand when you actually have to reboot because sometimes with a Linux distribution, it's more of a recommendation but if you know exactly what was updated then you can make a more conscious decision as far as whether a reboot is actually necessary before you just go and do it. So if Apache like you were saying is one of the things that was updated, probably not. Could you see a recommendation? Maybe you probably won't see that either but if you do, you could say, no, thanks. I already know that was just Apache. I'm going to restart Apache and we're fine. So you can make that decision up and by yourself as far as whether or not you want to honor that request otherwise Windows will just send someone to your door knocking on your door. You need to restart your computer or whatever they end up doing. Yeah, it certainly pesters you a lot more. It's usually just a suggestion on there and kind of left up to you. Right. So one of the things that I think we should probably get out of the way is what types of situations may or may not require or maybe recommend a reboot. Now you mentioned kernel updates. Now there's a way to avoid reboots with all of this which we'll get into but I think that's a good place to start. With most distributions when you have an updated kernel it's not removing the old one. I mean, some distributions actually do when you install an updated kernel it replaces the kernel that you're running on which is kind of scary to think about but Debian and Ubuntu and many others they install the updated kernel alongside the current one. So that means in order to use the new kernel you have to restart because it's during the boot process that it actually picks the most recent kernel on the list and boosts into that. So just simply having that installed isn't always all you need. Now, if it's a application, a demon or some kind of service that runs like Apache, Nginx generally speaking, you could restart that service and you're fine. Some distributions will restart the service automatically. It kind of depends more on the package and how it's configured. So I remember, I think this is probably still the case when you install an update to MySQL in Ubuntu it restarts with MySQL process. That may not be what you want because your app goes down when that happens. Maybe you'd prefer to just restart it later when you want to but you'll notice that behaves differently depending on the context, the distribution, the package maintainer, things like that but it is often the case when you update a package the service will restart right then and there. And I believe that's all configurable for example in Debian in the unattended upgrades. Yeah, there's a flag for it that you could do which is another topic we'll be talking about that as well. But I feel like you as the administrator you have to watch for that. So if you know there's a critical vulnerability in Nginx and you update the package, you look at the output you noticed it didn't restart the service make a mental note, make sure you restart that service if it restarts automatically, I guess you're fine but just basically gotta keep your eye on the output. I know it's a wall of text but they have a general idea about what exactly happened when you updated. Absolutely. Yep, that's important. So getting into unattended upgrades. Now, in full transparency, I'm not fully aware of how other distributions do it because I'm basically a consequence of what I'm exposed to the most, muscle memory if you will but Debian and Ubuntu is what we're referring to when we say unattended upgrades but other distributions have an equivalent thing that you can use the idea being that it's going to essentially install all the security patches at a given time with Debian and Ubuntu you install the unattended upgrades package and you're pretty much all set although you might want to adjust the configuration. For example, you could put in an email address in the configuration for where the message is being sent to so you have some kind of notification that this happened you could choose which time you want it to reboot or even if you want it to reboot at all you could say, no thank you you don't want it to reboot automatically or you could say, yeah, 2 a.m. a reboot is fine go ahead and restart it you could choose how you want that to be set up and going back to the importance level if it's something that's not internet facing it's probably not a big deal to reboot it manually if it isn't exposed to the internet one could argue a vulnerability chain could still lead to someone getting into that server but that aside, you make that choice if it's not all that important it's not public facing, okay, not a big deal but if you have like a node instance yeah, you probably need to do something about that and make sure that it reboots and one of the ways I like to think about this is that I have some servers that I want to be online 24 seven and some that I don't now I'll talk about later how I solved the 24 seven one but if I don't care if it's down for example something I might use during the day but I'm not using it three in the morning it can reboot that's fine I don't care because I'm sleeping so whatever but if many people are using it such as the learnlinux.tv website I would probably prefer that not go down is basically if I can help it yeah, I do have mindset to automatically apply security updates which I believe is the default still for unattended upgrades so when you install it that's actually the default it's going to just apply the security patches you have to go in there and change it if you want to do more I'm fine with automatically apply security patches because they don't often require anything more than a service restart but I do have it set to restart because the fear I have and this actually applies to even my website I'm fine if it has to reboot in the middle of the day because a hacked website being up is much worse than a minor downtime because my website takes about 25 seconds I think from the time I type reboot until it's completely fully running maybe even less because I got it on one of those really high speed servers so it's like it doesn't take long worst case is there was a 20 second disruption on my website that someone had to experience but if they had to experience someone who defaced my website that may be less pleasant and certainly a more awkward phone call going, hey, you know what your sites got on it now? Yeah, that's never good when that happens so I mean unattended upgrades is like the minimum in my opinion and it's so easy to set up and on my end, I think I've talked about this before where my Proxmox servers shut down at like 12, 30 in midnight and I don't care, right? Because they're down, they're internal they can be down and it saves electricity it's more green that way there is a debate on whether or not it's harmful to servers to have them turn on every day I argue it's fine but for those servers they have unattended upgrades set up not automatic reboot they all shut down anyway at 12, 30 so I just make sure that it's scripted to happen at like 11 p.m. at night so that way when the cron job hits that shuts everything down they've already been updated so when they come up the next day which I have triggered at like 7, 30 in the morning about the time that I'm just getting started for the day then all my servers come back online so since you were updated the night before it's fine, I don't really care and then I handle the internet servers a little bit differently because they are being exposed I have a next cloud server that is now publicly available I have people using it all over the world but just a few people it can reboot it too in the morning so you just basically make up your own mind as far as what should and should not reboot and when and just use your best judgment Yeah, and you can set this up even on your own system but if you're like your desktop but if you're using something like I'm a big PopOS fan in PopOS it prompts you for the updates I just say yes all the time and I've actually because having extra media devices plugged in I've had to write a little script I call boot things and boot things is just all the things that my system does when I log in because I do shut it off pretty much every day I don't just don't leave my computer on when I'm not here at the office so I actually have it running flat pack update and the after get update it's just part of my boot up process so everything's nice and fresh every time I boot it up Yep, that's one way to do it too So one thing I want to touch on I don't want to spend too much time on this because I think this is going to be a little bit overboard although I'm sure there's a certain subset of our audience that are that's probably doing a huge subset of others that likes overboard so let's go there Yeah, but actually maybe I'm yeah, maybe everyone does so the whole idea of like a rolling update system so in cloud we have auto scaling slash auto healing where servers come online and go away to match the load but similarly we also have rolling updates which is probably something more likely to happen in the home lab a good example of that is like a virtualization cluster so let's just say you have I don't know, three hypervisors so you just move all the VMs off of one live migrate, they don't go down so now this server, the host server has no VMs running on it you can update it, reboot it when it comes back move some VMs over to it free up another server update that one, restart it, repeat until each of the three hosts were updated and basically nothing ever went down except for the hosts themselves now, I mean, in the home lab do you care? I don't know, kind of depends, right? Because the worst case, your significant other your kids are watching house on Netflix and or Plex or whatever and all of a sudden it goes down okay, they can resume their show in 15 minutes it's fine obviously at a company it's a lot harder but I think we as home lab people we still would rather not have to restart everything if we can help it because it's a little annoying, to be honest Yeah, for sure Yeah, and I also kind of wonder why are we even rebooting anything in 2021 if you were to ask me like 10 years ago would we still be doing this? I'd be like, no, I doubt it but then again, you know I have a computer mouse in front of me so I didn't think we'd still be using that either but here we are Here we are with some of those things they just haven't, that hasn't changed much Yeah, and the reason why I'm not going to go too deeply into rolling updates is because it really depends on what type of system you have set up whether or not that's easy to do or not I mean, especially when you get into database servers I mean, having like a database cluster becomes a pain and I've done it, you could absolutely do it but do you really wanna go through all that? I mean, personally I don't but maybe someone who enjoys database administration more than I do, maybe they'd be more keen to set that up And with the rolling updates out of the way now we get into the concept of live patching which is really cool Yes, this is really neat the way that this is all engineered, I like this It is, yeah and I think the problem with it is that it's a little confusing to people that are kind of starting out because most things, you know you get an improvement in the Linux kernel and you benefit right away So for example, the AMD sync feature in the monitors I forgot which kernel version came out with that but as soon as it did then everyone who had that monitor that had that feature in there benefited immediately there's nothing to configure, nothing to tweak it's just, okay, new kernel, new feature reboot you got the new feature, great that's kind of what we're used to, right? New features can improve speed and things like that and one of the new features in the past several years I actually forgot what year it was the concept of live patching in the kernel and if you asked me, you know years and years ago if that's something we'd be doing I'd be like, no, that's impossible but it's not because you can do it so the concept of live patching is literally injecting a patch right for a module or whatever right into the kernel as it's running so you don't have to restart for a kernel update you'll still get an updated kernel package that you install via your package managers such that when you reboot it'll be booting into the updated kernel but you'll be able to temporarily postpone those updates or the reboot because it's right there in the kernel injected live which kind of seems like kernel black magic to me but here we are it's a very real possible thing we can do now Yeah, being able to actually modify they've done a lot of engineering to it's kind of cool because it used to be way more monolithic and much harder to compile everything to the kernel and then as they started breaking it apart they solved for a lot of these pain points the way we load modules the way we everything if you remember was a add the kernel module recompile the kernel not just you couldn't just insert a module you spent a lot of time recompiling it and now come all the way here in 2020 we may still be using a mouse and not just doing waste commands for our computers in a fluid way but now we do have the ability to slip that code in and replace or modify the code so it can keep working and of course like on next reboot you're gonna get it without the slip in but that little slip in part like you said that's that kernel black magic stuff that's really cool engineering It really is I think the problem with it why I say it's complicated and not straightforward like most of the features we get is because there's no clear direction for most people how do I go about doing this? So you could download a patch you can put it in the proper directory there's some things you have to do I will get into and you could go ahead and live patch right then and there Now are you really gonna have time to look for these patches find out how to install them it's not the easiest thing to do so what people do instead is they subscribe to a paid service to do this for them so all the common suspects like Red Hat and Ubuntu and the similar enterprise distributions out there they have a paid service that you can use they subscribe to and it'll just go ahead and check for patches and inject those automatically for you so that way you don't have to worry about that and that makes things a lot easier but the problem is if you are using a little bit of SUSE enterprise and maybe like a Red Hat family distro and maybe an Ubuntu server you're potentially paying three different companies for the privilege of live patching which gets a little tedious after a while but full disclaimer they're a sponsor of LearnLinux TV but I really love their service TuxCare makes a product called KernelCare which supports multiple distributions for live patching so you actually can pay one company regardless of which distribution that you're using which I think is a lot better and they're a little bit cheaper too now Canonical has one service that's even cheaper than that which is actually free but only for three machines but if you only have a few Ubuntu servers then this is perfect because you can have like an enterprise level live patch system set up and working for literally no money at all so three Ubuntu servers it's easy you can actually set up live patch there's instructions out there I have a video on it as well that teaches you how to do it I think it's called the Ubuntu Advantage program last time I checked I think it was $5 per machine but the first three machines are free so if you only have a few then I guess in your case then that's great then you're all set you have live patching yeah it's this like feature that they have on there it's been a kind of a weird thing that that's like what these companies have settled on as the upsell but it is also some more complicated engineering to get it to work so I think that's probably why it's not it's still open source it's just that the facilitating tools that do that have the extra fee attached to it right and they're inconsistent too which is another problem because if there's a vulnerability out there that's pretty bad you're hoping that it's gonna be live patched but maybe the vendor doesn't agree with you on the level of importance and that's not one of them that's going to be live patched different companies will do different things one company might be better at it than others I was looking at some documentation before we hit the record button today and right on Red Hat site for this they say this isn't meant to eliminate all reboots we just basically patched the most important things but they don't patch everything and they're very clear about this so they don't want you to think like using their service you won't have to reboot your servers you probably won't but you might still have to whereas SUSA they advertise this mitigates reboot so they're more in on eliminating the reboots than Red Hat is so depending on your distribution of choice it may or may not actually be something you can really rely on you might still find yourself rebooting your server but at least we have the capability of doing this now whereas we of course didn't until recently yeah it's I don't know I should take a look cause I know you've there's sponsored your channel I've not actually tried the TuxCare but it is some kind of interesting to try that out and I'm sure you must have a video reviewing it to kind of show how they do that type of patch management right I do and it's a little old actually I was surprised when I saw just how long they've been a sponsor cause it didn't seem that long and I looked at the video I'm like wow that's my old branding so it needs to be updated there's some new features that are coming out which is why I haven't updated it yet but I will now another thing that they also are able to do I think this is worth a discussion is they're able to patch shared libraries as well because that's another reason why you might need a reboot so for example if you have something running and it's linked against a shared library you know maybe something like SSL that's been patched then you know maybe restarting isn't a service isn't going to work there's might be something else that needs to be restarted it just becomes kind of like this rabbit hole of trying to avoid a reboot at this point and it's not a kernel update at this point but you still might have to reboot I mean technically you don't have to if you could find out exactly how to restart everything that's using the shared libraries but that becomes a pain it's probably easier to reboot but then they have kernel care plus which actually live patches running services as well in particular certain shared libraries you can't say that it's going to patch everything but there's going to be some common shared libraries that they will live patch which eliminates even more reboots which is pretty cool and yeah I like the service quite a bit they're a little cheaper from what I've seen when I first looked at it than the others and they go after multiple distributions basically LTS style distribution so your enterprise Linux Ubuntu LTS they're not going to work with the intermediary releases of Ubuntu for example because they have a life they don't support Arch because they have a life but I mean no offense to Arch users I love Arch I always have at least one installation but it's just one of those things that you can consider I guess what it comes down to in the home lab is it worth the money maybe you could say the money by disrebooting and not pay anyone anything or if you use Ubuntu just use the three servers that you can use and if you only have one server that's facing the internet then you can just put the live patch service from Canonical on that server and maybe that'll just be enough to solve the problem Yeah and I see a question here and this is something you know towards the end here we want to talk about and I guess not as good as times any is when things go wrong when you're patching and I had a mail server that I maintained for years and one thing that did happen was well I had to maintain it for I think eight years and the updates finally did deprecate a few functions you have in the file this is something you kind of have to deal with it's dealt with relatively well for major packages but for minor packages it may not be as dealt with as well so when there's version updates that will deprecate maybe some function that's in the configuration files right you have to address that manually in some of them and there's you just have to kind of be aware it's part of being a Linux system administrator because if this system worked 100% all the time I mean what would me and Jay do? Right yeah there wouldn't be anything to talk about would there? Yeah. It's kind of awkward but you have to kind of look for this and it's very it does a good job of telling you I was able to ignore some errors in PostFix for about I don't know a good year and it would be for it finally wouldn't PostFix wouldn't start because of deprecated function I'm like oh I guess the time's up on the warning of there deprecating this function in future versions the future version is here you just have to keep an eye for it it doesn't seem to happen to often like on major things like Apache, engine acts and those they're relatively it's weird looking at Apache going I've been doing the same format for Apache Comp files for I don't know how many years but a long time and usually though if they have a whole rewrite of a version of the configuration file you'll get a whole update into the version of the software so you'll end up eventually you've been told this has not even supported anymore it is something you have to watch out for but I haven't really seen it come up too often most of the time and I'll use gray log as an example because when they did some bigger version updates part of the update was re-updating the changes and getting rid of things that were deprecated it did automatically for me in the configuration file it says no this isn't used anymore we removed it it just kind of is in the notes and you're like awesome you mitigated it for me and that's just really good coding on the developers part for the people maintaining the software. Third party packages or small one-off projects yeah that's a hodgepodge not all them update fine. Right no that's very true and it is the case I mean sometimes it deprecate things and they change things and you have to redo how you do things and if anyone listening thinks that's annoying to have to redo something because of an update I agree with you it absolutely is but think about it from our perspective when we wake up in the morning and determine that we have to redo an entire tutorial because it's no longer current with the way it is in reality so surprise get recording it's not a fun time for anyone I don't think but it's just a nature of the business we have this happen so it's just one of those things one of the many things that we deal with is these updates and you know what to do about them but getting back to the question what do you do about this? So it really depends on what kind of breakage you're experiencing like you were saying it doesn't happen with Linux very often it's very rare but I have seen it I had an Arch Linux install I know what you're thinking already as soon as I say Arch Linux but this has happened on other distributions as well but I remember this one because I remember how I fixed it where I had this old laptop that was already like three or four generations old by the time I installed Arch on it so usually with Linux older hardware is rock solid unless they deprecate something nobody is really going back and changing too much of the old code unless there's a vulnerability so your old latitude laptop is probably safe but in this case it wasn't so I installed the kernel update rebooted and it wouldn't boot, it was bricked like it just wouldn't start and what I had to do is just get a live CD go into a CHroot environment and I side loaded the previous kernel back into it and then it booted up just fine. And now normally with Ubuntu or Debian and other distributions it's a lot easier to recover because you just select the previous kernel to go ahead and get you started so that way you're not booting into the newly updated one that for whatever reason has a regression so for those distros it's really easy just hit escape at the beginning choose the previous kernel in your set but Arch Linux for example replaces the current kernel with the new one so there's nothing to go back to which is why I always make sure I have two completely unrelated kernel trees installed so I just don't have that capability but that's if it's a kernel update that breaks things if it's a service like Apache and X or whatever you'd probably have to tail the logs as you're restarting the service which of course is going to crash but why did it crash? If you're tailing the log you can see exactly why it crashed and then make a decision as far as what you have to do and honestly it's pretty much down to copy the error message and paste it into Google because nine out of 10 times that'll lead you to the answer. Yeah, the first result will be on Stack Exchange Matter of fact, with PostFix I remember the problem was it didn't even record a Googling it said like line 39 is no longer supported you just could comment it out because it was a deprecated function that was enabled by default and they didn't accept turning it on with the parameter that was used in the previous version it was some type of the way it handled certificates so it was like all that I do is comment that out and it's telling me line 39 I live until line 39, comment out oh look it starts up fine a lot of them each service you just have to go through the logs and we brought this up I think when we were talking about cool Linux tools LNAV is one of my favorites I team up split the screen I LNAV to the log file of the service I'm trying to restart because it'll highlight all the errors in red it'll scroll automatically I have that in there start service see what the error is all right I got the error pulled up down at the bottom of the screen then you go and type VIM and whatever the config file is for that service and away we go I figure out what is it that needed to be changed what needed to be updated what's been deprecated that needs to be fixed to get this service back up and running Yep absolutely now how can you prevent having to go through a lot of work to recover your systems and the answer is obviously using snapshots which depending on your type of server could be very easy to do or not so easy so for example if it's a physical server you aren't going to have the same tooling that you have with a virtual machine a virtual machine you could just go in the GUI hit the snapshot button before you do your update you could just reboot it or whatever you have to do if it doesn't come up something's broke you don't have time to fix it right now you've got to move on with your life you can just restore the snapshot and then you're back to the way it was that's always a great thing to do we also have tools like TimeShift which can be used on Linux it only works on distributions I don't know if they fixed this yet but you have to be running grub which most distributions are it'll still allow you to restore certain things but a full system restore may or may not be possible unless you're using grub there's also like LVM snapshots you could use if it's DFS you could use that but our FS has snapshots as well if all else fails you could take a clonezilla image if it's a physical server and none of those things apply to you so that way you have something to fall back to if the update doesn't go as planned yeah and for me I've really shifted to running all my critical infrastructure as VMs over the years and I mean containers are good as well and there's some stuff where the VM does have maybe Docker inside of it but that just simplifies things quite a bit especially you know you're just doing a new Docker pull for a new image and swapping it out real quick that temporarily goes really fast there's a minimal amount of downtime there and then I'm a big fan of for obviously a lot of you I've talked to a bunch of channel XCPNG and like Jason earlier it will do the rolling pool patch updates to keep the XCPNG server up to date but then all the VMs inside it's just process procedure because even some of our infrastructure is run on Windows you know we just snapshot it load the new version as long as everything's working fine I hold the snapshot for maybe 24 hours to make sure there's no issues purge it and the way we go life is good yep I really love timeshift I think that's something that if it's compatible with your system that everyone should check into you just have to have the extra disk space for all the snapshots and whatnot but it's so easy to use I mean it might take you a few minutes to learn a few things about it like everything else but it's helpful you can restore your entire system if you have to at least you'll have that snapshot if you need it I think that should be the mentality is if you're not snapshotting things somehow let's find a way to snapshot because if nothing else you'll probably really enjoy having that snapshot hopefully you'll never need it but if you do it's great to have it makes it so much faster especially if the problem's a little bit more convoluted especially when there's a dependency like some dependency updated and this has happened sometimes where the line of business application software may not be aware of the dependency that got updated this is one of the big reasons for snapshotting when you have those one-off tools so if a dependency maybe it's got a Java dependency and there's a new version of Java a new version of MongoDB and you have a tool loaded on that system that actually depends on MongoDB well that update may break it and then the problem you run into is the line of business application is not actually ready for the new version so they have to do something so that snapshot lets you hurry up regress back to the previous version like do I really need this version of Mongo just yet you contact the developer of the software and hey you apparently don't work with the latest update to Mongo and they go we will next week so then you just hold off on that patch an extra week but that snapshot is that saving point on there and this is where you get a little bit off because it's the line of business applications and those one-off toolings I'll mention things like Unify controllers and stuff like that your non-standard, your extra packages not your standard Linux packages like an Apache or MySQL those are more mature well integrated into the update process and generally don't give you those kind of problems whether you're running a mail server you have a whole lot of other issues if you're running a mail server but if you're running web servers and you're running WordPress and things like that those problems generally when there's a new version of PHP it's generally not breaking WordPress because it just expects the newest version of PHP and things like that those type of things actually integrate really well together Yeah they really do now I think one question that may come up if it hasn't already is okay but how do I know what vulnerabilities I should be patching against if I only have time to patch a few things right now and I want to just get the most egregious things out of the way I like the tool Linus LYNIS that's really great for doing an audit of your system it's a free tool that you can download they have an enterprise version if you want it but if nothing else you could just add their community repository to get the latest version installed you could run an audit within Linus and it gives you this huge report with oh gosh so much information in that report I actually have a video I'm doing right now that's showing how this works and you could take that report and you understand exactly what the most important concerns are in your case for your server that kind of gives you an action plan as far as what you should target first so if your biggest threat is an Apache vulnerability then you know you have to at least update Apache and make sure that the service gets restarted if there's a kernel vulnerability well you know what to do there so if you're using live patching you can make sure that the live patch tool is actually patching that vulnerability if Linus shows that it's still vulnerable perhaps it is or perhaps it's not but maybe it's better just to reboot it but at least you'll have some idea yes it's a good start to run that tool to figure out what might be hanging out there is it checks some of the configuration files like SSH as well too it's been a little while since I've run it but it kind of gives you a whole list of things you should be doing to lock down your Linux server a little more yep absolutely and that's a whole story of it by itself I mean we do entire episodes and entire videos just on you know individual subjects within that realm so there's a lot to talk about when it comes to security it's never ending conversation yes and it's better to be patched than insecure hopefully that rings true because man I've seen some really old systems and it could brag in about uptime that's how I know you aren't patching things especially if it drives me crazy because it's like no one cares right I mean I think it is kind of cool to an extent but at the same time it's like I'm avoiding best practices aren't you know I'm the coolest thing ever I mean it's cool it's cool if you're running a Commodore I've seen some of those in some long uptime I've seen a few I love when I see some of these articles out there you know someone's still using this old machine and those are cool there's really not I mean they're not connected to the net they're isolated hopefully from the rest of the world so they're kind of novel that they're still on and running for all this time but modern systems especially ones that are internet accessible even if they're not even if you have them behind your firewall and they're more for your private access especially browsers so that in there there's a reason browsers have gone to their own patching systems and having them up to date and are updated in real time because their browser is now the threat surface that you interact with with the greater world so the browser is the way in so to speak so you may be thinking I'm behind the firewall so I'm safe but then I'm like well do you use the internet at all with a browser you need to keep those up to date the latest version of Firefox added a feature to they found basically a hack in Firefox where people were in modifying threat actors not people not just a general public the threat actors were modifying the proxy to stop Firefox from updating to hold back patches that would get them out so Firefox now has a way it can go around the proxy to check for an update to see if you're running an out of date version of Firefox because the war against you know the threat actors and getting in your systems when they know everything else is patched public facing and you're behind a firewall the next thing is the places you interact directly with so yeah the browser from your personal standpoint just to round this whole talk off is absolutely you got to keep the browser up to date all the time that's whatever browser of choice you're using as Firefox or Chrome either one of them keep them patched so one of the reasons I'm always a skeptic before someone says well what about this other browser Tom I'm like how good is their patching that is that scares me so much like I've literally seen browsers that you know I mean people can fork anything they want it's open source so no disrespect intended but a browser is not something somebody should rage for you know someone gets upset with Firefox or Mozilla or whatever because they're you know doing something they don't like oh I'm just going to fork the browser and they do it and maybe they're part of like three people that are updating the browser are they keeping up with CVEs and then the constant counter argument is well it's an open source browser browsing engine so as soon as the libraries get updated it's all automatically fixed which is untrue because they're putting additional Chrome and UI stuff on top of it that could be causing brand new CVEs to happen so I usually squirm when someone you know it says I'm using insert name of browser here that I've never even heard of before and they're doing their online banking and everything on that browser I just have to face palm because I mean you could fork anything you want there's nothing stopping you but please stop forking browsers it's just going to cause problems at the end of the day it is one of those worlds we live in right now where many of them are based on Chromium so the open source Chromium engine and Google is the maintainer for Chromium the open source and then they have Google Chrome based on it Edge is now based on it so it also like Jay says where's that vulnerability found in there and if the vulnerabilities in the Chromium engine great Google updates it Google rebuilds Google Chrome with that updated Chromium engine that's patch but this is where you've seen the diversion so Microsoft Edge puts the Chromium engine but then their own flavor on top of it and they've had vulnerabilities in the essentially the sauce they've added on top of the Chromium their integration so this is that concern that comes into each one of these is even though they may start with a secure engine you think they're getting updates what that covers the engine part provided that they pull from upstream as the upstream updates come in but then you have to worry about the extras they've done on there the leak for a while in Brave browser because I know it's a really popular one out there where Brave mis-implemented the way they were handling the Tor protocol and they were leaking a lot more data than I thought it was just a mis-implementation it wasn't anything malicious but these are the concerns that can come up and there was just a privacy leak less the security issue but it's one of those things it's worth keeping a very well conscious thinking mind about this that's the best thing to do you really got to forefront your mind before you see some random browser going hey this one looks cool so one example of that is this browser I don't know how many people remember this one called Reconq it was for basically a browser made for the Plasma desktop because it was made using the Qt tool kit and you know there's a number of people that thought it was a great browser I mean to be fair it was good I'm not saying any of these browsers are bad from a usability standpoint but it was discontinued in 2014 these browsers generally don't last long it's hard to maintain them and sometimes the developers you know they're human they get tired something changes in their life they have to do something else they can't really spend any time on it or maybe they're not as passionate about it as they used to be or they can't find a maintainer or anyone to adopt it that happens a lot there should be like a website that's a graveyard for browsers because there's quite a few of them out there that came and gone and everyone's like yes this is the best browser ever it's great and then you know year later it doesn't exist yep that's so true all right I think we've patched this whole show up right Jay hopefully you got a better understanding of patching I do have a video called unintended upgrade using unintended upgrades to avoid unintended consequences so it's about this Jay's got some videos on his channel about you know Linux patching and things like that you can check out even if it's an older video he does have one that talks care full disclosure they are a sponsor of Jay's channel not mine but you know either way it's a neat service if you're looking for a service to patch it but those hopefully you got a more well-rounded system and hopefully you don't have any out-of-date systems that you have in place and if you have a Commodore 64 with some crazy uptime please send us a screenshot take a picture of that and tag us on twitter on that I'm a sucker for Commodore 64 I'll end up listing a video on you know going nostalgic on them so I always I'm a sucker for those articles because I played Commodore 64, TRS-80 especially big fan you know the old stuff so Tandy, yes all the nostalgia I don't know if we'll do a nostalgia episode or not this is the homelab show not the homelab but I do have a nostalgia friend we could bring on so an argument can be made for the fact that you know even in homelab we always have this and I know everyone's guilty of this we have this downloads directory somewhere probably on our NAS and it probably has every game that we've ever purchased since like 1995 let's be honest and ISO images of Doom 2 and what not so it might be fun just to kind of talk about running this old software because at the end of the day I mean you may as well have some fun playing Doom 2 on a Raspberry Pi or something it's a lot of fun now we want to go watch the 8-bit guy go live some nostalgia alright thanks everyone for joining us and we'll see you next time thank you


And the president of Benin Solidarity Movement, BSM and former governorship aspirant of Labour Party in Edo State, Comrade Egosa Ubo, has said the arrest of the national chairman of the Labour Party, Julio Sabore, is long overdue that he should have been arrested for a very long time. Comrade Egosa Ubo made these statements in an interview with Benin Correspondents at Pomegera Friday shortly after Ubo was arrested in Benin City, the state capital. Comrade Egosa Ubo said the security agencies should investigate the Labour Party national chairman, Julio Sabore, over corruption and turning the party to his personal property. Julio Sabore supposed to have been arrested in last year, look at the situation where a man that was a tenor, now in less than a year, he has plenty of money that he can now buy houses in Benin, Urumi, Ekboma, Abuja, Lagos, UK, Italy, it should be investigated before Peter became the Shusheki Sakan Balance and after Peter became the Shusheki Sakan Balance so that they will know that they will not ask him how did he marks all this wet that he got. Is he getting wet? Abuja is a disappointment to those people, to those people. He is supposed to be happy that he is the national chairman of a youth oriented party that want to change, a better change for the country. But he is even worse than the people who are criticizing and fighting against the APC and the PDP. The president of Benin Solidarity movement, BSM and former governorship aspirant of Labour Party in Edo State noted that Julio Sabore made him move out of the party over corrupt leadership system that is not favourable to Nigerians. The president of Benin Solidarity and former governorship aspirant of Labour Party in Edo State said more. Julio Sabore is part of the reason I left Labour Party for a court party. I am a man of integrity. Anything I do in life is for a purpose for the good of the society and for the good of the less privileged. I joined Labour Party in 2017-2018 for the simple reason that this party is masses driven and I decided to join them for the betterment of the people. But you see, I have contested election before during the local government election. Julio Sabore betrayed me. Hello, hope you enjoyed the news. Please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


have you ever had a project? And it was one of those projects you're excited about. It was something that you felt like this website was going to be fun to build. So you put your heart, your passion into it. You even go the extra mile and do a whole lot more than what was expected because you really wanted this to be successful for the client and help out their business and also thought that, hey, this one is going to be great for the portfolio. So you put all that work into it, all that care, and then a year later is still full of lore and ipsum text, the same old stock photos, no content, no images, and it just has all the signs that this website was abandoned. Now for a creative creating something to see whatever was created not come to life, it hurts. Even if we get paid, it still does not feel good. What's up everyone? I'm Jeffrey at Lightbox and I love talking about web design and the business behind it. And if you want to stay updated for more web design related content, be sure to hit that subscribe button. All right, in this video, what we're going to talk about is about finding out and trying to see, is your client ready for the website? This way we could prevent a situation where we put in all of our time, our energy, our effort, our care, our passion, all that stuff that we bring to the table on a project and then only to have that website, that project go completely to waste and not be used. And this usually is a diagnosis of a client that is just not ready to fully commit to whatever business that they're going in. Most likely the client might just have a fleeting moment of motivation on the idea that they have and they want to build the website but they're just not there yet, maybe not ready for that business yet. So for the solution to this, there are ways for us to vet a client, for us to diagnose and to take a deep dive and to see are there red flags, are there signs pointing to maybe this client just isn't ready. And if the client isn't ready, we could always steer them inside the right direction and help them along with wherever they're at. So here are five different areas that we could look at and red flags that we could look for. Number one, is your client ready to invest in their website? Now this is usually the biggest indicator. If the client is trying to find something that's just way too low, way too minimal of a cost because they just don't want to spend that money, well there's a chance that they don't believe in their business enough because somebody that is serious about their business, they're ready to go all out. They're ready to do everything possible to make that business succeed. Being a business owner and starting a business isn't like a weekend thing. It is serious work, dedication and commitment. It is six, seven days a week sometimes if that's what it takes. And it is a lot of investing. If they do not see the website as being a valuable investment that they're going to get their return on, then they don't really believe in it most likely and therefore they're going to look for something super cheap and they're going to try to cut corners as much as possible. Now somebody that is serious about their business, they understand they're going to have to invest and they're going to have a set budget. Of course a budget is also limited by what somebody could actually do, but we could look for this. We could look for these signs. Is this someone that is limited by their budget because that's all they have? Or is this someone that just does not want to spend? In red flag number two, does your client have a marketing plan? And if so, what stages are they in? One of the first questions I always ask in initial consultations is what are your marketing plans? What are you planning to do? How do you plan on driving traffic to your site? How do you plan on generating sales? What sales channels are you looking at? So I'm already digging into the marketing plan because that basically tells me where they're at. What I normally see here when I dig into the marketing plan is either three different scenarios. The first scenario could be that the client, they're ready. They're ready to go. They already know what they're going to do for marketing. In fact, they probably already got somebody on the marketing. They might have a digital agency, a marketing agency. They might have somebody for the SEO already and they're already starting to put the pieces together. Another scenario is someone that they know what to do for marketing. They know we'll probably do Instagram, Facebook, we'll probably do some Google ads. They just kind of know what to do, but they haven't started anything yet or they haven't really gone down that path of talking to marketing agencies and setting aside a budget for marketing, et cetera. And then the third scenario is, they don't know. They're like, well, I haven't thought about it yet. And you want to get that. And if somebody says they haven't thought about that yet, that is a huge red flag. That means they haven't even done their homework yet. They haven't even taken the time to really put together a plan and seeing exactly what this is going to take. Now, I'm not saying that it is impossible for someone to start a business because I started a business without knowing anything about marketing, but that was because I was just uneducated. I did not know about marketing and about business. I just went all in on it. So I'm not saying it's impossible. It's just when you get a client that has no idea about where they're going to go with the marketing, got to dig in a little bit deeper and I'll find out, do you have a budget for this? Do you realize it's going to take A, B and C? It's going to cost probably roughly about this much. It might take you this long to get a return on your investment. Start to like dig in a little bit deeper because remember when we're doing the consultations and we're vetting the client and we're trying to see is this client a good fit for us? We're also trying to see how can we help the client as well. Does the client have a business plan? Where do they see themselves in one year or in two years? These are the things I want to also look for when I'm talking with a client in an initial consultation because I want to see have they really done their homework? Do they know what this is going to take? Do they have a vision and a direction to go in? They don't have a direction. It's kind of hard to get a starting point when there's no path that hasn't been established yet. So we want to make sure there is a path that there is a direction and there is a plan. Red flag number four, are they solo or do they have team members? Now again, none of these are dealbreakers right here. These are just red flags that we're looking for. And again, I started my business solo and I'm sure a lot of you watching this are also starting your business as solo. So there's nothing wrong with being a solo preneur or doing anything solo. But if somebody does have a team member, even if it's a virtual assistant, if they have just somebody on their team, that's a great indication that they are ready that they are fully committed.  But if you got someone on your team, if you've hired somebody, you have somebody that you're responsible for, you can't just walk away because that's a huge consequence to let someone down that someone else's livelihood. And red flag number five, are they continuously changing their minds and having new ideas for other businesses? Alright, now this is a big one. This is something to really watch out for. If you're talking to the client and they got this idea for this business or telling you everything about it, and if they happen to slip in that they're also starting other businesses, that's something to, that's something to really look out for. Because I mean, it's one thing, okay, it's one thing if this is a client that has built many businesses, that has many established businesses, because some people are just good at business, that's their skill, they could build businesses. I got clients that they have several businesses, they could build them up no problem. But I've also had clients that have never even built a business and are already trying to build two, three, four, all at the same time without trying to build their first business. Myself, I'm going to use myself as an example, because I started off not knowing about business, which is the main reason why I do this channel, and I focus on the business side of web design. We do tutorials, stuff like that as well. But learning the business side was the last thing that I learned and the most crucial thing that I needed to learn in order for my business to grow. And that took years, it took time, it took dedication, it took perseverance, it took a whole lot of commitment. There's no way I could have started two, three, four businesses. And I've had clients that try to do this. And this is where they abandon their website and whatever project they're on. So you can put in all this time and effort and really care about a project. But if that client is just going to leave it and abandon it, it doesn't feel good. It feels like all that, that wasted effort, all that potential, all that care and passion. And if you're creative and you really care about the work that you do and about the outcomes that come out of it, then this is something you're going to want to try to avoid. Now, if you're new and if you're in your first year, maybe even your second, having these kind of projects is no problem because your first year, your first two years is all about learning and about developing skills and about learning how to look for the red flags, deal with clients and all kinds of stuff. It's just learning. But if you're two, three, four years in, this is the time we need to start avoiding these kind of projects. We want to avoid them because they're not going to help us grow. And here are a few reasons you may want to avoid these. Your work, ideas and passions, they will go to waste. Again, even if we get paid, it doesn't feel good to just watch what we create, never get used. The client will be unresponsive. They could draw out the project, they could delay feedback, they could take time giving content or never give content and assets. And now we step into this huge realm of scope creep. These are the projects are supposed to take three weeks, but end up taking three, six months to complete because the client, they're just not into it anymore. They lost their motivation. They're ready to walk away. They're ready to cut their losses. And we still got to get paid. So we're trying to push the project to be completed. And this is where a project could go way off track and could really take up your time. But if you're new, practice, get the projects that you can get all the experience that you can.  See, hey, are they a good fit? Are they serious? Is this a business that's going to go somewhere? It's a great feeling when you work with a client and you build that long-term relationship and you see their business start to grow. And then you also see that your contribution actually helps that business grow. That is a huge boost to self-esteem. It makes me love doing what I do. It makes me feel important. It makes me feel valid. But when the website goes away, it doesn't feel good. And maybe I'm just overly sensitive and I have to admit I'm a super sensitive guy. But hey, maybe you're sensitive too. I don't know. Well, anyways, I hope this video helped out. And I'll be back again soon with more web design related content. So make sure to subscribe. Do all that good YouTube stuff. It really does help. It's much appreciated. Thank you.


the final in the Bronx Red Sox winning it four to three. We've heard the term the agony of defeat mentioned a lot of times in the history of sports and you look at this one as the Yankees rallied with two in the ninth but they came up just short. Well they came up just short that an amazing season but this series comes down to the fact that they scored four runs in two games at Yankee Stadium and you got to say they scored two runs in the bottom of the ninth because Kimbrell was all over the place and tried to give it to them. They battled to the end but at the end it's going to be disappointing because the bats really didn't show up. Some questionable moves by Aaron Boone in this series. Alex Cora had a great series going all in with Salem Kimbrell at the end. Yeah pulsating finish for the Yankees as you said they get a couple of runs in the ninth inning they give their fans one last gasp of hope but in the end they lose two games at home and as you said John only four runs. This is a team that set the all-time home run record. They did not hit a home run in the last two games at home. They dominated at home this year. Second best record in the major leagues but the Red Sox thoroughly outplayed them and John you hinted at it. A lot of the questions about tonight's game will be Aaron Boone staying with Cece Sabathia too long.  Boone himself talked about how you have to have someone ready at a moment's notice and Boone did not do that when Cece had trouble in the third inning. It was a few batters too late to finally replace. Yeah we're waiting for that sense of urgency right. Ben attendee gets hit and we're all watching it saying who's warming up in the bullpen and it just happened late. Aaron Boone seemed like he was a little late and then on the flip side Alex Cora gets five out of Porcelo and he goes to the bullpen and get some good outings from some guys who have been a little shaky.  Kimbrell obviously is shaky but he gets a job done but I thought Aaron Boone in this game we talked about going to your guys early. You got to have a sense of urgency. I thought a little bit late with Sabathia in there and he gave up some runs in the third and give a little context to it. John mentioned Ben attendee getting hit. When he got hit by a pitch that was the fifth base runner against Cece in the first eleven batters. There was a lot of traffic on the basis so it wasn't as if Cece had earned a longer leash at that point and it never hurts to get somebody up. Cece could have gotten a double play ground ball right there and you have the reliever sit down but he did not get David Robertson up until there were two outs in the inning and the Red Sox had a one to nothing lead. Robertson wasn't ready. Two guys the next two hitters come through with run scoring hits against Cece and suddenly one nothing is three nothing and the way the Yankee offense was performing it felt like a lot larger than three nothing. It makes me think of what you said prior to game three and that's what you thought he would manage it like a wildcard game. So if that's the case you get some traffic on the basis it's a one nothing game.  As Jack said just have him ready to go have the option if you want to go to him. Everything developed really really slowly for Aaron Boone getting his bullpen guys ready. It got away from Sabatia a little bit and you just felt like you said with the way the Yankees have been swinging the bats the last two days that three run deficit was huge at the beginning of the game.


Ladies and gentlemen, I am back once again with another video for all you lovely people out there in the internet space universe. Today, today, we have something very special that we haven't done yet. This will be the first video doing it. We're going to be doing an overview of our past performances in the Bitcoin Daily VIP Group. Okay, this is going to be something new that we're going to be putting out there because a lot of people have been asking for, I guess, for more transparency. And they want to see what type of results we've been getting in the VIP Group. It is a paid group. If you guys are interested, send me a message so I can send you the link and get you set up. If not, it's cool. You don't have to be in it. We have our free telegram group. These are just for the people who want all the trades that I'm personally making. As you know, I'm more of a day trader and swing trader basically. So I do a lot of day trades and a lot of swing trades. I try not to hold onto too many points for too long. I try to just get profit and keep on moving forward. I trade based on technical analysis. I don't trade based on fundamentals. Fundamentals, they're not statistics. I feel like you can't base your trade off of those because they're just kind of made-up scenarios in your head that you're trying to... So I don't trade based on fundamentals. I trade solely based on statistics and technical analysis. So I started tracking this in April. I wish I would have started earlier, but I started in April. And I know that in March and February, the market was down. So it probably wasn't very good months either way. But I know that I wish I would know the exact numbers on them. And I've posted so many things in the group. It will take me hours to scroll all the way back and write them all down one by one and all that. And I just don't have the time for it. So I started tracking this in April. And we have two months now. Today is June 7th. So we just started the third month of this. And I won't be showing you guys the trades that we're making so far in this month because as you can see, we have a lot of open trades still. But I'll show you from the previous two months. So I hope this gives you guys a really good view of what we're doing and what we do in the Bitcoin daily VIP group. I hope it opens up your eyes a little bit to what we're doing. And if any of you are interested, as you know, just let me know. So let's start with April. April, let me tell you guys was a phenomenal, phenomenal, phenomenal month for us. April was the month that Bitcoin did have a great bounce back. A lot of outcoins just had crazy bumps during that month. As you can see here, we only made 10 trades in April, just so you guys can see that. I'm not sure what the average is. I think the average is probably in the 20s, the 30s, trades a month. But for some reason in April, since we just came off these two really down months, I was trying to be very picky with the positions and the trade setups that I was choosing and just trying to choose the highest probability trades possible because I needed a win for my guys in the group. So I got you guys a win and I'm going to go over it. So as you can see, April, we made 10 trades and we won 10 trades. 100% winners, 0% losers. The total profit loss was, if you add them all up together, was 547.55% profit. And the average profit loss percentage per trade was 54.75%. Just let that sink in for a little bit. 54% profit was an average trade during this time in April. So let's go ahead and go to April. Let's go through the trades. Let's check them out. All right, so it was pretty straightforward. As you can see this chart here, this is open close, the date that we made the trades, the date that we closed it. I'm supposed to put the time here, but I don't need to keep track of the exact times, so I didn't put them in. Long or short, so if we had a long position or a short position, I didn't start it yet, but I'm supposed to put the coin here. So the first point was Corey. So on April 1st, we made a trade for Corey, long position, at .00029. And this, we ended up selling this at .00048. So you can see that we made a 65.62% profit. This trade closed on April 28th, so it was about a three-week trade, a three-week hold on this one. Yeah, that was actually the high, well, it went a little bit higher. And I personally trail with the stop loss. And sometimes I do take profits in between, but the final thing overall was 65%. Corey, so you can see that was a win. And you'll see as I show you more and more trades, my gathering of the numbers got a little bit better. Because see here, I didn't put the stop loss. I didn't enter the target here, the targets, I just put the final target. All right, so let's go to the second one, also from April 1st and closed out on April 23rd. This was a long position on XZC. Let me write it here. So we took a long position on the first at .0044. And we ended up, let's see, okay, so here the target was .0085, which was a profit potential of 93%. We landed short of that, but we still took home a nice 18.18% profit on this one. So that was the one on the first that we closed on the 23rd, so we held that one for about three weeks. Our third trade was on April 2nd, and this one was also a long, all these were longs. This one was XRP for Ripple, and we came in at, okay, so this one was USD. So that's why it's a little bit confusing here, is that I couldn't get it to switch to USD and then switch to BTC as well. So it'll just look like that, but you'll notice here it says USD on these. But we got in at 50 cents, and we sold at 90 cents. So we ended up getting a total profit of 80%. You'll see here our target was actually 68 cents. So I sold some here, and then I held the rest until it got to the top, which I sold at 90%. I mean at 90 cents. So total profit was 80% profit on that trade. April 3rd, and this one we actually closed on May 3rd. So this one was a month-long hold, hold on a second, I'm adjusting. So April 3rd, let me put it here again. What was it, Ethereum? We picked up Ethereum, we went long on it at 404, and as you know, it went up pretty high. Our target price was actually 446, which would have been a 10% profit. But I didn't even sell it at 446. I took maybe 10% off over 446 when it was in the 500s, and then I held the rest. And it went all the way up to 800 is where we ended up selling for 98% profit. 98% profit in one month. What could 98% profit do to your bankroll, to your portfolio on one trade in one month? Think about it for a little bit. Alright, the next one, April 10th, and I actually didn't write the closing date on this one. But April 10th, we went long on, we go long on, oh, on D-Trash, I mean, D-Cash. D-Cash, we bought on April 10th. So this was before that huge jump at 0.095 BTC, and we ended up selling at 0.16 BTC. So not only was that a 68% profit, but due to the math on where BTC was, on April 10th, on BTC's price, and where it was when we sold, I'm not sure when we sold, sometime towards the end of April, but just checked the price, and it would be about 100% on this property. So I didn't even include that in there. But remember that when you're trading pairs versus BTC, whatever BTC's price goes up, the value in USD goes up as well. So in Bitcoin terms versus Bitcoin, it went up 68%, but its value overall in USD was over 100%. Alright, the next one, April 10th as well, long position on, let me write it over here, A-D-A. Alright, so on A-D-A, we bought in at 0.00026. Our target was 5K, but we made it out at 4027. I'm not going to say all those other zeros again, that's too many zeros. So 4027's where we stopped out at with a trailing stop for a 54.88% profit on that trade, and that one we closed out on May 1st, so it was about a three week hold as well. The next trade didn't come until the 16th. I think I was just enjoying the profits so much that I was like, let's just ride these out. On the 16th, we went long on Nano, and we bought in at 0.0007. We got out at 0.001, that was a 42% profit. Yes, sir. Wow, that was a really low stop loss. I think that's a mistake. I don't think I would risk 28% loss. I definitely never do that. But like I said, this was the first month when I first started, so I was still like confused on some of the stuff. To be honest, I wasn't filling it out completely. All right, so now the 21st, the next trade, or the last trade, the Nano one, we closed it out on May 3rd. So that was about three weeks as well. The next one on the 21st, this one was actually a seven day trade, so one week. This one was for ICX, boom, ICX BTC. We bought in at 0.004, and we sold that 0.005 for a 25% profit. That one was super simple. That was a seven day trade. One week, 25% profit, not bad. Next one, on the 21st as well, so that day I was on it, I was on point. We put it here, we went with Tron, TRX. We bought in at 600, and we sold that 1,000 on the first. So that was about two weeks. For a 66.67% profit. So another great win, and then the last trade of the month on April 27th. This one was a two day trade actually. I am blocking the name of this trade. RPX. So this one was RPX, RPX. Oh, whoops, I wrote it in the wrong place, my bad. RPX. I need to leave this one before it confuses me. RPX BTC, we got in at 12.50. We got out at 1600 for a 28% profit. So that was a two day, in two days we got 20%, not too shabby. So that was our April. We only made, in April we only made 10 trades. We hit all 10 trades for an average profit of 54.75%. So now let's go on to May. Now you're going to look at May and be like, wow, that was a terrible month, right? May, we made 21 trades, actually 27. Yeah, 27 trades, because we have six that are still open right now apparently. The number of winning trades was eight, and the number of losing trades was 13. So I'm sure you're saying to yourself, wow, what the fuck? How do you go from 100% accuracy to 38% accuracy? Guys, like I said, I am here to be super transparent. I want you guys to see what we do and how we handle even losing months. You guys are going to see the good and the bad during this series. So I want this, this is going to be a unique experience. So I'm pretty excited about this. So let's talk about it. Let's talk about it. So eight wins, 13 losses, but remember I still got six open ones. So if I hit all six of these, then we're going to be okay. We're going to be over 50%, which I expect to happen. But right now, let's forget about those six. Let's just say that we have 21 trades. Forget about the six that are still open. In 21 trades, we only hit eight of them and we're wrong on 13 of them. So 38%, right? Now check this out though. Even though we were wrong, 61.9% of the time, the total profit loss of May is 63.69%. And the average profit loss percentage per trade is still plus 3.03%. So we still made a profit in May. I just want you guys to see that. You're still profitable in May, even with a 38% accuracy. And if these six hit, this is going to shoot up over 50%. And this is the total profit loss and the average profit loss per trade is going to shoot up. And we'll have, it's a winning month. It's still, even though we only hit 38% of our trades, we still got a winning month. We're in profit 3%. Now let's take a look at what went wrong. All right, so as you can see here, there's a lot of Ls. Yep, we caught a lot of Ls during this month, but we warned the important ones. And this is one of the things that I preach about in my new course that I'm working on, about how to be a profitable trader, how to take proper risk management, and how to minimize your losses and maximize your winners. So the first trade that we took here was May 3rd, XRP, we bought at 87. Ended up selling at 81 for a minus 6.9%. We're trying, our target was 1.15, a dollar and 15 cents. So we completely missed that, but we only took a 6.9% loss and we stopped out. We cut that short. The next one on the fourth was IOTA. We bought at $2 and we sold at $1.87 for 6.5% loss. So two losses in a row. Notice both losses are pretty small. The third one, May 6th, EOS, we bought at 16. After it dropped from 26 down to 16, we thought, wow, this is a great price. Let's see if it hangs on, but nope, it kept dropping and we got out at $14.50 for a negative 9.38% loss. Next one, and notice all of these are pretty short trades. Four days, this one was a little bit longer, 13 days, two weeks, this one was four days, so these dropped on us really quick. Tron, this was a winner. It was a winner, got on the fifth, sold on the 25th. We got in at 900, sold at 1,000 for 11.11%. Our target was 31, didn't quite reach it, but we're happy with taking our 11. And I think that was the final target. There were targets in between. I wasn't just aiming for one straight shot to 244% profit. But yeah, and I'm sure I wasn't aiming for 22 loss potential either. But we did win this one. So that was our first win of the month. On the ninth, we took XMR at 220 USD. And we stopped out at 215 USD for a 2.2% loss. So we kept a tight stop on that one. And that's because everything was kind of going down, wanted to keep it kind of tight. Next one is on the 10th, we did bat, got in at 4,000, and we sold at 4,300 for a 7.5% win. And that trade took one week. Notice XMR, we sold, we got off the same day. Yeah, this one was one week, and one week we made 7.5%. Next one on the 10th, Neo, we bought in at $70, but we never sold. And I should have sold. I'm sure people in my chat probably did sell, but I never sold. And the reason why was because I made a mistake, and I didn't set the stop loss correctly. So I had slippage, and it didn't end up selling. By the time I noticed, it was under $60. And I was like, you know, how much further can it go, really? And then it dropped to $45. So that's why you sell, that's why you set a stop loss. Once it got to $45, I was like, I'm at $45, how much lower can it go? And thank God it stopped going that low. So I'm still holding on to that. I've actually took a new position on that, and I'll get to that one. So the next one, so that's a lesson. See, even I make mistakes, man. It's normal. So the Neil Hoddling, May 11th. We went long on XVG at 757. We got out at 670, 11% loss. The 16th, Doge at 50. We got out at 48, 4% loss. On the 16th, NXS, this kind of was saved our month, really. We got in at 24, and we sold at 35 for a 45% profit. So that was huge. But see, now do you guys understand the part of, you know, taking, it's okay to take losses as long as there's small losses. And then when your winners hit, they're going to hit, you know, so you're kind of swinging for the fence. So it's fine. You're going to strike out a lot as long as they're small though. It doesn't matter because what's going to matter at the end is when you hit the big one. So it's, that's why sometimes I make so many trades because I rather take minimal, a lot of small losses than miss out on a big trend on a big upswing. So, you know, it's a numbers game. As long as you take proper risk management, you'll be fine. Next one on the 18th, with BCN, we got in at 100, sold at 90 for a 10% loss. ADA on the 18th, this one's actually still open, got in at 3,000 and we're still holding that currently. I'm not sure exactly what's at right now. I think it's at 27. But I am still holding. This is another one that I did not set a stop loss on. I should have probably set it around 28, 27, but you know, it's still running.  I didn't set a stop loss at 27, but it never triggered. So I'm still holding. Cool. So yeah, so that would have been a 10% loss if I sold it, but it's not. It's still an open position. So even though I'm down from where I bought since the trade's not closed, it, you know, it doesn't count. On the 18th, again, ICX bought in at 43, sold at 40 for a 76.98% loss. That was a 3-day trade on the 19th. Got then at 50, sold at 46 for a 8% loss on the 20th. Got in at on Elf 15-5, like a fly or something. Sold at 15 for a 3.23% loss. BCN took another 10% loss on BCN. BCN got me twice. This is one of my 22nd. BCN got me twice on Zcash. We're still holding our position on Zcash. This is from the 23rd. So this is about two weeks ago. We're still holding our position because it never hit our stop, which was at 6%. It never hit. So we're still holding Bitcoin. What do we do here on Bitcoin? Okay. So Bitcoin, this one was a leveraged trade, actually. I don't have it here with leverage, two times leveraged, 2x leveraged long trade. We got in at 7380. Got out at 7610 for a profit of 3.2 times 2. So that'll be 6.24% profit. Something like that. So it's actually more than what it says here. We made 6% profit on this one. Thinking. I don't know if my numbers are right on that. I think it might have been higher. I think it's, I think it's like a 9%. I don't know, whatever. Anyways, on the 26th, we got in on salt at 25300. We're still holding. It never hit our stop. So our stop was set to 3.5%. Hasn't hit. So we're still holding that. Zcash got in on the 26th for 275. We stopped out right away for 267, which was awesome because we only lost basically 3% on that trade. And look at where Zcash is at now. It dropped, huge drop. So that's why you need to minimize your losses. Wabi, on the 27th, we got in. This one we just actually got out of recently for a 31.25% profit. And this is within what? Like a week? Within a week. We hit a 31% profit on this one. Our target was 100% though. So I was kind of sad. This was our final profit, our final target. So I did have targets in between. On the 28th meme, we got in at 2000, and we're still currently holding. It never hit our stop. I'm not sure what the stop is, but it's, I believe it's still around the same price range, I think. But it hasn't hit our target or our stop. So we're still holding that. Neo, we got in. So I remember I told you I took a new position on Neo. So I bought in at 47. This is a trade that I posted in the VIP. And we sold at 56 for a 19.15% profit. We closed that out on the first. And I'm actually waiting and looking for a new position on Neo. Did I buy back? I don't know if I bought back in yet or not. ADA on the 30th got in at, so don't mind the price. It's like .000, all the zeros and then 2738 at the end. I just wrote it like this for some reason. And we actually made a profit of 7.74% on this one. So that one was cool. As you can see the end of May, we got a lot more winners. So let's look at the last 10 trades if possible. One, one, two, three, four, five, six, seven. So seven and then one, two, three. So we won seven and lost two, right, eight. I'm sorry, I'm confused. One, two, three, four, five. One, five, lost two. So five, two, and then we have three that are open. So our last trades are actually good, pretty good. As you can see, the month started turning a bit and giving us some, you know, finding the bottom and reversing a little bit, giving us a nice bounce. Even though on 31st we shorted, so that's why we lost, we shorted BTC at 75.30. I think at 2X leverage as well. And it went up to 76. So we got stops at 93, basically 1%. Times two, so we lost about 2% on that. And the last trade that we made in May, the 31st, Zillica, Zill, 1425, got out at 1718 for a 20% profit. So as you can see guys, I am super tired of talking. That was really long. But yeah, that's been the recap of the last two months. In July, I will do a recap of this month. As you can see right now, we've had four trades closed. So far, we've won two, we've lost two. And we currently have 20 open trades. That's right. The first week of June, we're already up to 20 open trades. Six of those trades though, I believe are still from May. So we have 14 open trades, 14 trades plus the four. We have 18 trades total in June so far. So yeah guys, if you guys are interested in the Bitcoin Daily VIP, send me a message. I will give you the instructions, the price and all that other fun stuff. I will be doing these regularly on a monthly basis, updating you guys, keeping you guys up to date on exactly how we're doing in the Bitcoin VIP group just so you guys can have the inside scoop on it. I want to show you guys the transparency and I want you guys to see what's going on. I want you guys to see the winners and the losers, the joy and the pain. And I want to see, I want you guys to see how you can profit no matter what the market conditions are. There's always ways to profit with proper risk management and minimizing your losses and maximizing the profits. That's basically it, man. I am out of here. I'll be posting this probably today in the morning or tomorrow or whatever. Guys, follow me on Instagram, Bitcoin.Daily. We are the biggest community page for Bitcoin on Instagram. Any other page that you see with more followers than us, they bought their followers and they're offage and you can tell easily just by going to your pictures, looking at how many likes they have and what their engagement is, how many comments they have. A lot of times you'll see that they have 100,000 followers and 40 likes on the picture or you'll see that they have 100,000 followers and 5,000 likes with two comments on the picture. Or sometimes they get the whole package, they buy 100,000 followers, they buy the 5,000 likes and they buy 100 comments of just spam though. I'm not sure why, but yeah. I do get a lot of spam comments in mine as well and the reason why, if anyone ever wonders, is because I use the hash tags and people target the hash tags, people with bots target the hash tags and they leave automatic comments.  There's a lot of bots out there guys. Don't be fooled. Bitcoin Daily is the real deal. I'm out guys. Till the next one. Peace.