Jose A

My feedback

  1. 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 →
    Jose A supported this idea  · 
  2. 110 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  19 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  3. 218 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  4. 209 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Feature Suggestions » Mail  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  5. 2 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 » WordPress Toolkit  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
    Jose A commented  · 

    Hi,

    Now is possible "bulk remove" from WordPress Toolkit UI, but I cant´t see "bulk clone" options.

    Also I think that is useful command-line support:

    --install Installs new WordPress instance.
    --remove Remove a WordPress instance.
    --clone Clone a WordPress instance.

    Jose A commented  · 

    Yes, for example; A option to "Bulk Clone" dev.domain.com to others subdomains/domains selected (tester1.domain.com, tester2.domain.com, tester3.domain.com, tester4.domain.com, tester5.domain.com, ...)

    OK, waiting for "bulk removal" and command-line support for all ;)

    Jose A shared this idea  · 
  6. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Feature Suggestions » WordPress Toolkit  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  7. 180 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Feature Suggestions » Web / HTTP functions  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  8. 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 →
    Jose A supported this idea  · 
  9. 176 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  10. 113 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Feature Suggestions » Databases  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  11. 435 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  Feature Suggestions » Web  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  12. 46 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 » Web / HTTP functions  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  13. 51 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    open discussion  ·  7 comments  ·  Feature Suggestions » Security  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  14. 214 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Feature Suggestions » Databases  ·  Flag idea as inappropriate…  ·  Admin →
    Jose A supported this idea  · 
  15. 806 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    39 comments  ·  Feature Suggestions » Backup / Restore  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.

    Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:

    #1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)

    #2. Backup to different storages (like daily to FTP and monthly to Google Drive)

    #3. Multiple Storages of the same type (like 2 different FTP servers)

    ID in our Issue Tracker: PPM-1701
    -DL

    Jose A supported this idea  · 
  16. 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…

    Jose A supported this idea  · 

Feedback and Knowledge Base