Originally Posted by till
This works great
So I deleted the symlink /var/www/ispconfig and if I do: ls -la /var/www/ispconfig now it returns this:
ls: cannot access /var/www/ispconfig: No such file or directory
I suppose this is the right response. A question to understand this better. Was this symlink added during ispconfig3 installation, or how ? This is ISPConfig 18.104.22.168 (after some updates from previous versions) on ubuntu 10.04 following your tutorial: http://www.howtoforge.com/perfect-se...nx-ispconfig-3
What could have been caused If I wouldn't removed it ? cause I wouldn't have known this!
A couple of more questions/comments if you don't mind:
I mean, now I protected it with a password which for my needs right now is all I wanted, similar thing I did for the phpmyadmin. Though only I am the one to be able to access the control panel and phpmyadmin after that. So are you thinking of adding something like this or similar, as a feature in ispconfig 3 so that it uses the username and password of each account ? Or it could be done much more wise I guess. Example about phpmyadmin protection, cPanel forwards you to phpmyadmin only (I think) when logged in cPanel (or is it a hack they do on hosts ?). I don't agree when I see them hosts exposing the /cpanel url on every website like www.anotherwebsite.com/cpanel
Once Digest is better than Basic authentication (when no ssl, as I've read), why is it not the default on ispconfig or other control panels out there when for example creating a directory password protection ?
In any case, what I wanted to do is done fine and I got to thank you for this help here, and congratulate you for this amazing work you have done with ispconfig (especially version 3).