Search results

We see the problem now for the first time also for a domain, that has no subdomains but one extra domain in the subscription, that is forwarded to it. The wildcard certificate is not renewed and ends up in a freezing state as described in the bug report ("continue" and "cancel" buttons).

We can confirm, that the problem also still exists same as mentioned in our bug report. E.g. one client wildcard certificate, that is not renewed since some days (4th of March):

Plesk Onyx 17.8.11 Update 64 is quite old (13 August 2019). What OS are you using? Maybe this one is also already end of life and the OpenSSL library is outdated to generate correct CSR's (Certificate Signing Requests).

@arupa No, there is no workaround, only a lot of manual click around. The bug also changes its behavior sometimes. Maybe because of some of the latest updates of Plesk and/or SSL It!. Here is one example scenario of an affected client (the ACTUAL RESULT is a bit different than in my bug...

OK, just in case someone needs it, here is the list (and my factorial approach was wrong ;)): ac3 aC3 Ac3 AC3 avi avI aVi aVI Avi AvI AVi AVI bmp bmP bMp bMP Bmp BmP BMp BMP bz2 bZ2 Bz2 BZ2 css csS cSs cSS Css CsS CSs CSS cue cuE cUe cUE Cue CuE CUe CUE dat daT dAt dAT Dat DaT DAt DAT doc doC...

Maybe as a little addition: the location directive does not change the filename that will be processed. So it doesn't matter what file system is used. Right now try_files is not even called because of the strict regular expression for capital letters in the extension part that forbids any match...

I think there is a misunderstanding of the problem. Files like: - MyStaticFileWithUppercaseLetters.txt are working already with the current location rule Only files with uppercase letters in the extension are handed over to Apache: - MyStaticFileWithUppercaseLetters_InTheExtension.TxT If you...

Hello @Kaspar , thanks for you annotations. The problem with the "bug free updates" we also see since over one year. In the past we did update our servers immediately - we did even activate the auto-updates option till we had some serious business incidents with our clients and broken systems or...

Hello, I did open this thread to provide and get information, if the current Plesk Obsidian 18.0.59 release is stable enough to deploy it on live systems with hundreds of clients. To make sure everything runs smoothly and risks are minimized we already have a 3-step roll-out plan, when Plesk...

Username: TITLE Smart static files processing is only working for lowercase file extensions PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.59 Update #1, Debian 11.9, x86-64, PROBLEM DESCRIPTION The "Smart static files processing" under "Apache & nginx...

For all Plesk users that want to roll-out the current release 18.0.59 #1, there is now maybe one more thing to consider. As described in this thread, the password protection for Nginx did not work at all for at least 18.0.58 and 18.0.57. As a side effect e.g. the backends of Shopware 6 systems...

Unfortunately the patch doesn't work out of the box. For the ones who ended up here asking why: you will need to manually regenerate the nginx.conf files for all affected websites in one way or another. If you are not sure how to do, the Plesk repair utility for web is the way to go.

@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...