Recent content by Sofiia Kulish

Hello, @wtfred , our team released a fix for the issue with EXTPLESK-14068. That update requires no manual actions and should have been already applied. Please do let us know if you encounter any further issues.

Hello, Plesk does not roll out new major versions to all servers immediately, even when automatic updates are enabled. Instead, updates are distributed gradually in batches. This staged rollout helps ensure stability and allows Plesk to detect potential issues early before the update is made...

Hello, Thank you, @theunknownstuntman, for confirming that the issue is no longer reproducible on your side. As noted, the issue has been fixed in Plesk version 18.0.79. The changelog will be updated accordingly.

Hello, The fix has been released in Slave DNS Manager version 1.10.8. Please verify the update and let us know whether the issue is resolved on your side.

Hello, The issue has been fixed and is available in Slave DNS Manager version 1.10.8. Please let us know whether the issue has been resolved on your side.

Hello, Thank you for your patience. The ticket is currently being worked on with the highest priority. I will keep this thread updated and let you know as soon as a fix is available.

The fix has been released and will be delivered to your server within the next 24 hours. Please let us know whether the issue has been resolved or if it still persists after the update is applied. Thank you for your cooperation.

Hello, The bug has been confirmed. The ticket ID is EXTPLESK-14071.

Hello, Thank you for reporting this issue and for the information you provided. We have confirmed the bug. The ticket ID is EXTPLESK-14068. Our team is currently working on a fix with high priority.

I would suggest opening a ticket with Plesk support for an investigation of the issue on your server. To sign-in to support and open a ticket go to https://support.plesk.com. If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide...

Another possible way why the server still uses the outdated extensions version is turned off "Auto update" toggle on /modules/catalog/index.php/updates. Turn it on and run plesk daily -f UpgradeExtensions

Try to follow in browser /modules/catalog/index.php/updates Check if "Auto-update" is enabled. If it's disabled, enable it, click "Check Now" button, check all extensions and click "Update" button. If it was disabled after enabling, run one more time plesk daily -f UpgradeExtensions

To debug your issue, configure logging on your server. Add in "panel.ini editor" extension rows [log] priority = "7" Save and run "plesk daily -f UpgradeExtensions". Provide the command's response that I could determine the issue.

In case the custom catalog is used I suggest to update not only 1 extension, but all extensions using plesk daily -f UpgradeExtensions with commented custom catalog url.

Your server might use the custom extension catalog with outdated plesk extensions versions. Check the configuration parameter in the file /usr/local/psa/admin/conf/panel.ini [extensions] catalog.url In case it's present in the configuration file, comment it, update the extension using plesk...