ISPConfig applies strict settings to every directory in /var/www that s not a website, so it might be that some of your horde settings dos not get applied or that they got negated or overridden.

Try to move the apache horde config file to /etc/apache2/sites-available/, then create a symlink in /etc/apache2/sites-enabled/ to that file, the name of the symlink should be at after the sites in alhabetical order e.g. 999-horde.conf and restart apache.

This ensures that the horde config file is loaded in apache after the ispconfig.conf and ispconfig.vhost file

Ok, so there must be something wrong with the horde code or rewrites rules, especially as this happens only on this one URL. If it would be a general rewrite issue e.g. caused by ispconfig, then no URLS in the /horde directory would work as ispconfig is not applying any rules specific to horde or one of its subdirectories.

It seems as if horde tries to rewrite to a file /var/www/horde/nag/t on the disk instead of https://cleandrum.com/horde/nag/t which then gets rewritten to a php file. You should check the .htaccess file in /var/www/horde with the horde devs, maybe there is an option that needs to be activated or the URL is rewritten in the wrong way inside that file.

Ok, so there must be something wrong with the horde code or rewrites rules, especially as this happens only on this one URL.

Click to expand...

Just to clarify - This error happens on ALL the websites and the IP, there is no difference. So that would seem to suggest that either mod_rewrite is not configured properly or I have issues with some code somewhere??

Correct?

The Horde Dev team no longer reply to this problem. Seems its too hard for them, or I'm too dumb.

Just to clarify - This error happens on ALL the websites and the IP, there is no difference.

Click to expand...

Correct, and this shows us that its a horde issue and not one inside the sjwarts website created by ispconfig. In my post above I referred to the URL inside of horde and not the domain you access horde with. If it would be a general rewrite issue e.g. as if mod_rewrite is not active like the horde devs told you, then nothing in horde would work, not even the horde login. But your problem is just a single function in horde is not working, if I understood you correctly, its just that the task manager does not work and that indicates that something in horde or in a .htaccess file in the horde install folder handles this taskmanager URL differently then the other functions in horde.

Please post the .htaccess file from horde, maybe we find something in there.

Please post the .htaccess file from horde, maybe we find something in there.

Click to expand...

Code:

# IMPORTANT: DO NOT EDIT THIS FILE!
# It will be overwritten with any future upgrade.
allow from all
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ rampage.php [QSA,L]
</IfModule>

# IMPORTANT: DO NOT EDIT THIS FILE!
# It will be overwritten with any future upgrade.
allow from all
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)$ rampage.php [QSA,L]
</IfModule>

Click to expand...

Please try to remove the following lines:

<IfModule mod_rewrite.c>

and

</IfModule>

If mod_rewrite would not be loaded, you will get a apache 500 error then.

Regarding the login error, do you remember what you changed since you logged in successfully the last time?

Ok, if the error is still the same, then the problem is not that mod_rewrite is inactive like the horde devs said. Otherwise you would get an apache error (most likely 500) that the directive RewriteEngine is invalid.

Do you remenmber what you did in the horde install which might have caused the "User [email protected] is not authorized for Horde." error? I guess this must be something in the horde user config or changing of a databse login or similar and not a change in a apache file.

And which guide did you follow to install horde on your server? Here is e.g. a guide for horde 4 on a ispconfig server, maybe you can compare your configuration steps with that guide even if you use a newer horde version: