hello friends! new(ish)!

Setting up a Server: Difference between revisions

From InstallGentoo Wiki v2
Jump to navigation Jump to search
>4ab41
(Added Windows SSH server, removed from home server page)
mNo edit summary
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Need a fileserver that won't face the external internet?  Check [[Home server]].'''
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.
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.


A lot of this applies to both a physical machine as well as a [[VPS]] setup.
Common uses for a server:
 
* Install a media player system and stream content to your local network
=== Common uses for a server===
* 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).
* Install FTP software and run an FTP site.
* Install a cloud service like Seafile 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.
* 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.
* Host a personal website.
* Run your own mailserver just like Hillary!
* 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.
** Warning: Running a mailserver is a shitton of work, especially if you want emails to google/outlook to be seen.
* Run a dedicated game server.
* Run a dedicated game server.
* Run various webapps, develop your own webapps.
* Run various webapps, develop your own webapps.
Line 17: Line 13:
* 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=
[[Setting up a Server/Home or Remote?|Home or Remote?]]
* [[Encryption|Encrypted or unencrypted drive (LUKS)]]
 
* [[Home server/Choosing an Operating System]]
[[Setting up a Server/Choosing an Operating System|Choosing an Operating System]]
* [[Home_Server/Setting up your Storage]]
=Setting up your services=
* [[Home server/Remote access]]  
Most packages have clear tutorials on their repo/project site. Here are some handpicked guides as well as some written by other anons.
*[[Setting up a Server/Mail|Mail]]
*[[Setting up a Server/DNS|DNS]]
*FTP
*Cloud Storage
*Web Server
*ZNC
*SSH
*Everything in Docker
*HAProxy (for multiple machines behind one ip).
*VPN
*Media Automation (Sickbeard, Flexget etc.)
*Security
*Media Streaming with icecast/ffmpeg/cvlc


=Recommended software=
=Recommended software=
*Mail: see [[Setting up a Server/Mail]]
* [[Home server#Server software]]
*DNS: see [[Setting up a Server/DNS#Authoritative]]
* [[Home server#System administration software]]
*FTP: vsftpd, glftpd (nonfree)
*IRCd: inspircd, ngircd, kike
*IRC Bouncer: znc
*XDCC: iroffer-dinoex
*XMPP: Prosody
*Proxy: danted
*Usenet Server: Leafnode, InterNetNews
*Web Cache/Reverse Proxy: varnish, squid, nginx
*Web: nginx, darkhttpd (use stunnel for ssl)
*Config Management: cdist, ansible, salt
*Control Panel: Webmin, Cockpit
*Direct Connect Server (DCC): uhub, luadch
*Monitoring:


==Less common ==
==Common home server services==
*BBS Server: Mystic BBS (BBSs are dead)
Most packages have clear tutorials on their repo/project site. Here are some handpicked guides for the most common types of software used
*MUD: PennMUSH
* Cloud Storage - Nextcloud
* Web Server - [https://homebrewserver.club/fundamentals-webserver-website.html Apache] or NGINX
* VPN - Wireguard or OpenVPN
* Media Streaming - Jellyfin or PLEX
* XMPP - [https://homebrewserver.club/configuring-a-modern-xmpp-server.html 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 [[Wikipedia:RAID|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.
 
== 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 samba, so you can watch your chinese cartoons on any device and keep your documents/whatever synchronized. This synchronization 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. NAS4Free allows you to easily set up RAID arrays using UFS or ZFS.


== Web server ==
== Web server ==
Line 71: Line 41:
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.
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===
===HTTPS===
Line 80: Line 49:
[https://certbot.eff.org/ Certbot] makes https easy to implement with Let's Encrypt certificates
[https://certbot.eff.org/ Certbot] makes https easy to implement with Let's Encrypt certificates


==Remote access via SSH==
=External links=
 
* [https://library.linode.com/ Linode Library] - Good beginner tutorials
=== GNU or BSD based systems ===
* [https://landchad.net/ landchad.net] - "Chad's Guide to Starting Your Own Website"
 
* [https://github.com/x08d/lockdown.sh Script to secure Debian and Debian based Linux installs]
1. You usually enable the ssh server during the installation. Do this if possible, it is the simplest way.
* [https://gist.github.com/deergod1/818ec78ab70947a2f89df2bb5bb28896 Setup pfSense]
 
* [https://github.com/pikvm/pikvm Raspberry Pi KVM for managing servers remotely]
2. If you did not setup sshd to auto start you can type:
* [https://devconnected.com/syslog-the-complete-system-administrator-guide/ The Complete System Administrator Guide]
 
* [https://github.com/erebe/personal-server/blob/master/README.md Example of a personal server]
:* <code>/etc/rc.d sshd start</code>, if you use System V init.
* [https://www.cyberciti.biz/cloud-computing/increase-your-linux-server-internet-speed-with-tcp-bbr-congestion-control/ Increase Linux Internet speed with TCP BBR congestion control]
:* <code>systemctl enable sshd.service && systemctl start sshd</code>, if you use systemd.
 
3. If that does not work, you need to install <code>sshd</code> or <code>openssh-server</code> with your package manager.
 
=== On [[Windows]] ===
 
* Download [http://cygwin.com/install.html Cygwin]
* Choose "Install From Internet"
* Choose a mirror to download from
* When you get to the "Select Packages" screen, search SSH
* Choose to install the "Bin" version of the "openssh" package
* Download all dependencies and wait for setup to complete
* Open Cygwin and wait for the initial setup to complete
* Type "ssh-host-config" without the quotes
* Say yes when you get asked about privilege separation
* Say yes when asked to create a local user named sshd
* Say yes when asked to install sshd as a service
* When you see "CYGWIN=", type "ntsec tty" without the quotes ([http://www.chinese-watercolor.com/LRP/printsrv/cygwin-sshd.html this guide]explains why)
* You should be done now setting up the SSH server. To start it, type "net start sshd" without the quotes.
 
If you see:
 
The CYGWIN sshd service is starting.
The CYGWIN sshd service was started successfully.
 
Then everything went correctly. If not, you should Google the error.
 
=== On [[OS X]] ===
 
Simply go into sharing permissions and enable fucking everything.
 
=== Post-setup ===
 
* Forward port 22 to the server ([http://portforward.com/ Here's a guide if you don't know how])
* OPTIONAL: [[Setting_up_a_Server#Domain_and_static.2Fdynamic_IP|Assign the server an address]], so you can type ''server.com'' instead of XXX.XXX.XXX.XXX ([http://lifehacker.com/software/web-publishing/geek-to-live--how-to-assign-a-domain-name-to-your-home-web-server-124804.php Read this])
 
===Tunneling===
Create a tunnel and use it as a proxy for environments that block certain DNS requests or pages and to encrypt your data
===Wake on LAN===
Turn on a PC on your LAN [https://wiki.archlinux.org/index.php/Wake-on-LAN Arch Wiki guide]
 
===Web hosting===
Host webpages, use nginx or apache [https://library.linode.com/web-servers/nginx/installation/debian-6-squeeze debian nginx guide]
===Proxy===
You can use a proxy [http://www.debiantutorials.com/installing-and-configuring-squid-proxy-server/ guide]
====Compression====
[http://freecode.com/projects/ziproxy Ziproxy] (Opera style web compression, including images)
 
==Media automation==
===Torrenting===
Use a daemon like Transmission or Deluge.
 
===TV Series===
You can use a daemon like [http://sickbeard.com/ Sickbeard]
===Movies===
You can use a daemon like [https://couchpota.to/ Couchpotato]
===Music===
You can use a daemon like [https://github.com/rembo10/headphones/ Headphones]
 
=Security=
[[Setting up a Server/Security]]


= External links =
=See also=
[https://library.linode.com/ Linode Library] - Good beginner tutorials.
* [[Home server]]
* [[Setting up a Server/Home or Remote?]]
* [[Setting up a Server/Mail]]
* [[Setting up a Server/DNS]]


[[Category:Tutorials]]
[[Category:Tutorials]]
[[Category:HowTo]]
[[Category:HowTo]]

Latest revision as of 08:23, 3 July 2023

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, especially if you want emails to google/outlook to be seen.
  • 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.

Getting Started

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 reminder why you should always self-host and if you don't, avoid inbred retards
A reminder why you should always self-host and if you don't, avoid inbred retards

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.


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

See also

Retrieved from "https://igwiki.lyci.de/index.php?title=Setting_up_a_Server&oldid=12201"