• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question SSL It! Settings > TLS versions and ciphers by Mozilla

From my experience this list is only very rarely updated, so it does not make sense to check it regularly.
Agreed, so I'm only looking for a cron doing this every 3 months.

As far as I am aware, there are no active plans on introducing automatic sync option. If possible, please submit a request on features.plesk.com.
Thanks, but features.plesk.com is a step backwards from Uservoice. I'm discouraged to submit requests because I don't see my entry on the website, I don't see how many others have requested the same thing, and I don't appear to receive any acknowledgement as to whether it's being considered or not. Maybe this is by design?

This forum now seems like the better place for feature requests as I can post something, people can Google for it and add their support, etc.
 
Thanks, but features.plesk.com is a step backwards from Uservoice. I'm discouraged to submit requests because I don't see my entry on the website, I don't see how many others have requested the same thing, and I don't appear to receive any acknowledgement as to whether it's being considered or not. Maybe this is by design?

Thank you for the feedback. I completely understand your concern. At the moment, the process works as follows: when you submit a request, you should receive a confirmation that your email address has been verified and that the request was successfully submitted.

All submitted requests are then reviewed internally. By design, the platform we use does not publicly display requests at this stage. If a request is selected for user-demand evaluation, it is moved to the Under Consideration tab, and if it is approved for implementation, it is added directly to the Public Roadmap. In both cases, you will receive an additional notification with an update.

If there are certainly no plans for implementation of the requested feature, I follow up with the user through a support ticket to clarify that.

I realize that this isn't an ideal workflow, but, frankly, neither was UserVoice. It also generated quite a lot of complaints and didn't provide the experience we and users were looking for.
 
So, back to synching TLS versions and ciphers by Mozilla, is there a way I can set this up in a cron? Is there a CLI command or API for this?
 
Back
Top