Search results

That latency being at least 15+ minutes, while executing stats doing it correctly immediately seems odd to me. In any case, it feels like something here is no longer working correctly since early march. None of what I saw today has been an issue before.

Interesting. So I can reproduce the following on my instance: logrotate command does visibly only empty the file, nothing else. Only when I execute /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=<mydomain> the rotation actually happens. So If i execute logrotate three times...

So, I have no idea what I'm actually doing, but executing /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=<mydomain> does correctly rotate the logs? You can now see the previously vanished big logs that were rotated into packaged files (100 MB and 75 MB). How is that even...

I just tried the "logrotate -f /usr/local/psa/etc/logrotate.d/<domain name>" way you had mentioned in your post, the error_log was removed, but not rotated. It's just been emptied. Weird. Maybe that was a problem due to it having become so big, but I see that my access_log also has not been put...

Here is a screen, actually only the access_log was rotated when doing the fix mentioned by Peter. The error_log doesn't rotate on manual either.

I can confirm this is the case, I just noticed this today as well while working on a MediaWiki Update, the error_log wasn't rotated since early march and has gotten to a sizeable 6 GB. The same was true for access_logs, which is at 1.2 GB. And php-fpm_error.log as well. Manual logrotate worked...

Yeh, their algorithm is horribly broken: https://talk.plesk.com/threads/password-security-secure-does-not-recognize-a-secure-password-as-secure-but-as-medium.358283/

Oof, that algorithm seems broken beyond repair.

Brute-Force attacks are effectively stopped by not allowing them, not by longer passwords. If you allow someone to test a million passwords without stopping him, that's a totally different issue. For normal users requiring them to use that long passwords does simply not work and is not required...

Yes, it's confusing, we've now set security to Medium, as we couldn't enter passwords otherwise. For all low-security cases we use passwords that fulfill exactly the current description of 'secure' and those are definately not crackable in 7 minutes. Unfortunately with 'secure' they cannot be...

User name: D3nnis3n TITLE Password security "secure" does not recognize a secure password as secure but as 'medium' PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.30, Ubuntu 20.04.1 PROBLEM DESCRIPTION Kl1#-3zL (for example) is not recognized as a secure password but...

Yep, is working for me as well, but the installer does no longer present it. Last time i installed Plesk it was in the list while installing.

Hello, it seems the Docker extension is not yet available for Plesk used on Ubuntu 20.04? Is this correct? Is there an ETA when this will be available?

Actually, they did renew, just an hour later as it does UTC. Well, it works without SSLit, so i'm throwing that plugin out.

Sorry cepesh, i saw this post too late - i have since removed SSLit completely in the hope renewal would work again today. Unfortunately it seems like it hasnt tried renewing the wildcards today at all, e.g. no error no success. Only non-wildcards have been renewed. Earlier this worked just fine...

Hello cepesh84, i've already done these steps (as mentioned in the OP) several times, the issue persisted through any renewals nontheless. These workarounds / fixes are ineffective, removing the orders will lead to the renewal failing with the same error the next time it's supposed to be renewed...

Thanks, i tried. Given everything implies that this should work and i cannot get it to work on a new Plesk instance either, i have hopes devs might find something.

Having the same issue. The old Let's Encrypt certificate can be kept, but no new can be received.

User name: D3nnis3n TITLE Let's Encrypt wildcard cartificates cannot be renewed automatically PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.28 Update Nr. 3, Ubuntu 18.04.4 LTS, AMD64 PROBLEM DESCRIPTION When activating the auto-renewal of Let's Encrypt Wildcard...

So, how can i report a bug to Plesk? Typically a staff guy watched the threads and created one on their own, but they didn't this time.