That’s a predictable behavior. If you can’t work on your site from another machine on your own network, or if you really want to access it from the servers browser, you will either have to set up your site in a name based virtual host container in httpd.conf, or you can add an entry to your hosts file that will resolve your domain to localhost, or “127.0.0.1” from the servers browser.
You can try this first if you aren’t yet familiar with name based virtual hosts.
Open a console:
[you@yourhost ~]$ su –
Password: (your root password)
[root@yourhost ~]$ gedit /etc/hosts
– or using whatever editor you like. When the file opens, add these entries on their own lines at the bottom of the file making sure to leave space in between just like the existing entries above it:
127.0.0.1 ww.pcelementspr.com
127.0.0.1 pcelementspr.com
( I left one “w” off to prevent it becoming a link – use all three – “www” when you make the entry. )
Save the changes and close the editor. I can’t remember if you need to do an httpd restart or not … system-config-services will bring up the service configuration gui from a console … but now when you access your site from the browser on the server, I think it should look normal again. I hope that’s all correct info. Perhaps someone will jump in if I left something out.
Here is a reference for Using Name-based Virtual Hosts as well.
