Aaron McHale

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale shared this idea  · 
  2. 9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Suggestions » Databases  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale commented  · 

    In a shar ed hosting setup Plesk can force a subscription's database names and usernames t=o have a prefix.

    The problem is the prefix used for the database name is often quite long as it is based on the domain name and so there are sometimes very limited characters for the actual database name. On top of that the database username prefix that is forced is often considerably shorter and so you end up with database names and usernames that are connected to the same database but are different making it harder to keep things organised. Additionally it becomes much more difficult to describe the database using the name and makes it harder to identify what application each database relates to.

    I am proposing making it possible to use either the numeric domain, web space or subscription ID (whichever one makes most sense) as the prefix for both the database name and database username.

    This would allow for much more characters to make sensible datrabase names and ensure that the database name and username can match, all making organisation much easier.

    Aaron McHale supported this idea  · 
  3. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Usability and UI  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale shared this idea  · 
  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Suggestions » Web Applications  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale commented  · 

    Plesk has cron support, look for the Scheduled Tasks link at the top right

  6. 354 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  14 comments  ·  Feature Suggestions » Panel/Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  7. 182 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    48 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale commented  · 

    Not just frame forward, but also standard HTTP Redirect forward, this will be more important when the web moves to "HTTPS by default" as then a redirect would fail with an SSL Error.

    Additionally please make the Let's Encrypt extensions also support these.

    Aaron McHale supported this idea  · 
  8. 335 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  28 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  9. 379 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    46 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →

    We have serious doubts this function can really increase server security:
    1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
    2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.

    As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.

    As for concerns that default password requirement is set in “weak”, that fail2ban module is not…

    Aaron McHale supported this idea  · 
  10. 1,010 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  128 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  11. 35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  12. 22 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 
  13. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature Suggestions » Usability and UI  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale commented  · 

    I support this, and I'd also like to add that if you are working on multiple files it can be very annoying to have the code editor pages have to re-load when you switch tabs, it means every time you want to switch tabs you have to save the file. I would also like to see with this feature if you are editing large files not to have to scroll back to where you were every time you switch tabs.

    Aaron McHale supported this idea  · 
  14. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Suggestions » Plesk (general)  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron McHale supported this idea  · 

Feedback and Knowledge Base