Hi, Not sure if anyone else is having these problems, but it seems that many of the features in ISPConfig 3.0.4.1 have to been done in a different, custom way...features not working. 1. Folder Protection - I am assuming this is supposed to possibly create an .htpasswd file? Generally the password is auto encrypted. This of course can be generated from numerous websites. I tried file protection in ISP and only get either 500 internal server error or it simply doesn't protect. 2. Set backups (folder zip daily, weekly, monthly). Every website on all three servers using ISPConfig 3.0.4.1 writes a folder or two and that's it. Example, I opened a back-up zip that was a wordpress site and it copied wp-content without themes, plugins...only uploaded images! Joomla site...same essential problem. 3. Trying to use suPHP causes 500 internal server error with any website stating "index.php" is smaller than min_uid" After Googling this, most recommendations were to set the uid to 0 (although don't leave it here). Just check and this should let it work. Tried everything...no go for suPHP...500 internal server error no matter the configuration. 4. Redirect option does not work....500 internal server error. Tried using full URL extension with and without http:// also with and without trailing / Then tried just the extension with and without first and trailing / Then I tried all of these with flag none, R, L, and both R & L. Internal Server error 500. What's going on with ISPConfig? I have clients dropping like a rock because they can't use any features at all. Regarding redirect, I had to code into index.php or index.html to force the redirect. Besides setting up the site (hoping all they require is plain CGI php) having a file system and access to phpMyAdmin, nothing really works. I have three servers now with ISPConfig 3.0.4.1 and they all have precisely the same issues stated above. Any suggestions? Man I do not want to lease cPanel, but ISP is always bugged or not working in some fashion or another.
These are all installation and configuration problems of your servers and no ISPConfig bugs, thats why nobody else reports them and why they are not listed in the bugtracker. We would have been be able to help you if you post the 500 error messages. 1) Post the exact error. 2) Seems as if you uploaded the files with the wrong user or that you selected the wrong PHP mode for the website. Files ahve to be owned by the web user and client group, thats automatically the case when you upload them with FTP. If you upload them with ssh as root user, then you have to chown them afterwards. The website settings for PHP based cms systems have to be: php mode: php-fcgi Suexec: on See Description in ISPConfig manual. 3) Thats a setting of the Linux distribution that you have choosen, not from ispconfig. Beside that, you should not use suphp for php based cms systems like joomla, wordpress, drupal etc. See 2) for the php settings that shpuld be used. 4) Post the exact error message from the error.log of the website. Just a general note, the most stable and recommended distribution for ISPConfig is Debian. So for production systems you should use Debian or Ubuntu as recommended on ispconfig.org website.
Till, If the error logs showed anything note-worthy, I would have. I wasn't even receiving mail logs for Dovecot auth problems until I completely circumvented ISPConfigs set-up. Although unfortunate, the mail system works great with ISP out of the picture. Tried this AM to set-up and FTP for this client (dropped the file manager, dropped the database, dropped DNS, the whole nine yards) cleaned the overhead in isp's db and mysql db, started all over. Craetion of FTP user doesn't work, so I added a temp user shell to transfer files. Can't login. Can go straight to file manager (the new one) as root. Know the DNS is right. Not a server config problem. This thing is iron clad. I can operate the whole thing with shell commands all day and night, but this helps users zero. They would even know what Putty was!
