• 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.

Mail tab hangs on Chrome browser

tristans

Basic Pleskian
the "Mail" tab (to configure mail accounts in the https://[IP]:8443/smb/admin-home control pannel) now hangs Chrome browser.

this seems to be an issue the started a few days ago on the most recent version of Chrome.

this is quite annoying.

no such problem with FF.
 
yes, the problem occurs with
Chrome 11.0.696.60 unknown

it seems to also cause problem with Plesk 9.0.1 CP
 
oh ok.

---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE\
10.2.0 on CentOS 5 x86 64-bit

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
the "Mail" tab (to configure mail accounts in the https://[IP]:8443/smb/admin-home control pannel) now hangs "Chrome 11.0.696.60 unknown" browser.

ACTUAL RESULT
hangs after clicking the "Mail" tab (to configure mail accounts)

EXPECTED RESULT
display control pannel to configure mail accounts

ANY ADDITIONAL INFORMATION
i was also unable to sign-in a plesk 9.0.1 CP with Chrome 11

no problems with FF
--------------------------------------------------------------
 
Thank you for report and cooperation. I have forwarded it to developers.
 
thanks.

in the meantime, until this is fixed, a workaround is to use Firefox.

oh, i forgot to mention: the machine that i run the browser on is a Windows XP SP3 (x86)
 
Hm.. The problem is not reproduced on my Chrome 11.0.696.68 (Windows7)

Tristans,
Could you try it again? may be it was a kind of Chrome bug that is already fixed?
 
Back
Top