• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Resolved HTML is shown in support SSH access extension

Kaspar

API expert
Plesk Guru
Username:

TITLE

HTML is shown in support SSH access extension

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.51
CentOS 7.9
support SSH access extension 1.1.0-46

PROBLEM DESCRIPTION

Content isn't properly parsed and get shown as HTML in the license overview of the support SSH access extension.
B8ZW6xD.png

This only seems to occur on servers upgraded from Plesk .50 to .51. I am unable to replicate this issue on freshly installed servers.

STEPS TO REPRODUCE

1) Navigate to Extension Catalog
2) Install the Support SSH Access extension
3) Open the Support SSH Access extension and click the OK button to grand access
4) Click license key to expand for more information
5) Notice how the content isn't properly parsed and get shown as HTML

ACTUAL RESULT

Improper parsed content which get shown as HTML

EXPECTED RESULT

Content properly parsed and shown

ANY ADDITIONAL INFORMATION

Retrieving keys again (via Tools & Settings > License Information) 'fixes' the issue some how.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
According to developers this is a temporary issue with cached content that will automatically resolve within one day. It only affects one specific change between the .50 and .51 version and has not functional impact, plus will auto-resolve. For these reasons I have marked the thread as "resolved". If developers want to provide a fix for this cosmetic issue needs yet to be decided.
 
Back
Top