Skip to content

Alexander Marinov

My feedback

2 results found

  1. 1,270 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Alexander Marinov commented  · 

    @nikamuro and the rest of the Pizza guys. This comparison is ridiculously narrow-minded. Let put aside that in my end of the world a pizza costs $7-ish and there are even cheaper places on the globe.

    It's narrow-minded because you *assume* one Plesk ... perhaps installed on *the* server (the one and only!). If so please read my statement again and this time carefully:

    "you are overestimating the value of Plesk if you think that the cost of a Plesk+Paid AV combo is worthy for a VPS installation."

    Hopefully this time you spotted the VPS thing at the end?

    So if you'd like to run a hosting environment in a late 90's style, with hundreds if not thousands of users on the same instance perhaps it's not a big deal. I may personally find it outdated, unsecure and hard for ensuring reliability to each and every account hosted there, but hey, it's my opinion! I won't go the route to force it to you. Please be kind enough not forcing me to discuss your pizza stuff as well.

    Let me elaborate a bit on why I do consider ClamAV mandatory and why the offered alternatives are really expensive using digits and not ... totally unrelated things.

    In my experience large organizations usually go for either 3rd party hosted service or a specialized one (i.e. I've seen Zimbra used in the wild but yet to see self-hosted Plesk for the sake of corporate email).
    Smaller ones tend to stick to more generic solutions as using a shared hosting provider. In my own version of the Matrix the need for Plesk usually emerges once an SMB starts outgrowing shared hosting's limits and start thinking for migration to a VPS. Let's assume that regardless of the needs the precise price of that VPS (or dedicated for that matter) is irrelevant - lets call it X - and try to calculate the extra spendings necessary.

    One of the first requests will usually be the need of business email which nowadays requires scanning as crypto-viruses can be devastating.
    - Plesk offer is to either buy Kaspersky for €359.88 annually (EURO guys!, not USD) which as of today gives $426.86/annually. This does not include any maintenance/support work necessary
    - Hosted email goes $2-$5 per user monthly. As this is a 3rd party service so it won't have maintenance/support costs.

    Math says that GSuite is cheaper for up to 7 users, and e.g. Zoho is cheaper for up to 14 users. And this only considers price parity, not feature parity! I'm afraid that GSuite vs Plesk as email solution is a lost cause under those conditions. In my experience people are more likely to trust (and hence pay) Google/Zoho rather than an unknown solution. I'd personaly bet on $5 that one is more likely to convince people to spend 2x on GSuite that on AV for Plesk.

    Now let's shortly discuss the point where I can actually integrate ClamAV myself. Or why I rather won't:
    - Integrating things in a product which development cycle you don't control is extremely risky. At any point an upgrade can break something.
    - The effort of doing this properly is comparable to that of writing (or adopting) a provisioning recipe to deploy a mail server + Roundcube
    - I won't have any ot the cumbersome restrictions that I need to fight in Plesk (custom SSL cert for IMAP (unless they fixed it)? HSTS? 2FA? Good lucck on the last one in Plesk)
    - It will operate in it's own environment hence the reliability won't depend on Plesk's (but rather on your skills to set it properly)

    So with that in mind I'd personally rather use 3rd party or custom bult setup. It does involve some effort yes, but my experience so far with Plesk is hardly flawless as well.
    - Had to reinstall and convert to cloudlinux as Plesk's Cgroups were buggy - 500% CPU limit would have still translated into one core (it seems they fixed this later on)
    - Had to write a custom script to synchronize the Secondary DNS as the plugin suddenly became buggy and stopped doing that (I'm not kidding at all: https://pastebin.com/YYGnXiqg, also was fixed at some point but in the day it costed me few hours to debug/workaround)

    With that in mind any customization is a no-go for me and I would not recommend it to anyone else as well.

    Well hopefully this is enough for my POV to become clear, not that it matters for me. I don't think anything will happen here (and in the "admin" name request as well) so took the effort to unsubscribe from notifications.

    Wishing good luck to everyone regardless of your opinions on that particular topic.

    Cheers

    An error occurred while saving the comment
    Alexander Marinov commented  · 

    I don't know why we still comment on this. It should be obvious by now that this "feature" was chosen for monetization if one wants to feel more secure :)

    So dear plesk team, yes we can integrate ClamAV on our own but then what is the benefit to pay for a "solution" if this requires additional effort to steup and *maintain*?!

    If I'd like to go that route then I'd rather go fully self-managed than start hacking trough an encrypted 3rd party software. Thanks, but no thanks.

    And IMO you are overestimating the value of Plesk if you think that the cost of a Plesk+Paid AV combo is worthy for a VPS installation.

    Alexander Marinov supported this idea  · 
  2. 236 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Current scope for Plesk Onyx is to enable an ability to serve all http(s) requests by Nginx only.

    Note: apache will still be installed. Switching of apache to optional component is subject for the next release.

    Update:

    The ability to turn off Apache and have content served by nginx only on a per-website basis is now available in the latest Plesk Onyx 17.0.14 preview. We encourage you to check the implementation and let us know what you think. Please visit the following forum thread to learn how to access the preview: https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172

    How to try this feature:

    Go to any website, click Apache & nginx Settings and deselect the “Proxy mode” checkbox under nginx settings. The feature is also available in Service Plans.

    We would appreciate hearing your feedback on implementation of this functionality. Thanks in advance!

    —AK

    Alexander Marinov supported this idea  · 

Feedback and Knowledge Base