CloudatCost

FYI -- the coupon code still works.
Now to figure out the easiest way to host my own sites!

CentOS with LAMP and ISP Config 3 or Froxlor would be the easiest way unless you want to pay for Cpanel..

This might help you if you haven't done it before https://www.howtoforge.com/perfect-server-centos-6.4-x86_64-apache2-dovecot-ispconfig-3-p3

Reid Cooper

@thecreativeone91 Hey, you have an avatar now! Nice to finally see you.

scottalanmiller

@thecreativeone91 said:

This might help you if you haven't done it before https://www.howtoforge.com/perfect-server-centos-6.4-x86_64-apache2-dovecot-ispconfig-3-p3

Good starting place. Although that tends to build out lot of extra stuff. That's meant for people running their own hosting provider!

Danp

Thanks for all the input. I believe that LAMP is up and running properly. I looked into both ISP Config and Froxlor. I like the look of ISP Config. However, the tutorials I've read appear "complicated" with lots of steps.

Do I really need to disable the firewall, SELinux, install all of these extra packages, etc?

scottalanmiller

Firewall should not be disabled, just ports 80 and 443 opened. Firewall should always be on.

Disabling SELinux is pretty important, if you don't do that you will need to know how to configure it.

@Danp said:

Thanks for all the input. I believe that LAMP is up and running properly. I looked into both ISP Config and Froxlor. I like the look of ISP Config. However, the tutorials I've read appear "complicated" with lots of steps.

Do I really need to disable the firewall, SELinux, install all of these extra packages, etc?

ISPConfig has it's own firewall. You can use either. It would be simpler to use ISPConfig's firewall.

Danp

Ok.... this has been a fun "experiment". Clearly I don't have Fail2Ban properly configured:

Last failed login: Thu Feb 26 06:37:39 EST 2015 from 103.41.124.16 on ssh:notty
There were 7770 failed login attempts since the last successful login.

[root@localhost ~]# fail2ban-client status sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 0
|  |- Total failed:     0
|  `- Journal matches:  _SYSTEMD_UNIT=sshd.service + _COMM=sshd
`- Actions
   |- Currently banned: 0
   |- Total banned:     0
   `- Banned IP list:

I'm thinking that I should start a new thread so that this one can get back on topic.

@Danp said:

Ok.... this has been a fun "experiment". Clearly I don't have Fail2Ban properly configured:

Last failed login: Thu Feb 26 06:37:39 EST 2015 from 103.41.124.16 on ssh:notty
There were 7770 failed login attempts since the last successful login.

[root@localhost ~]# fail2ban-client status sshd
Status for the jail: sshd
|- Filter
|  |- Currently failed: 0
|  |- Total failed:     0
|  `- Journal matches:  _SYSTEMD_UNIT=sshd.service + _COMM=sshd
`- Actions
   |- Currently banned: 0
   |- Total banned:     0
   `- Banned IP list:

I'm thinking that I should start a new thread so that this one can get back on topic.

You need to do

vi /etc/fail2ban/jail.local

Then copy this into the file, and save the files (hit insert to add text, escape to leave insert mode and :wq to write quit (save & exit)

[sshd]
enabled = true

Make sure SELinux is disabled as well.

Danp

@thecreativeone91

It was enabled, but wasn't logging. It may have been an issue with SELinux. I've since started over by reimaging the server. Further discussion is occurring here.

Appreciate the input!