Bug 8831 - Can't access my website on any IP except localhost
Summary: Can't access my website on any IP except localhost
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-26 22:39 CET by Fabrice DANT
Modified: 2013-08-03 06:22 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Fabrice DANT 2013-01-26 22:39:55 CET
Hi,
All my LAMP installation works fine in my browser when I'm staying on "localhost" address.
But when I type "http://127.0.0.1/anyfolder" or "http://192.168.0.xx/anyfolder" = error 500
Something is misconfigured but I can't find what.
I've disabled my firewall (there is also an issue with the draktool because it doesn't save my firewall configuration when I click on "All - no firewall").
Maybe the problem is not located into Apache confs but anywhere in DNS or firewall configs. I don't know.



Thank you !
Comment 1 Manuel Hiebel 2013-01-26 23:20:07 CET
http://www.cyberciti.biz/tips/http-error-500-internal-server-for-php-pages-and-solution.html

and btw, bugzilla is not for support
Comment 2 Fabrice DANT 2013-01-26 23:32:17 CET
The issue is in fact due to the bad behavior of the draktool.
My server seemed to run after "service iptables stop"
Comment 3 Fabrice DANT 2013-01-26 23:47:39 CET
Oh yes, error 500 was my own mistake after disabling iptables, my PHP pages had bad redirections. I was confused by the fact that I thought draktool saved my firewall configuration (all disabled) and didn't, in a first time.
I had to report a draktool bug with the firewall configuration.
Comment 4 Manuel Hiebel 2013-01-27 00:25:53 CET
check before, we have already a few one
Comment 5 Henri de Solages 2013-08-03 06:22:07 CEST
So this, in itself was not a bug, was it?

Status: NEW => RESOLVED
CC: (none) => fiable
Resolution: (none) => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.