Search results

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…

Hi, is there a way to restrict certain changes to the DNS-Settings for customers, who have the right to alter their DNS-zones? I'd like to mark certain entries as immutable; escpecially the NS-Records, so that the customer doesn't accidentially destroy his name resolution alltogether.

BTW, we have a system, where the directory /var/www/vhosts/default/htdocs/.well-known/acme-challenge contains several thousand files. Doesn't the extension clean up it's files after a successful validation?

The thing is, that in the documentation, the column for default value explicitly contains the string "1 day" and not just a number. I tried setting a single number, but it looks like this is invalid, or equivalent to the (mentioned) value 0, which sends a message every time.

Hi, I've got a question concerning the setting "send-notifications-interval" in panel.ini. The documentation (https://docs.plesk.com/en-US/onyx/administrator-guide/plesk-administration/managing-let’s-encrypt-settings.78586/) says the default value is "1 day", however it's not very clear on the...

Hi, according to the official Administrator's Guide (Appendix A: Ressources), the 'disk space' value in a service plan definition "includes disk space occupied by all files related to the subscription: content of websites, databases, applications, mailboxes, log files, and backup files."...

DUMP_TMP_D is set to /tmp. This value wasn't customized;this seems to be the default value. How does this fit to the above information from the official documentation, that during creation the backups are stored in /usr/local/psa/PMM/tmp/? Is the documentation out of date?