If you want to be safe, then clean install is the way to go. Sure you can try to uninstall chipset drivers but your PC will probably work (or have issues) regardless.
I thought I could get away without doing a fresh install, and it worked mostly fine until I found out just how badly corrupted it had become and had to do a fresh install anyway.
Works fine now, but I really could have saved upwards of 8 hours if I had just done a clean install from the beginning.
I've done it without reinstalling windows, but sooner or later I did a complete reinstall.
It is always best to go with fresh installation with hardware updates on those occasions. It seems there are a quite a few difference that makes windows unstable.
I've done it without reinstalling windows, but sooner or later I did a complete reinstall.
It is always best to go with fresh installation with hardware updates on those occasions. It seems there are a quite a few difference that makes windows unstable.
That code means that the previous Windows installation has not yet been completed. It's failing to install whatever you're trying to give it because the updater instance in already running.
I recommend force closing everything that has anything to do with updating in TaskManager and disabling auto updates.. Then, restart.. See if anything tries to update, some stuff usually does.
The point is - kill off any running updater instances and then try to initiate updates from the WindowsUpdate window.
I had a bug on my laptop (Dell XPS 9700) that caused it to fail updating after a certain point and I had to reinstall Windows. It would fail to install the update and consequently fail to boot. Then it would boot loop itself into oblivion and I'd have to manually recover the previous stable instance of Windows.. Idk if you have issues of that sort. But if you can't get the Windows to update the easy way, you reinstall it from disc while keeping all data and it'll update itself during installation.
As @LIGISTX mentioned, you shouldn't need to transcode at all. If all your media is 1080 and all your clients are 1080 capable, just set the clients to play original quality and it'll keep transcoding to a minimum.
The Qnap will be able to do some transcoding, probably one 1080 to 720, but not much more.
Here is a write up on the Qnap TS-233 you mentioned:
QNAP TS-233 Plex Media Server NAS Tests – NAS Compares
If it’s local, why do you need to transcode at all?
Streaming using direct play (not actually transcoding anything) can work on a potato. It takes effectively no resources from the machine. Transcoding is when you need to change the codec or change the quality, which is what takes actual power. If your planing to mostly use this for local playback within your home, don’t transcode at all… make sure you have media that can be played by whatever player you intend to play it on.
We've finally got our website live! Check it out at https://lmg.gg/ltx2023
You'll find general information about the event, different ticket tiers, office tours, WHALE LAN, as well as some booths that we currently have planned. We'll be adding things as they're confirmed, so stay tuned for regular updates on the WAN Show, as well as on here and through social.
If you're an LTX 2020 VIP ticket holder, you’ll be contacted by our team before tickets go live at the same email you used to purchase your 2020 ticket. If you're a member or the media or are a content creator, please email us at partner@ltxexpo.com.
If you'd like to volunteer, please sign up at https://lmg.gg/ltxvolunteer.
Follow us on social at:
https://twitter.com/ltxexpo
https://www.instagram.com/ltxexpo/
https://www.facebook.com/LTXexpo
Let us know if you have any questions or concerns, we look forward to seeing you there! @Chase Douglas @SCaldera @STERPH
This is an accompanying guide for our recent video (currently on Floatplane) where we setup a DIY VPN server using Pritunl.
Note: Image links will be coloured like this: https://google.ca (I still need to finish this, was posting at the end of the day and ran out of time D:)
Parts List:
A credit card or PayPal account to rent a server with
That's it - unless you intend to install Pritunl locally in which case you will need a system or VM to install CentOS onto
Stage 1 - VPS Install, Firewall, and Setup (before the video tutorial section):
Before you can do any installing, you must deploy a VPS from your chosen provider. For the purposes of this tutorial we will be using Vultr.com (LMG affiliate link), specifically their $3.50/month 1 core, 512MB of memory, 500GB of bandwidth plan (note: this plan is only available at their New York/New Jersey data center).
Create an account at Vultr or your chosen VPS provider.
Deploy a VPS at your desired tier and location, choosing Centos 7 as your operating system (it appears Pritunl does not yet support CentOS 8, although this may change). This is one of the lightest-weight mainstream operating systems that Pritunl is compatible with right out of the box.
Wait a few minutes for the VPS to deploy and start up - you should get an email once it is ready.
Once the VPS is running and ready, you'll need to get an SSH client so we can SSH into the VPS to setup the Pritunl VPN server.
Download, install and then launch the SSH client of your choice. We will be using PuTTY because it's simple, but any SSH client will do: https://lmg.gg/8KVmQ (https://i.imgur.com/POLV3i4.png)
Copy the IP address assigned to your VPS into PuTTY, and click "Open" (https://i.imgur.com/PKYfvD2.png). You can find this in your VPS provider's control panel (https://i.imgur.com/z4To3uM.png).
You may be prompted about a "PuTTY Security Alert" with a message about the host key not being cached, this is normal, click Yes (https://i.imgur.com/RRMqhMI.png).
After it prompts you with "login as:" enter 'root'
Then for password, copy and paste (paste in PuTTY by right clicking with your mouse) in the password supplied in your VPS provider's control panel (https://i.imgur.com/JwQxXHZ.png). You should now be logged in over SSH.
Update the server and setup automatic security updates
Quickly update the server by running 'yum update -y' (https://i.imgur.com/f7uWUge.png)
**OPTIONAL BUT RECOMMENDED**: Setup automatic security updates on your VPS: https://www.howtoforge.com/tutorial/how-to-setup-automatic-security-updates-on-centos-7/
Now that you're SSH'd into the server, while technically optional, we highly recommend setting up some basic security including: changing your root password, setting up a sudo user and blocking root from SSH login, and setting up a firewall.
At a bare minimum, you should change the supplied root password. This was provided to you in plain text through your provider's web panel and should be considered insecure until it is changed:
Enter 'passwd' in PuTTY and hit enter. Input and then confirm your desired new password (https://i.imgur.com/unLgve8.png).
Setup a firewall either in OS, or via the control panel of your VPS provider. We will be using the one supplied by Vultr.
On the Vultr.com website, under Products>Firewall click the "Add Firewall Group" button (https://i.imgur.com/plIIpKJ.png) and set the description to something related to VPN so you remember what it is for (ie. "VPN Firewall")
Create a firewall rule to allow SSH connections to the VPS (https://i.imgur.com/oxtHuHw.png).
Protocol: SSH
Port: 22
Source: My IP (or you can set this to Anywhere, but this will allow anyone to attempt to login to your server)
Create a firewall rule for the VPN server IP (https://i.imgur.com/R67XT7E.png).
Protocol: UDP
Port: 1337 (or whatever you decide to use as your VPN port)
Source: Anywhere (or you can define a specific IP range if you want to limit access to your VPN to only that range)
Create a firewall rule to allow HTTPS connections to the VPN web panel (https://i.imgur.com/WyRmpSC.png).
Protocol: HTTPS
Port: 443
Source: Anywhere (or you can define a specific IP range if you want to limit access to your VPN web panel to only that range)
Create a firewall rule to allow HTTP connections to the VPN web panel for LetsEncrypt SSL, if you want to specify a custom domain (https://i.imgur.com/SXuJuXH.png).
Protocol: HTTP
Port: 80
Source: Anywhere
Then, you must attach the Firewall Group to the VPS for it to take affect.
On the Vultr.com website, under Products>Instances>Cloud Instance (the VPS you rented for this)>Settings>Firewall select the Firewall Group we created earlier, with the description you assigned yourself (https://i.imgur.com/FUc91Xw.png).
Click "Update Firewall Group" to apply the changes (https://i.imgur.com/9eHNUio.png).
Setup a sudo user by creating a new user, setting the users password, and then adding the user to the sudo user group. This new user with only have access to commands that affect it's own user directory (not the rest of the system or other users), unless they prefix commands with 'sudo' (essentially running the command as root), which has password verification. For this to be at all beneficial we must also restrict root from logging in via SSH.
Run 'useradd <USERNAME>', replacing '<USERNAME>' with your desired user name (https://i.imgur.com/ziPXvm9.png).
Run 'passwd <USERNAME>' replacing '<USERNAME>' with the username of the user you just created (https://i.imgur.com/76nomeh.png).
Run 'usermod -aG wheel <USERNAME>' replacing '<USERNAME>' with the username of the user you just created (https://i.imgur.com/60lrNyY.png).
Run 'nano /etc/ssh/sshd_config' and change the "PermitRootLogin yes" line to "PermitRootLogin no". This will prevent root login over SSH (https://i.imgur.com/aJzoFvh.png).
Use 'Ctrl+X', the 'Y' key, and then the 'Enter' key to close the nano text editor and save changes.
Run 'systemctl restart sshd' to apply the above change (https://i.imgur.com/cOkWVJX.png).
Close PuTTY, so you can re-login with your sudo user.
Re-Login to SSH on PuTTY with your newly created sudo user by following steps 2.2 to 2.5, replacing "root" with whatever username you chose for your sudo user.
If you're using your VPS provider's firewall like we did in this tutorial, you will need to disable the CentOS firewall as it will block the VPN's web panel from being accessed. If you plan on using the OS based firewall, we are assuming you know how to configure that yourself.
Run 'sudo systemctl disable firewalld' (https://i.imgur.com/6GLlgME.png).
Run 'sudo systemctl stop firewalld' (https://i.imgur.com/5TOJyZp.png).
Run 'sudo systemctl status firewalld'. This should show the status as "inactive (dead)" (https://i.imgur.com/kTGqsw7.png).
Use 'Ctrl+C' to exit this view.
Bam, your OS is now secured, auto security updating, and ready to go for Pritunl.
Stage 2 - Installing & Trying out Pritunl (this is where the tutorial portion of the video starts)
Now that our OS is setup, and you're SSH'd in, it's time to install Pritunl. I'm expecting that these commands could change in the future, so please refer to the official Pritunl documentation here: https://docs.pritunl.com/docs/installation
Copy over each piece from the CentOS 7 portion of their install docs to your SSH client individually as shown here: https://drive.google.com/a/linusmediagroup.com/uc?id=14i5tFSPXfOd7B_sKnYgKPmNLiWEiGJOp
With Pritunl installed you should be able to access your Pritunl VPN web interface at https://<SERVERIP>/ replacing "<SERVERIP>" with the IP of your VPS, and can now configure the VPN server.
Run 'sudo pritunl setup-key' in the PuTTY SSH client. Copy (double left click in PuTTY) the key it supplies into the Pritunl web interface (https://i.imgur.com/8Oqoykd.png).
Run 'sudo pritunl default-password' in the PuTTY SSH client. Copy (double left click in PuTTY) the username and password it supplies into the Pritunl web interface (https://i.imgur.com/Q6qePiM.png).
You should now be logged in and placed at the "Initial Setup" screen. Choose a username, password, and optionally a custom domain for your server (https://i.imgur.com/ckz8qzO.png).
Navigate to the "Users" page and click "Add Organization" to create an Organization, this is essentially a group for users (https://i.imgur.com/qF1kM6W.png).
On the same page click "Add User" to create a User(s), while being sure to specify a secure pin (https://i.imgur.com/zbCyJzX.png).
Navigate to the "Servers" page and click "Add Server" to create your VPN server (https://i.imgur.com/00nyfI3.png).
Set "Name" to whatever you'd like to name the VPN server.
Set "Port" to your desired VPN port, this is the one we added a firewall rule for earlier in the tutorial. We are using "1337".
Enable "Allow Multiple Devices"
Disable "Inter-Client Communication" (this disallows VPN users on the same virtual network from seeing each other, you may wish to keep this feature but if you don't know what this means, just disable it).
Click "Add" to save the configuration.
Before you can start the server, you must attach the Organization you created earlier to it, so the server knows which users to allow to connect.
Click "Attach Organization", and it should auto populate both the organization and server you made earlier, as they're the only ones present in the database (https://i.imgur.com/6MPdOhr.png).
Click "Start Server", and bam, your VPN server is now running!
With your VPN server configured, you can now download the Pritunl client on your respective device, and the user profile used to connect to it.
Navigate to the "Users" page again, and click on the down arrow for the user you'd like to connect with (https://i.imgur.com/dldl5KR.png).
Navigate to the https://client.pritunl.com/ website to download the Pritunl client for your respective device, and then install it (https://i.imgur.com/hHtEQiw.png)
Launch the Pritunl client, and then drag the <USERNAME>.tar file into the Pritunl client (you can also use the Import Profile button) (https://i.imgur.com/I9Uge7H.png).
Click the hamburger menu icon on the profile you added and then click "Connect". Enter your pin, and BAM! You're now connected to your very own VPN server.
Note: If the connection doesn't succeed, it's likely you forgot to disable the CentOS file (steps 6.1-6.3.1), or you incorrectly set the port during the Pritunl setup (Stage 2, step 2.6.2), or you incorrectly set the port during the Vultr firewall setup (step 4.2.1.2).
Check https://whatismyipaddress.com/ to see if your IP address did indeed change. It should show your location as wherever your VPS is hosted. Yay.
Note: If you are trying to setup a VPN server to access your network remotely, there are instruction from Pritunl here: https://docs.pritunl.com/docs/accessing-a-private-network
Same... when I ran my R7000 as a primary router, I used a laptop cooler as well (though plugged into the wall). I now use mine as an AP for my PFsense router and there is almost no detectable heat.
Huh, weird, my R7000 works fine. Granted, I never run factory firmware on it - I have Advanced Tomato and it works well. It is aging though, and eventually will need to be replaced with something else in the near future. Seriously considering going with something from Ubiquiti Networks instead.
If you have any way to actively cool the router that might help. DDWRT made my router run hot as hell. I used a laptop cooler I had laying around and plugged it in to the routers USB port. Found it ran much cooler. The lack of support is why I choose to buy a new router. Because I was not sure when DDWRT was going to update the firmware due to the security issues found in WPA 2 last year or so.
Thank you! I don't know why my response hasn't been posted but I am currently using DDWRT. This actually comes with its own problems too. Slow support aside, my wifi drop randomly if there is 7 or more devices are connected. It also requires to restart every so often in a matter of days. I haven't tried advanced tomato. I will check this out and thank you again for your recommendation on Synology RT2600AC.
Here you can suggest review topics:
LTT in the past has covered this device, Taran did some more videos on his personal channel about them.
They look super cooll, but also somewhat expensive.
This is the videos I am talking about:
Taran video and its follow up:
DarkAcid1212 got a reaction from Louiespitfire in HELP, my cpu light keeps coming on despite reseating the cpu multiple times and bios flashing the motherboard
DarkAcid1212 got a reaction from Crunchy Dragon in Swapping out for new mother board and processor
DarkAcid1212 got a reaction from svmlegacy in Swapping out for new mother board and processor
DarkAcid1212 got a reaction from Radium_Angel in What’s the BEST TV Under $400?
DarkAcid1212 got a reaction from kirashi in Rant about my router
