• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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