• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Search results

  1. Araoo

    Resolved SSH Acccess doesn't work

    I solved my issue using this information Unable to connect over SSH with a valid user and password: Failed password for invalid user - Thanks for your help I appreciated it!
  2. Araoo

    Resolved SSH Acccess doesn't work

    I doubled checked and it's not the case. Moreover, all usernames previously allowed are not working anymore (since we made the update) ...
  3. Araoo

    Resolved SSH Acccess doesn't work

    The user is listed, I have the following return: username:x:10006:1003::/var/www/vhosts/mydomain.fr:/bin/sh
  4. Araoo

    Resolved SSH Acccess doesn't work

    No firewall rule on port 22 ...
  5. Araoo

    Resolved SSH Acccess doesn't work

    I have an "access denied" error whereas I allowed the user to connect using ssh (I followed these article: How to give Plesk users SSH access).
  6. Araoo

    Resolved SSH Acccess doesn't work

    Hi Igor, thank you for your answer. SSHD service is up and running and port 22 is listening (I can send you I screenshot if needed).
  7. Araoo

    Resolved SSH Acccess doesn't work

    Hi there, since we updated to Plesk 17.5 none of our allowed users can use SSH ... that's wired... It was working on Plesk 12.5 ... Any help or advice will be much appreciated. Many thanks in advance. Cheers!
Back
Top