Search results

@kpushkarev Sure, you have the full insights to the existing logic and which solution fits the best. I did only some blackbox testing to support a fast patch. But the location / I did not touch. It's the same syntax as before / current .59 release. If the location ~* optimization is not...

Correct if the password protection is not on the root level as it was in my example. In my posting above I did clarify it. There is always space for optimization^^

@kpushkarev Your solution is also one way to go. This part of the config file exists only for the option "Serve static files directly by nginx". I would prefer the @fallback solution with only one location directive, means without the "outer one". Here is the current buggy nginx.conf as...

We did investigate the mentioned problems deeper. Actually we are talking about two different problems, depending on your Plesk version in use. We checked some of our "older" Plesk servers with Plesk versions 18.0.58.2 and 18.0.57.3. And one test server with the latest 18.0.59. For versions...

This bug is super annoying. Since end of December we are forced nearly daily to manually create and clean-up the certificates for our hosting clients on all of our servers as otherwise warning emails are sent to our clients and/or the websites get non accessible after the certificates finally...

The whole migrator seems not to have a high priority anymore as it has a lot of serious open bugs. We stopped using it whenever possible. We did not have one single migration in the past that was ok out of the box. Data was missing, settings were not transferred, [the list is endless]. I...

This is what we are doing already. But since the latest update, the lowest value in the dropdown we can set is 3 for a mailbox in block mode. That is not enough. So how can I now set a spam level of 0 or 1 or -0.1 for a specific mailbox with spam action = "block"?

@danami Then please integrate a setting to make this feature accessible again if the server admin wants so. We have a lot of users that are using spam levels of 1 or 2 for their mailboxes and they need this values because they are under high loads of incoming spam. Our servers are configured...

@danami Our clients like to set their own spam levels. Here are the values for one of our smaller servers with 150 mailboxes: SELECT DISTINCT(`spam_tag2_level`) FROM `policy`; 1 null -0.1 7.5 2 3 0.9 -2 0 5 -1 2.5 3.5 5.5 We got already the first support tickets asking why this feature is not...

@danami Since the latest release we cannot set our own individual "Spam level" and "Spam kill level" anymore. Only the default values from the dropdowns can be chosen. Please revert this change and make the input fields editable again. Right now we can only make our own settings by editing...

@Peter Debik The affected servers have reseller licenses without direct support by Plesk. Maybe @Bobbbb has a proper license to open a ticket.

Username: TITLE SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.57 Update #5, Debian 10.13, x86-64, SSL It! 1.14.5-1856 PROBLEM DESCRIPTION Since mid of...

@kpushkarev Thanks for clearance. We did already use just "mariadb-server" as default value for our external sources. If other Plesk users are also using MariaDB repositories from the MariaDB Foundation this is the way to go (+ update /etc/apt/sources.list.d/mariadb.list before to bookworm).

@Peter Debik Maybe as an additional info: we did just test the upgrade on one of our servers having also the Imunify360 extension. The result is a broken system as Imunify360 does not support Debian 12 + Plesk yet (event though we did find a Debian 12 repository for it that was ok in the upgrade...

@Lrob Sure it is, see "Dist-upgrade from Debian 11 to Debian 12": https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk Just step 14 has a little mistake as Debian 12 is using MariaDB 10.11. and not 10.5. So just use...

Our Plesk partner did just send us the information about the new prices starting from 01/2024 onwards. For us the license costs will increase between 11 and 13% (last year between 12 and 22%). So at least the increase is slowing down. In the last months we did experience much worser price...

Docker Extension - Changelog: 1.8.1 (6 November 2023) [+] Added support for Debian 12. Maybe an early Christmas gift is on the way ;).

Afterwards it should work again.

To setup a secure Rocket.Chat instance via Plesk and Docker containers can be challenging on a beginner level. The NodeJS und FTP part is not needed at all. To help you further we need first to see your container settings for MongoDB and Rocket.Chat.

The new feature does only partly improve the situation for outgoing mails. The main problem still remains: the rules are applied for both - incoming and outgoing mails - and cannot be defined individually per direction. On top outgoing mails can only be influenced by the server wide global...