MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hmmm, OK the fact that it does not stop may help explain why changes to the configuration changes that you are making to the httpd.conf file do not appear to be recognized.
Because in the format that the conf file should have the system listening not on port 80, but on port 8080.
If it is possible, I would like to see of you could restart the machine. This way we know that the service will stop, and it will restart and read the configuration file. Once the system restarts, I would suspect that it should respond on the 'new' port. If after the reboot it still does not respond then I suspect that the httpd.conf file that we are editing is not controlling the instance of Apache that you are using and we will have to go back to the drawing board to sort things out.
Hi guys - I know I's been long time ago.... but could you tell how that story ended??
I have similar problem - my apache keeps giving me "Access forbidden" message, and I don't know where to set it up properly
rgrds
T.J.
I solved one part of my problem: RootDirectory were pointing to wrong place. So now I can see 'It works!!" page - and now there is time to start a fight with no-ip ...
In my httpd.conf I put Listen for ports 80, 8080 and 8001 just to make sure that at least one of them will kick in. I found out that Apache denies all access to as default to whole file system "/" so it is nessesery to create a directive which will allow access to directory containnig www documents....
In your case i think it might be firewall blocking traffic to your box or there is some options set which deny access from foringer addresses - Listen shoould contain only port numbers i think no IPs
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.