• 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.

Question How to publish webmail access under plesk server domain like plesk.domain.tld/roundcube?

Hi Igor.

Thanks for the fast reply. I actually read a few of those posts. But the main difference with those cases is that i'm trying to use the Plesk URL and not a client URL.
But from the post you send me. I think the idea of use a symlink should work.

ln -s /usr/share/psa-roundcube /var/www/vhosts/plesk.domain.tld/httpdocs/roundcube
ln -s /usr/share/psa-horde/ /var/www/vhosts/plesk.domain.tld/httpdocs/horde

Now the question is how to correctly redirect the clients webmail record to the correct https URL.

The idea is :
if client has horde as webmail then webmail.client.tld redirects to https://plesk.domain.tld/horde
if client has Roundcube as webmail then webmail.client.tld redirects to https://plesk.domain.tld/roundcube

On the same post you send they seem to be doing something similar, but on the same client domain, not to the server domain.
 
the idea of the symlinks opened a new whole issue..

On test now i get (I hided the domain):
AH00037: Symbolic link not allowed or link target not accessible: /var/www/vhosts/plesk01.domain.tld/httpdocs/horde

I already modified the site configuration.
I added :
Options +FollowSymLinks -SymLinksIfOwnerMatch

And also fixed the symlink owner just in case.

I had also set open_basedir to:
{WEBSPACEROOT}{/}{:}{TMP}{:}{/}usr{/}share{/}psa-horde{/}{:}{/}usr{/}share{/}psa-roundcube{/}

Any ideas?
 
Back
Top