• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Horde Webmail & VFS module

From SWSoft support:
------------------------------
It has been fixed by adding the following line into
/usr/share/psa-horde/config/conf.php:

$conf['documents']['type'] = 'horde';
------------------------------

Great!
 
Hi,

I do this and restart server, but problem is not fixed, i have always this error message. Somebody can help me ?
 
here is my conf.php

<?php
// $Horde: horde/config/conf.xml,v 1.74 2004/12/09 16:33:30 jan Exp $
/**
* Plesk predefined configuration for Horde3
**/

$conf['debug_level'] = E_ALL^E_NOTICE;
$conf['max_exec_time'] = 0;
$conf['use_ssl'] = 2;
$conf['compress_pages'] = true;
$conf['umask'] = 077;
$conf['session']['name'] = 'Horde3';
$conf['session']['cache_limiter'] = 'nocache';
$conf['session']['timeout'] = 0;
$conf['server']['name'] = $_SERVER['SERVER_NAME'];
$conf['server']['port'] = $_SERVER['SERVER_PORT'];
$conf['cookie']['domain'] = $_SERVER['SERVER_NAME'];
$conf['cookie']['path'] = '/';
$conf['sql']['phptype'] = 'mysql';
$conf['sql']['persistent'] = false;
$conf['sql']['socket'] = '/var/lib/mysql/mysql.sock';
$conf['sql']['protocol'] = 'unix';
$conf['sql']['hostspec'] = 'localhost';
$conf['sql']['username'] = 'horde';
$conf['sql']['database'] = 'horde';



// get password from /etc/psa/.webmail.shadow
if (!($fd = fopen("/etc/psa/.webmail.shadow", "r"))) {
echo "<script>alert('Unable to get webmail password!')</script>";
exit();
}
fscanf($fd, "%s", $buff);
fclose($fd);

$conf['sql']['password'] = preg_replace("/\n/", "", $buff);
$conf['sql']['charset'] = 'utf8';
$conf['auth']['checkip'] = true;
$conf['auth']['admins'] = array();
$conf['signup']['allow'] = false;
$conf['signup']['approve'] = false;
$conf['signup']['preprocess'] = false;
$conf['signup']['queue'] = false;
$conf['log']['priority'] = PEAR_LOG_ERR;
$conf['log']['ident'] = 'HORDE';
$conf['log']['params'] = array();
$conf['log']['name'] = '/var/log/psa-horde/psa-horde.log';
$conf['log']['params']['append'] = true;
$conf['log']['type'] = 'file';
$conf['log']['enabled'] = true;
$conf['log_accesskeys'] = false;
$conf['prefs']['params']['driverconfig'] = 'horde';
$conf['prefs']['driver'] = 'sql';
$conf['datatree']['params']['driverconfig'] = 'horde';
$conf['datatree']['driver'] = 'sql';
$conf['group']['driver'] = 'datatree';
$conf['cache']['default_lifetime'] = 1800;
$conf['kolab']['enabled'] = false;
$conf['menu']['always'] = false;
$conf['menu']['links']['help'] = 'all';
$conf['menu']['links']['options'] = 'authenticated';
$conf['menu']['links']['problem'] = 'never';
$conf['menu']['links']['login'] = 'all';
$conf['menu']['links']['logout'] = 'authenticated';
$conf['auth']['params']['app'] = 'imp';
$conf['auth']['driver'] = 'application';
$conf['mailer']['params']['host'] = 'localhost';
$conf['mailer']['params']['auth'] = false;
$conf['mailer']['type'] = 'smtp';
$conf['vfs']['params']['vfsroot'] = '/tmp';
$conf['vfs']['type'] = 'file';
$conf['portal']['fixed_blocks'] = array();
$conf['documents']['type'] = 'horde';
 
same thing when trying to add to addressbook in horde.

A fatal error has occurred
You must configure a VFS backend.
Details have been logged for the administrator.
 
But when I hit the mail link agian after the failure message , the entry is actually added to the address book.
 
Originally posted by albans
From SWSoft support:
------------------------------
It has been fixed by adding the following line into
/usr/share/psa-horde/config/conf.php:

$conf['documents']['type'] = 'horde';
------------------------------

Great!

Thanks, that worked for me!
 
From plesk:

Thank you for your attention and this information. This error took place, and it was fixed in a later build of Plesk 8.0. Updates woll be available soon.

Thanks,
 
Back
Top