httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yehuda Katz <>
Subject Re: [users@httpd] Permission Still Denied with Moodle
Date Tue, 15 Oct 2013 13:42:43 GMT
Good to hear.

I also discovered that the netstat output not showing an IPv4 listener was
(at least in Debian) a design decision. They considered changing it to be
type 'tcp46' instead of just 'tcp6', but it is not clear why that was not
changed. I believe it also depends on the kernel and I have never seen that
before on any other system.

- Y

On Tue, Oct 15, 2013 at 9:18 AM, Timothy Curchod <>wrote:

> Hi again Yehuda,
> Where is the iptables firewall configuration?  Oh, that's no longer the
> default firewall in Fedora.  Let me introduce you to FirewallD:
> #firewall-cmd --state
> running
> #firewall-cmd get-default-zone
> public
> #systemctl stop firewalld.service
> Webservice on port 80 restored.
> Success.  Now all ip addresses are accessible!
> The two boxes here, one running Fedora 10, and this one running Fedora 19
> can't be more different.  The desktop, Gnome, screensavers, etc, and now
> the firewall are completely different.  Thankfully the terminal and gedit
> are still the same.
> Yehuda, Eric, Stormy, and anyone who read my e-mails, thanks for the help.
> Now it's time to read the huge document at
> to figure out how to work this
> thing.
> Timothy.
> ------------------------------
> From:
> Date: Mon, 14 Oct 2013 22:00:43 -0400
> To:
> Subject: Re: [users@httpd] Permission Still Denied with Moodle
> On Mon, Oct 14, 2013 at 6:06 AM, Timothy Curchod <>wrote:
> The bad news is that in the error log there is nothing when going to
> or http://*my*.*ip*.*goes*.*here*/info.php.
>  Localhost works fine.
>  So if there is no error in the httpd error_log, then I am on the wrong
> mailing list now, right?  It's not an Apache problem, it's a network
> setup/hardware issue.
> To recap, the problem now is that requests through localhost work properly
> and other requests time out. Is that correct?
> To me this really indicates that either Apache is not listening on other
> IPs (which we went through already) or (not sure why I did not mention this
> sooner) you might have a firewall in the way. Can you check if you have a
> firewall (like iptables) running on the system?

View raw message