apache not working with virutalhost

so for some reason,  apache stopped parsing all pages, it would just show blank i cannot ifgure out what is up with this config file, but anyway, i replaced it wth the std one, that is distributed with apache 2.0.54.

anyway, now with NameVirtual set, ot listen *:80, and i have virtual hosts enabled. they all show the same page, they all show the first virtualhost that is listed, so whatever is in that directory is show for all virtual hosts, here is what my virutal host line looks like

--snip--
NameVirtualHost *:80

<virtualhost *>
serveradmin webmaster@phre.net
servername phre.net
serveralias www.phre.net
errorlog /home/phre/logs/phre.net-error_log
customlog /home/phre/logs/phre.net-access_log common
#SSLEngine on
#SSLCertificateFile /home/phre/www.phre.net.crt
#SSLCertificateKeyFile /home/phre/phre.key
DocumentRoot /home/phre/public_html
</virtualhost>

why wouldn't this work. It worked before...
nastealAsked:
Who is Participating?
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.

bimal_linuxCommented:
In your configurations, instead of * please give the IP address. It will work.  if ip is: 111.111.111.111 it will look like:

NameVirtualHost 111.111.111.111:80

<virtualhost 111.111.111.111:80>
serveradmin webmaster@phre.net
servername phre.net
serveralias www.phre.net
errorlog /home/phre/logs/phre.net-error_log
customlog /home/phre/logs/phre.net-access_log common
#SSLEngine on
#SSLCertificateFile /home/phre/www.phre.net.crt
#SSLCertificateKeyFile /home/phre/phre.key
DocumentRoot /home/phre/public_html
</virtualhost>

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
nastealAuthor Commented:
actually i just removed the :80 after namevirtualhost *:80, and now it works. spectacular. sorry i should have closed this but i figured it out about 30 minutes ago :( thanks for the help though.....

mod close the thread
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.