Facebook
Twitter
-
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.
Important Repair Kit Extension
- Thread starter Ruslan Kosolapov
- Start date
-
- Tags
- bandwidth repair kit request
Spoiler:
And a technical detail about this: Repair Kit doesn't form these messages, it receives the messages from plesk repair CLI utilities. Thats why we can't, for example, provide here a link to the subscription - Repair Kit extension has no idea what the error message states. Also, to get this little improvement you need Plesk 17.9.
Hi.
We’ve released Repair Kit 1.1.0: Repair Kit - Plesk Extensions
The main features of the release are Disk I/O and improved filters in the Process List module.
Changes:
1.1.0 (19 February 2019)
We’ve released Repair Kit 1.1.0: Repair Kit - Plesk Extensions
The main features of the release are Disk I/O and improved filters in the Process List module.
Changes:
1.1.0 (19 February 2019)
- [+] The extension now collects disk I/O data and shows it on the process list.
- [+] Added the "Exclude root"/"Exclude SYSTEM" filter on the process list, which hides system's power user processes.
- Improved the extension's interface by fixing a number of UI/UX issues.
- [-] Added the notification shown if Repair Kit could not fix all detected issues and they must be fixed manually. (EXTPLESK-584)
- [-] If "Auto-update of resource usage" is turned on, the selected page is now kept after the process list was refreshed. (EXTPLESK-668)
Hi.
We’ve released Repair Kit 1.2 (Repair Kit - Plesk Extensions)
There is a new feature: MySQL Process List. This is Beta version of the feature (the whole extension is stable, but this particular feature is beta) – we decided to release it earlier to get feedback as soon as possible, so, there can be issues (especially with old MySQL versions or with MySQL-compatible software like Percona Server and so on). For now, the feature is free.
Also, there are UX improvements.
We’ve released Repair Kit 1.2 (Repair Kit - Plesk Extensions)
There is a new feature: MySQL Process List. This is Beta version of the feature (the whole extension is stable, but this particular feature is beta) – we decided to release it earlier to get feedback as soon as possible, so, there can be issues (especially with old MySQL versions or with MySQL-compatible software like Percona Server and so on). For now, the feature is free.
Also, there are UX improvements.
I just installed and ran the check of the repair kit extension and it shows something like this
There are incorrect permissions on some items: /etc
There is incorrect ownership on some items in the WWW root directory of the domain
What is this?
I want to know exactly what files are affected and how they would be corrected.
Automatic repairs without showing what would be done may break some functionality.
If a check tells me about "some items" that makes me frown.
The check needs to know what is affected and how and I want to know it too before I run some obscure repair function.
There are incorrect permissions on some items: /etc
There is incorrect ownership on some items in the WWW root directory of the domain
What is this?
I want to know exactly what files are affected and how they would be corrected.
Automatic repairs without showing what would be done may break some functionality.
If a check tells me about "some items" that makes me frown.
The check needs to know what is affected and how and I want to know it too before I run some obscure repair function.
