If you believe that the problem will require a Plesk Engineer to log in to your server via shell (telnet/ssh/RDP access) you may provide support with server access information. Before we can log in to your server we will require you to agree with Plesk's Server Permission Policy. This will give us permission to log in to your server and perform repairs. Issue Resolution Time is normally less for cases where customer permitted Support to access the server.
Note: For security reasons, we strongly advise that you change your passwords when submitting them to our support team. After the problem is resolved, you can then reinstate your regular passwords. Plesk Technical Staff does not retain your login information.
Providing with direct access:
Login to the Help Center and add server access as a reply to the ticket.
Note: Since help Center uses https connection, it is secure. After access to the server is verified by the support engineer, they remove the reply from the ticket and put the credentials to a special field. This field is flushed when the ticket goes to "closed" state.
Note: To provide Plesk support with direct access to Google Could server use the following article:
How to provide Plesk support with access to the Google Cloud server?
Alternatively, on Linux servers, you can avoid disclosing passwords by installing our public RSA SSH key into the list of authorized keys. You can follow these steps to properly install them:
Connect to the server via SSH
Make sure PubkeyAuthentication is enabled in SSH configuration
# grep PubkeyAuthentication /etc/ssh/sshd_config
Download our public SSH key:
# wget https://support.plesk.com/hc/en-us/article_attachments/360003621494/id_rsa.pub
Add it to the list of authorized keys on your server for the appropriate user. By default, the list of authorized keys is located in
~/.ssh/authorized_keys(home directory of the current user) For example, for
rootuser the authorized keys are located in
First, you need to make sure
~/.ssh/directory exists, and then place the key to
# mkdir ~/.ssh && chmod 700 ~/.ssh
Then, put the downloaded key to the
# cat id_rsa.pub >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys
Keys may be removed after the conclusion of the support incident.
If remote access to the server is limited with firewall, please make sure that it is allowed from Plesk Support IP addresses