Search results

Yep, overlooked that part. To fix it, execute the following command: ln -s /usr/share/psa-roundcube/.well-known /usr/share/custom-roundcube/.well-known That should fix it. Edited my original post to reflect the change.

Please take note that it was a quick write-up on how I did it on one of the servers I maintain. It is not meant to be a 'one-stop-shop' for all Plesk servers. I simply got bored on waiting for them releasing it. For example, it does not account for nginx-only environments (it will be easy to get...

You could export the current database of Plesk's Roundcube, import it in the new one and then use Roudcube's migration script to update the database version. Should be easy. However - I don't recommend migrating it back after Plesk's webmail maintenance is on schedule again because I don't know...

As promised, here is my setup. It does not touch any Plesk files, except ones that we are allowed to change by design. However, it's late and it is a quick write-up. Keep that in mind. Make sure you have root access on the server. If you don't know how to handle it, please, don't continue. I am...

I will check if there is a way to do that without breaking updates in the future. Expect a update later tonight or tomorrow.

Don't overwrite anything in the default Roundcube directory (/usr/share/psa-roundcube), it might break future updates! The way to go is by overriding config (templates). Make sure you backup every file (before) you touch (it).

Roundcube has been known for supporting old versions for a very long time. The current LTS version is still 1.2.9 AFAIK. This isn't even the version Plesk currently uses. I suspect 1.3 series will get LTS before 1.4 does, so this might take a very long time. Think multiple years, not month. 'It...

So it's the end of january already. Nearly 3 months went by, Roundcube 1.4.2 has been released, a big update for Obsidian has been released with the update of many third-party scripts, yet no word on this. I can imagine a proper update and testing might take some time, however, the Roundcube 1.4...

One of the domains on a server I manage is mail-only. When someone goes to webmail.{mail-only.domain} it has a non-valid cert. It seems not to be possible to attach a valid cert, as the Let's Encrypt extensions returns the error that hosting has not been enabled on this domain. This should be...

I think you're in for a tough ride as Multi Server isn't designed that way. MutliServer extension != PPA. Multi Server aims at a unified configuration using a single point of login.

@Anthony: Consider making an API for the whole Plesk mail part. Let users free to implement their own solutions.

@Anthony: Please use a solution that works on Linux. Since most linux-based mailserver packages are free, I recommend you to make a minified mail-only Plesk stack to install on the given server. Pros: Extensions like MagicSpam can still be applied. I bet many webhosters running a Plesk...

"but I think..." Currently, using the planned MultiServer feature to do this, it's only possible in the way I described first. Maintaining 2 separate servers as I do now is cumbersome and time-consuming. @Anthony: As you liked the post above, are you planning to make it possible what he...

It's always a good idea to spread server load. Offloading email, while hosting say less then 50 websites, can still be beneficial. In many ways. And my expectations are a lot of Plesk users just want it the way I describe. It's not the first time that people, mainly because my reason earlier...

For example, I like to have the mail separate from the web hosting. Doing so would cost me (as a freelancer): 1 Server for the management node (€10/m) 1 Server for the webhosting (€20/m) 1 Server for the mail hosting (€20/m) 3 Plesk Licenses (3×€11,25/m) 3 Plesk Multi Server Licenses (€3×€9/m)...

So, another vote for a small connector daemon here, keeping the Plesk Panel on the management node only. The most ideal setup I like is where service nodes only contain the services I want them to serve. So, say, if a node is a webserver, only a webserver (and MySQL if chosen) is installed on...

Ah, I understand. Can you spoil a bit of features coming in the next version?

Surprising decision. DNSSEC is important stuff, should be in the core of Plesk. With security developments evolving fast, it might get as important as secured HTTP is now on a relatively short term. This certainly isn't a niche feature, but that's my opinion. The same like having to pay extra...

Upon checking, CloudLinux support has clarified it: Docker will not run on CloudLinux due to a different kernel design, and there are no plans to support it. :(

Unfortunate. Are you planning to support it?