• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Can't access the My Extensions page on Plesk 18.0.62

WSNHosting

Basic Pleskian
Server operating system version
Alma 8, 9
Plesk version and microupdate number
18.0.62
Can't access the Extensions page on Plesk 18.0.62
OS : Alma 8 and 9
Plesk : 18.0.62

can't not open Extensions

1719975241638.png

1719975293771.png

i try edit panel.ini

1719975346499.png

can open but have error

1719975426100.png

1719975484417.png

and panel.log

1719975573223.png

if use old version 18.0.31 can open

1719975676447.png

I tried deploying wget to a domain that had issues in several countries. I have the same problem.

How to fix ?
 
This Error

Uncaught Error: Minified React error #185; visit Minified React error #185 – React for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

see in website detail :

Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

now work on firefox only..
 
This problem occurs only on the first tab, causing the entire display to fail.

But you can press to access other extensions. Through other channels to display other Tabs.
 
Back
Top