![]() ![]() ![]() It is slightly different from the original file from the tutorial I based my setup on - I had to uncomment outbound DHCP request as I used Linode host and it was essential for the server to work. A INPUT -m state -state NEW -p tcp -dport 443 -j ACCEPT A INPUT -m state -state NEW -p tcp -dport 80 -j ACCEPT A OUTPUT -o eth0 -p tcp -m tcp -dport 443 -m state -state NEW -j ACCEPT A OUTPUT -o eth0 -p tcp -m tcp -dport 80 -m state -state NEW -j ACCEPT A INPUT -i eth0 -p tcp -m tcp -dport 222 -m state -state NEW -j ACCEPT A OUTPUT -p udp -dport 123 -sport 123 -j ACCEPT # Outbound Network Time Protocol (NTP) request A OUTPUT -o eth0 -p udp -m udp -dport 53 -j ACCEPT A OUTPUT -p udp -dport 67:68 -sport 67:68 -j ACCEPT ![]() # Allow outbound DHCP request - Some hosts (Linode) automatically assign the primary IP # Allow all traffic on the loopback interface I OUTPUT 1 -m state -state RELATED,ESTABLISHED -j ACCEPT I INPUT 1 -m state -state RELATED,ESTABLISHED -j ACCEPT # Accept any related or established connections With that, I created a node with a Debian Jessie distribution, set up the root password and booted it.įrom Remote Access tab, I read the server’s IP and used it to log in via ssh (for the sake of this post, let’s assume that the server’s IP is 1.1.1.1): Preparing a serverįirst, I registered at the Linode site and configured my planning - 1 node with 2 GB of RAM, 1 CPU Core, 24 GB of space and 2TB of transfer. Most of that time I spend reading comprehensive tutorials to learn how to tweak things in the future (links to useful materials at the end of the post). Merely following the tutorial let me set things up in about 2 hours, from the moment I registered a Linode account to the moment when I registered as the first user on working site. I was honestly surprised, how easy it was to set up a Mattermost server to the point where it just works. Since Let’s Encrypt won’t allow you to register a certificate to a domain like li]., you should also obtain some nice domain if you don’t have one already. Altogether, it should be under $13 per month. We decided to go with the cheapest Linode server, obtain a TLS certificated from Let’s Encrypt and back up our data using both Linode backup functionality and AWS S3 storage. The setup we decided to try out is a single Debian server with TLS secured connection and daily backups of all configs and user data in the cloud. Originally this post was published on ScalaC blog at. After that, I will describe how its UX compares to Slack’s and whether or not it’s something right for you. I’ll show that, as long as you are not afraid of command line, you can quickly setup your own secured chat server from scratch. With those assumptions in mind, I compiled knowledge about basic server security guidelines from Mattermost’s documentation and several tutorials. I made some assumptions about used hosts, distros, and setup that simplified the whole process. In this post, I want to describe how I configured my Mattermost server step by step. It appears there is one - Mattermost Team Edition. have access to all archives without high pricing, you might start with some cheaper alternative. However, if you want to fully own your data and e.g. Most, if not all, of us, know about Slack and how it (usually) improves communication within teams that use it. After a while, we found out that social media and instant messaging apps are not really an answer to our needs, so we decided to give a chance to something that easily engages everyone. When you live far away from some of your best friends, you want to find some reasonable ways to stay in touch. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |