• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk 12.0 Preview (Windows)

Plesk 12.0.12 for Windows adds a lot of IIS optimizations. To see how faster Plesk actually works now, simply take a look at the graph below. It shows you the time it takes Plesk to create a subscription depending on how many subscriptions are present on the server already. Each subscription used for this benchmark had WordPress installed on it for more accurate measurement.

The spikes on the graph show when daily maintenance script was running, increasing server load.

PERFORMANCE.jpg

As you can see, with these optimizations Plesk 12.0.12 shows 2.5x-4x performance boost compared to 11.5.
 
Can anyone from Parallels Team tell me if mylittleadmin integration in plesk 12 for windows has been improved? Current and previous versions relie on dns record for mssql.<domin.tld> and does not use https:// connections which causes two problems. Firstly user gets warning about sending encrypted data (https://) to mylittleadmin which is only configured as http by plesk. Every time another domain is added to plesk it creates a new iis binding on port 80 so manually configuring https isn't practical.

Otherwise I've looked at the Linux version and its looking good so far. If that performance improvement in plesk 12 is reflected in wild it will be a good achievement.
 
Can anyone from Parallels Team tell me if mylittleadmin integration in plesk 12 for windows has been improved? Current and previous versions relie on dns record for mssql.<domin.tld> and does not use https:// connections which causes two problems. Firstly user gets warning about sending encrypted data (https://) to mylittleadmin which is only configured as http by plesk. Every time another domain is added to plesk it creates a new iis binding on port 80 so manually configuring https isn't practical.

Have you trested this behaviour on test Plesk 12 Preview installation?
 
You only have a live demo of the Linux flavoured plesk 12. That feature is exclusively windows... To test it I'd have to run up a windows vps, install plesk 12, then configure Mylittleadmin by hand + licence. This is non-trivial hence the question. It'd have thought, perhaps mistakenly, that it should be a fairly straight forward question for you guys to answer. Either then functionality has been improved, its in the pipe or functionality is unchanged. Cheers.
 
Hi, it didn't change in 12.0 - we still redirect to mssql.<domain>
Are you looking for https:// availability for mylittleadmin (but there will be warning anyway - no valid SSL cert)?
Or you are looking for another kind of solution?
i.e. for mail someone suggested to redirect to <domain>/webmail instead - this way SSL warning can be avoided
 
Hi, it didn't change in 12.0 - we still redirect to mssql.<domain>
Are you looking for https:// availability for mylittleadmin (but there will be warning anyway - no valid SSL cert)?
Or you are looking for another kind of solution?
i.e. for mail someone suggested to redirect to <domain>/webmail instead - this way SSL warning can be avoided

Thanks for the answer Sergey.

In reference to why I was asking;

What we were looking for was a way to avoid mssql.<domain.tld> handle as customers remove the dns record which can generate unnecessary support issues. Also if it used the server name on either a custom port or sub-folder like host/mssql then we could use https:// to avoid the "sending encrypted data over an unencrypted link" browser warning as it would then be secured by the servers wildcard certificate. If you don't have a certificate then http:// still makes sense for those people.
 
Hi there,

is Plesk 12 now available for production use and will there be support for upgrades of that release or is it intended for preview purposes only?

Thank you,

Online Solutions
 
Back
Top