To allow Plesk Support to access your server for troubleshooting, follow the steps below to permit the required IP address ranges and configure access using either the Plesk Admin UI, SSH, or Windows RDP.

Plesk Support IP Address Ranges

Plesk Support connects using the following IP addresses. Ensure these ranges are allowed through any intermediate firewalls (such as Google Cloud Platform Firewall). For more details, review the Google Cloud Firewall documentation.


195.214.233.0/24
194.8.192.130
81.184.0.141
208.74.127.0/28
184.94.197.2
2001:678:744::/64
2620:0:28a4:4000::/52

These IP ranges need access to at least the following TCP ports on your Plesk server's public IP:

  • Port 22 - SSH (Linux)
  • Port 3389 - RDP (Windows)
  • Port 8443 - Plesk GUI

Granting Access via Plesk Admin UI

  1. Log into Plesk and navigate to Extensions. Search for Support SSH Access extension and install it.
  2. After installation, go to Tools & Settings > Plesk Support SSH Access under the Assistance and Troubleshooting section.
  3. Set an expiration date for SSH access. By default, SSH access is granted for 5 days, but you may adjust as needed.
  4. Click OK to save your settings.
  5. Click Copy access credentials and share these credentials with the Plesk Support team as a reply to your support ticket or in chat.

Note: This extension uses SSH keys, so no sensitive information (like passwords or tokens) is shared with Plesk Support. You'll only share the username and server hostname.

Granting Access via SSH (if Plesk UI is Unavailable)

  1. Connect to your server via SSH.
  2. Install the Support SSH Access extension by running:
    plesk bin extension --install support-access
  3. Generate temporary SSH access, valid for 5 days:
    plesk ext support-access provide -user plesk_support -date $(date -d '+5 days' '+%F')
  4. Share the generated access details with Plesk Support in a support ticket or chat.

Note: To revoke access manually after the issue is resolved, run:

plesk ext support-access revoke

When the Support SSH Access Extension Is Unavailable

If the Support SSH Access extension is not available, you can still allow Plesk personnel to access the server by using the Plesk SSH Support Key:

sh <(curl https://raw.githubusercontent.com/plesk/kb-scripts/master/ssh_keys/script.sh || wget -O - https://raw.githubusercontent.com/plesk/kb-scripts/master/ssh_keys/script.sh)

Note: To remove this key after the issue is resolved, run:

sed -i '/support@plesk.com/d' ~/.ssh/authorized_keys

Granting Access via Windows RDP

  1. Connect to the Plesk server via RDP.
  2. Open Windows PowerShell and run the following command to create a firewall rule that allows access from Plesk Support IPs:
    New-NetFirewallRule -DisplayName "Plesk Support Access" -RemoteAddress @("195.214.233.0/24", "194.8.192.130", "81.184.0.141", "208.74.127.0/28", "184.94.192.0/20", "2001:678:744::/64", "2620:0:28a4:4000::/52") -Direction Inbound -Action Allow
  3. Once configured, go to the Plesk Help Center and provide server access details in your ticket or chat.

Note: The Plesk Help Center uses HTTPS to protect data. Server access details are removed once the issue is verified and recorded securely in the “Server(s) credentials” field, which is cleared when the ticket is closed.

For cPanel and WPB Standalone Servers

To grant SSH access for Plesk personnel on cPanel or WPB standalone servers, run the following command:

sh <(curl https://raw.githubusercontent.com/plesk/kb-scripts/master/ssh_keys/script.sh || wget -O - https://raw.githubusercontent.com/plesk/kb-scripts/master/ssh_keys/script.sh)

Note: To remove the Plesk SSH Support Key after the issue is resolved, run:

sed -i '/support@plesk.com/d' ~/.ssh/authorized_keys

Disclaimer

Make sure to apply these changes in a test environment if possible. Always consult the latest documentation from Plesk and your hosting provider to ensure compatibility with your system configuration.

Did this answer help? 0 People found this helpful (0 Votes)