Apache2 httpd.conf problem

My dishwasher just blew up and the power in the whole house switched off. My webserver down stairs was running apache2 fine before. When I try to start apache2 now on the machine I get the error

Syntax error on line 292 of /usr/local/apache2/conf/httpd.conf:
The port number "http://mysite.com" is outside the appropriate range (i.e., 1..65535).

Even though on line 292 in httpd.conf

ServerName http://mysite.com

And above that is

Listen 80

So why is it doing this?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

>The port number "http://mysite.com" is outside the appropriate range (i.e., 1..65535).

The "http://mysite.com" is not regular port number i think :)

>Even though on line 292 in httpd.conf
>                               ServerName http://mysite.com
>And above that is
>                               Listen 80

Maybe something wrong hapend to your config file, edit something in it and save. If it doesn~t work try put a blank line betwen above lines.

confusedmoronAuthor Commented:
I commented that line out and it starts fine...  It's trying to read a port number from ServerName?
ServerName shouldn't include the http:// part, and you can specify the port there;  try either:

ServerName mysite.com

(without the http://), or:

ServerName mysite.com:80

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
confusedmoronAuthor Commented:
That worked. Thanks! What confused me was that it was working fine before, with the http:// part. So why would it just start complain about it now?
I don't think that it ever should have worked...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.