CentOS - Jan 2016 - Apache doesn't display "It works page" under CentOS 7

On Fri, Jan 29, 2016 at 11:41 AM, Michael H <michael at wemoto.com> wrote:
> setsebool -P httpd_can_network_connect on
> firewall-cmd --add-service=http --permanent
>
I have ran those two and still can't access. I have restarted httpd and
iptables services after ran those lines. BTW, what those means? setsebool
is part of SELinux? Or this is new kind of extra security layer on CentOS7?
I am moving from Centos 6.7 to 7 and things change between versions.

On 29/01/16 16:45, reynierpm at gmail.com wrote:
> On Fri, Jan 29, 2016 at 11:41 AM, Michael H <michael at wemoto.com>
wrote:
> 
>> setsebool -P httpd_can_network_connect on
>> firewall-cmd --add-service=http --permanent
>>
> 
> I have ran those two and still can't access. I have restarted httpd and
> iptables services after ran those lines. BTW, what those means? setsebool
> is part of SELinux? Or this is new kind of extra security layer on CentOS7?
> I am moving from Centos 6.7 to 7 and things change between versions.
Selinux has been around for a while.

setsebool - set selinux boolean

You should probably be using the firewall-cmd rather than iptables;
firewall-cmd --add-service=http --permanent - add the http service to
your firewall.

I forgot, unless you run

firewall-cmd --reload

the rules may not be in play.

Michael

> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

On Fri, Jan 29, 2016 at 11:48 AM, Michael H <michael at wemoto.com> wrote:
> Selinux has been around for a while.
>
Yes, I know this but ...

>
> setsebool - set selinux boolean
>
What I am asking is if the command above is part of SELinux since I doesn't
use before because it's a VM running on my PC so I not need such security
levels.

>
> You should probably be using the firewall-cmd rather than iptables;
> firewall-cmd --add-service=http --permanent - add the http service to
> your firewall.
>
> I forgot, unless you run
>
> firewall-cmd --reload
>
> the rules may not be in play.
>
Ummmm ....

# firewall-cmd --reload
FirewallD is not running