Problem with apache when changing the listening port

[FadeOut]

Hi,

I got an newly installed fedora core 5 linux box, and I am working in a company, but we need to have access to our website outside the internal network (from internet). So i decided to change the port, because my provider won't let us use port 80. (Seems that 8080 do not work neither) But, when i use port 8888, and restart, it will failed everytime, can anyone can help me with this tiny problem?

 

[thedaver]

How do you conclude it failed?

What did you write in httpd.conf to set the port?

Have you checked firewall settings on the LAN and local server?

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[sleipnir214]

Does your Apache error log contain any clues? When Apache fails to start, it will often log useful information there.



Want the best answers? Ask the best questions! TANSTAAFL!

 

[FadeOut]

thedaver :
I'd concluded it failed because when i typed :
service httpd restart, it stopped [ok] and it started [FAILED]

in httpd.conf I wrote :

Listen 8888



Sleipnir:
Where can i find those logs, i'm kind of rusty in the linux world (last time I was in touch with it, it was with mandrake 7.2)

 

[sleipnir214]

/var/log is a good place to start.

Or perhaps /var/log/httpd



Want the best answers? Ask the best questions! TANSTAAFL!

 

[sleipnir214]

You could also ask Apache. In your httpd.conf file there will be a ErrorLog line. That line tells Apache where the error log is.

You could very well have more than one ErrorLog line, with some inside VirtualHost tags. You'll want the line that is outside any tags.



Want the best answers? Ask the best questions! TANSTAAFL!

 

[FadeOut]

I've checked in /var/log/httpd/error_log but, it doesn't seems to have any information about the problem


(i've rebooted the server, and checked the last line, no lines were added since the first time i've checked)

 

[thedaver]

apachectl configtest

configtest - do a configuration syntax test

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[RhythmAce]

If all you have changed is the Listen directive then I would say it is not starting because port 8888 in already in use or is closed by your firewall. If you use a non-standard port then remember that users will need to use the port in the url i.e.

http://www.mydomain.com:8888

or port 80 will be assumed. If this is not acceptable, you may try a pointing service. They can point your domain name or a free sub-domain to a dynamic ip as well as a different port. A couple I can think of off the top of my head are dns2go, dyndns and tzo.

 

[thedaver]

you can try from the localhost

wget

http://localhost:8888

That might still fail because of local firewall, but it takes a great number of external variables out of the way

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/