Rich, I understand where where you are coming from. I too, have long time experience with computers and reached a point where I had to forget what was no longer valid or useful. Although languages like BASIC, Pascal, RPG II, etc. are no longer useful to me, they did help me to understand that there is lots I do know and lots I don't know.

What I do know is that trying to run a Web Server from somewhere other than a properly setup Data Center is not a good idea. Besides the fact that a DC can provide a much faster connection, they also have qualified people to look after hardware/routing issues. A managed Server will also get you qualified help with certain software issues; like what you are describing here now.

The fact you would post your Server config files on a public forum, instead of just the relevent section because you don't know where to look for problems, shows that you need qualified help in Server Admin.

Please do yourself and your future Clients a favour, lease or co-locate a Server from a DC and hire someone to set things up properly for you. After that, maintaining Zen Cart should not be a problem.

Uhhhh Rob those files just contain setup info and those files are the same files that are on every Linux server?? If someone can hack or is going to try and hack they probly already have looked at other coppies of these files. This is nothing thats TOP SECRET.

Rich, aside from (valid) security concerns with your current setup, this is the question you were asked:

What are your vhost definitions from your .conf files?

This could have been one of your answers:

NameVirtualHost xxx.xxx.xxx:80

#<VirtualHost xxx.xxx.xxx>
#    ServerAdmin [email protected]
#    ServerAlias www.yourdomain.com yourdomain.com
#    DocumentRoot /www/docs/yourdomain.com
#    ServerName yourdomain.com
#    User xxxxxxxx
#    Group xxxxxxxx
#    ErrorLog logs/yourdomain.com-error_log
#    CustomLog logs/yourdomain.com-access_log common
#    ScriptAlias /cgi-bin/ /directory/username/public_html/cgi-bin/
#</VirtualHost>

No need to post entire config files.

Let us not forget what was mentioned in your httpd.confg file.

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

This is the main Apache server configuration file. It contains the

configuration directives that give the server its instructions.

See URL:http://httpd.apache.org/docs/2.2/ for detailed information.

In particular, see

URL:http://httpd.apache.org/docs/2.2/mod/directives.html

for a discussion of each configuration directive.

**# Do NOT simply read the instructions in here without understanding

what they do. They're here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.**

I must admit that I am getting drawn into answering a lot of your questions and / or explaining what needs to be done. This I must now stop doing and wish you all the best. I can only hope though, that you follow my suggestions of setting things up properly. For the benefit of you, your Family and your potential Clients.

DrByte:

What are your vhost definitions from your .conf files?

PetesTown:

Do you mean the Apache System Config's??

DrByte:

I mean anything that defines how you've configured all those domains to work.

I was looking specifically for how you have your petestown domain vhosts defined. I don't see any of those in what you posted.

I'm inclined to agree with where Rob's directing you.
Perhaps studying virtual-host configuration/setup or a visit to webhostingtalk.com might take you further down the road of properly configuring your server since you want to do this yourself instead of have it commercially hosted.

Well as I stated earlier myself I DELETED ALL VIRTUAL HOST the only thing that is running is the APACHE WEB SEVER "localhost" the default sever that is created with every configuration when you first load an APACHE SERVER. The two files that I posted are the two main config files for your APACHE CONFIGURATION the virtual server configurations on this machine are written to /etc/httpd/conf.d/system-config-httpd-conf. And if you look above in the 3 of the 3 file post you will see NO VIRTUAL SERVER CONFIGURATIONS. "the lines you showed ROB" this is where they would be on this server. The /etc/httpd/conf/httpd.conf is the main config nad calls the above. there are 56 config files in the config.d folder but only one that handles this issue. Why will something see or not see subdirectories? Apache Directives set inside one or both of the above config files will overide the "htacess" or a "modsecurity" directive which is to deny everything first and then eveluate request from there on out. Soooooo being that this is the original configuration that worked for two months and this is not a VIRTUAL SERVER ISSUE now it may still be something changed in the SERVER config thats why I posted that file but its definitly not a VIRTUAL CONFIGURATION issue. So it still begs the question why can it not see the stylesheet. I was hoping to find a LINUX / ZENCART guy in here. I do understand the config guys. I ws looking for someone who understood it more than me.

And by-the way ROB DrByte go look at https://www.petesboots.org now and then feel free to post a comment ROB. I do understand the config actualy guys Yellow Knife was on the right track fallowed by something DrByte told me LOL

I want to thank everyone who looked and posted a comment and made and attempt to help, its funny sometimes you have to piece together many peoples comments in order to help yourself and your thought process. And always remember a forum is the sharing of all knowledge

                                                                                                Rich:clap:

PetesTown:

And by-the way ROB DrByte go look at https://www.petesboots.org now

I'm glad it's now showing content.
I'm puzzled about why it's converting to the IP address again instead of the domain name.

Hi DrByte that's because I went back and tried to put everything the way I had it when it worked and that was an HTTP forward with the IP/petes/petescart. I will correct that today and send all of them there. When I changed the forwarding the last time I was playing with it in the original loacation I had started using the domain name https://www.petestown.com because it was in the root it was still being found by the default server. when I setup the virtual server it is doing the forward just to the IP address. Now since I had my new virtual server set up as a dns I had https://www.petestown.com as its name and the rest were aliasis. So it would find the Index.PHP file but becasue the path was wrong ie https://www.petestown.com it would not find everything else. So when I went back to the IP address HTTP_SERVER HTTPS_SERVER it worked so it was the path in conjuction with how the forward was being sent with of coarse how I was handleing it on the sever here.
Rich