We are still actively working on the spam issue.
Difference between revisions of "Setting up a Server"
m (Removing redundant information) |
m (Fixed link) |
||
| Line 12: | Line 12: | ||
* SSH-tunnel to the server from work/school/etc to use it as a proxy, so that the admin of the network you're on can't see what sites you're going on. | * SSH-tunnel to the server from work/school/etc to use it as a proxy, so that the admin of the network you're on can't see what sites you're going on. | ||
* Run a VPN for location spoofing or security when you're out and about. | * Run a VPN for location spoofing or security when you're out and about. | ||
| − | |||
=Getting Started= | =Getting Started= | ||
* [[Encryption|Encrypted or unencrypted drive (LUKS)]] | * [[Encryption|Encrypted or unencrypted drive (LUKS)]] | ||
| − | * [[Home server/Choosing an | + | * [[Home server/Choosing an Operating System]] |
| − | * [[Home_Server/ | + | * [[Home_Server/Setting up your Storage]] |
* [[Home server/Remote access]] | * [[Home server/Remote access]] | ||
Revision as of 11:34, 23 December 2020
Need to email? Set up a web server? Well, here's some advice. We're gonna try to write this page like you've never done this shit before. It does, however, assume you have at least some basic GNU/Linux knowledge. If you don't, you probably aren't ready for this. You weren't going to set up a server using Windows, were you? Jesus Christ, how horrifying.
Common uses for a server:
- Install a media player system and stream content to your local network
- Install a cloud service like Nextcloud to run your own Dropbox service, no privacy issues, full control, unlimited space (well, limited by how many drives you can cram in).
- Always on seedbox. Start torrents with your phone through the web interface while out, they're done by the time you're back home.
- Host a personal website.
- Run your own mailserver just like Hillary!
- Warning: Running a mailserver is a shitton of work. You will get hacked all the fucking time and it's very high-maintenance.
- Run a dedicated game server.
- Run various webapps, develop your own webapps.
- SSH-tunnel to the server from work/school/etc to use it as a proxy, so that the admin of the network you're on can't see what sites you're going on.
- Run a VPN for location spoofing or security when you're out and about.
Contents
Getting Started
- Encrypted or unencrypted drive (LUKS)
- Home server/Choosing an Operating System
- Home_Server/Setting up your Storage
- Home server/Remote access
Recommended software
Common home server services
Most packages have clear tutorials on their repo/project site. Here are some handpicked guides for the most common types of software used
- Cloud Storage - Nextcloud
- Web Server - Apache or NGINX
- VPN - Wireguard or OpenVPN
- Media Streaming - Jellyfin or PLEX
- XMPP - Prosody
Centralized storage
A server is perfect for this job. It is (supposedly) an always available resource on the local network. If using this in your house, you can expect reasonable speeds, even over WiFi that will let you do many daily tasks. One option is to set it up with NFS (Linux-centric, can be used on windows but it's shit) or Samaba if you have Windows clients on your network, so you can watch your chinese cartoons on any device and keep your documents/whatever synchronised. This synchronisation is a key benefit of the network storage.
You may want to consider a RAID array for long-term file storage. RAID is not backup, but will protect your files in case of drive failure. See Home server#File Systems and RAID for more information.
Web server
A web server serves up a page. The nice things about serving it from a server, than, say, Wordpress or your Dropbox share, is that now you can run web apps and server side code for a dynamic page.
Keep in mind that many server software installs (such as email with) involve setting up a webserver, so you may not even need to do anything.
HTTPS
The extra CPU burden of TLS is minuscule. Your server should serve up everything on HTTPS only. Keep port 80 (plain HTTP) open but redirect everything to HTTPS. If port 80 is closed, typing the address of your server into the address bar of a browser will probably fail (because the browser assumes you meant HTTP, but you have to go to HTTPS).
Issue a self-signed certificate. CAs are for jerks. Set the duration short (eg. a year) and don't forget to make a new one. If you've got a domain, get a Lets Encrypt-signed cert and set up a cron job to renew it. They're pretty sweet.
Certbot makes https easy to implement with Let's Encrypt certificates
External links
- Linode Library - Good beginner tutorials
- Script to secure Debian and Debian based Linux installs
- Setup pfSense
- Raspberry Pi KVM for managing servers remotely
- The Complete System Administrator Guide
- Example of a personal server
- Increase Linux Internet speed with TCP BBR congestion control
