Strang thing just happened, I had issues with the slave permissions that I had to fix to get the slave (shared web) to update and setup a new website. The IP was set to * for the website and it seems to have created an odd case. I have this structure: /var/www/domain.com/web/index.html the default apache page loaded, I corrected the IP on the site and the website loaded as it should. However, I also have the regular ispconfig structure: /var/www/clients/client1/web1/web/ Where things seem weird to me, was after an update to index.html both index files were updated. So I did some digging. This is what I found: ls -l /var/www/clients/client1/ lrwxrwxrwx 1 root root 30 Sep 19 19:01 domain.com -> /var/www/clients/client1/web1/ Is this symlink meant to be here? I have been using ISPC for some time and have never noticed this before. I assumed the files would be under the client path and not in a named domain path.
Yes, that's always like this since ISPConfig exists and it shows that the files are in the client path, the domain is just a symlink for easy shell navigation.
