Guest timid1 Posted May 30, 2004 Report Share Posted May 30, 2004 Hi guys. I've just installed Mandrake Linux v10. I have Apache v2.0.48 installed and am getting the usual "successful installation index page." However, my ISP blocks port 80, so I set out to change the listening port to 8080 (I understand that /etc/httpd/conf/httpd.conf contains the necessary directives to make this happen). Even after I've committed the changes and restarted Apache, it acts as if it is still listening on port 80 and it denies all requests to port 8080. I've tested this out locally (on the Mandrake box) and on a separate Windows box on the same network. A separate, but possibly related problem, is that my requests for FTP/TELNET/SSH are all denied. However, I am using default ports for this. I have searched like mad for a solution, and from what I read, everyone says that it should pretty much work out of the box. I have tinkered a little with Webmin, but I don't think that I've tinkered enough to have FUBAR'd the config files. Any advice would be sincerely appreciated. Quote Link to comment Share on other sites More sharing options...
SwiftDeath Posted May 30, 2004 Report Share Posted May 30, 2004 (edited) I use to have the same apache problem. Webmin isn't a reliable application to edit apache unless you do some monitoring. The problem is that when you use webmin it doesn't edit the right config file for apache. Heres a list of what you should do, that I think will fix the problem. 1. Update webmin 2. Lower security level to normal 3. Log out and log on as root 4. Go to /etc/httpd/conf/ 5. Take the file httpd.conf file and put it somewhere else thats safe. (in case you need it again) 6. Make sure a file called httpd2.conf is there, if not forget what I said at all. 7. Log out of root and back on to your user 8. Raise your security levels again. 9. Try it out and see if it works. The reason I think this will fix your problem, is that webmin changes the wrong config file and when you remove the fake one its writing too, it automatically detects the right one which should be httpd2.conf, not httpd.conf. Also make sure to restart Apache after changes. Please let me know if this fixes your apache problem, I'm sorry I didn't know that answers to your other problems, but I'm sure someone else will. B) Edited May 30, 2004 by SwiftDeath Quote Link to comment Share on other sites More sharing options...
Guest timid1 Posted May 30, 2004 Report Share Posted May 30, 2004 The next question would be how to lower the security level. I set it to one step below paranoid when I installed Mandrake. Also, I didn't originally edit the httpd.conf file using webmin--I used good ol' vi! In any case, I'll wait for your response on how to lower the security level. Thanks! :D Quote Link to comment Share on other sites More sharing options...
SwiftDeath Posted May 31, 2004 Report Share Posted May 31, 2004 ok, to lower your security level you go into the MandrakeLinux Control Center. You enter your password and then you click Security. Then you click Levels and Checks. You'll see a dropdown bar, bring it down to standard. Make sure you set it back when your done with my intsructions that I mentioned earlier. Httpd.conf is just a fake file they put their I think, so you just try to edit http2.conf. You can also use Emacs instead of VI to edit it, which I find a lot easier. :lol: But webmin or comanche, is the best choice, for the command line challened and rookies. Quote Link to comment Share on other sites More sharing options...
Guest timid1 Posted June 1, 2004 Report Share Posted June 1, 2004 (edited) SwiftDeath, it turns out that the issue you've described with httpd.conf being a dummy file was the problem for me. I went ahead and renamed it to something else (httpdconf_backup) and then restarted the httpd service, and I am now successfully listening on Port 8080. I feel that I may have some sort of port forwarding issue on my router, though, so I just have to go figure that one out. I figure that as long as it's listening locally, I've got a routing issue. Thanks for the help! :) ** EDIT ** I fixed the problem. It turns out that my router was filtering out some local stuff. Even though my friends (outside my network) could access my server, I couldn't hit my server. In any case, I now have another problem, so I suppose that if I don't figure it out, I'll start a new thread. It's in relation to Apache configuration (for directory listings if there is no index file). Doesnt' seem to work for me. But I'll give it a shot. Edited June 1, 2004 by timid1 Quote Link to comment Share on other sites More sharing options...
SwiftDeath Posted June 1, 2004 Report Share Posted June 1, 2004 No problem at all man, it took me a while to figure that problem out, and I'm glad I did and that I saved another linux user some time. Thats what this board is for. :D Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.