Search results

I really wonder why it takes so long. The differences between Ubuntu 16 and 18, and between 18 and 20 are much less significant, than the ones from 14 to 16 (with the whole shift to systemd), and yet they were much quicker to provide a dist-upgrade-path at that time.

Thanks, that's useful. How old is the file? I noticed, that on some of our systems the file contians the parameters SSL_PROTOCOLS and SSL_CIPHERS, which aren't present in your file. Does anybody know if these are the settings for the autorinstaller web-interface (Port 8447), or for Plesk itself...

Hi, I'm looking on information on the file /root/.autoinstallerrc on Linux systems. Is there a documentation, on which parameters are possible in this file, and what exactly they control.

How can there be comments on a guide that is yet to be published? Are there some previews available? If so: where?

Irrespective of the question how useful it is: Is it possible to do it?

Hi, is there a way (database entry, panel.ini, special file), to force a minimum Password Strength Policy, for a system. I'd like to restrict the administrator to be only able to select between "strong" and "very strong" in the interface.

Today(?) the version 18.0.26 was released, and what should I say? It's the same situation again! Are custom skins even welcome? :(

BTW, I created a feature request on Uservoice, for a skin auto-update mechanism: Implement an Auto-Update function for Skins If you like the idea, you can vote there…

Did you try plesk bin admin --disable-access-domain

We would like to provide a webmailer for the Plesk-Standard-Domain (webmail.<plesk-domain>). Is there a way to achieve this without creating the Standard-Domain as a separate subscription? Since Obsidian it's possible to let Plesk listen on Port 443 (Thanks to plesk bin admin...

It's basically the same situation, like with the skins… It would be really nice, if the Skins contained some sort of auto-update mechanism. Like providing a download-URL inside of the meta.xml and with every update, the installer checks if there is a newer version available. This way it would...

DM? I already edited the skin for the new version… The element, which was the class .page-sidebar-wrapper in the previous version became .pul-layout__sidebar-inner in the new one… just had to add the class to the CSS. But why is it even necessary to change the classes with each version?

I'm a bit frustrated currently… I just installed the new Update to 18.0.24 on one of our systems and had to realize, that our company's skin is broken… again! :mad: What's up with the plesk developers/designers? Previously we had a skin, which worked perfectly in Plesk 17. It looked always the...

The meta.xml file is okay. The problem exists since upgrading to 18.0.23 I guess. Maybe it has something to do with this entry from the changelog: "Updating a Plesk instance using a custom skin to Plesk Obsidian no longer results in a broken skin. Instead, the custom skin is replaced with the...

Hi, is there a way to define a standard skin? Since a few versions, everytime our Obsidian Installations do a nightly Microupdate, the branding theme gets reset to the "default" skin. We always have to check all of our systems to manually change the skin back to our company branding (plesk bin...

Are there any updates on this matter? Ubuntu 16.04 will get EOL in about one year, so it should be about time to start planning the dist-upgrades now, which can't be done as long as there is no upgrade-path from Plesk.

Same Problems on Ubuntu (16 LTS & 18 LTS)

What kind of support is this? There is still no PHP 7.4 installation package in plesk installer, even though it's the latest version.

Hi, we need to change the ports bin9 is listening on on a Plesk-System. This applies to both, the DNS-Port (53) and the RNDC-Port (953). In the file /var/named/run-root/etc/named.conf there is a special section for custom directives, however bind doesn't allow to overwrite already existing...

Nobody an idea on this? Maybe as an extension…