Recent content by D3nnis3n

Thank you, that is what we actually already have set. We'd personally appreciate if more configuration options would be possible, including determining the renewal schedule. I understand your concern about rate limits, but we're one of those clients you probably don't really want to see anymore...

Hello, ACME SSL notes it can renew certificates before expiration - I'd like to have it renew on the first of every month for all domains, no matter their expiration date. How can I achieve this? This used to be possible with the Let's Encrypt extension and a config setting for it in the past...

Hello, I replaced all of our certificates with ACME SSL ones today - while doing so I deleted all Let's Encrypt ones. However, one domain didn't allow deleting the Let's Encrypt certificate, as even after removing the certificate from all places (Domain, Subdomains, Web, E-Mail, IP, Plesk Panel...

That was it. Probably it shouldn't be locked behind that when it's the only option one has ...

ACME SSL doesn't appear as provider for me after installing, even after removing Let's Encrypt. Can't figure out how to make use of it.

Using a different browser seems to indeed have worked. Pretty weird, I never opened the repair kit before at all. Might rather be related to already having been logged in to Plesk when I opened it - though that is the natural result when a process in Plesk tells me to do so.

I planned to do the MariaDB upgrade to 11.8 today and as part of the process in the web ui (the last time I did it via ssh) it requires me to check that I have the repair kit opened. Unfortuately, the repair kit doesn't work, as Google Chrome just tries to connect for a while and then shows a...

Doing so causes the updating problems if you have any other repositories configured that use default accepted algorithms, so they should not do that as it breaks their clients servers ... We only updated to .70 yesterday, and it did indeed restore the Imunify sources. There is no signs of...

So we figured this one out as well. The workaround is bad. It configures: APT::Key::Assert-Pubkey-Algo ">=dsa1024,rsa4096,rsa3072"; However, this line will replace the defaults, e.g. if this is configured, what is accepted by default will no longer be accepted when it is not in that...

Just in case someone else has the same problem in the future: Create the folder "resolved.conf.d" in /etc/systemd/ and add a 99-custom.conf with the following content: [Resolve] DNS=127.0.0.1 That will permanently change the DNS to the local resolver.

_Manual_ updating never failed, the issue is the warnings are seen as error which leads to the Plesk configured automatic updates _not_ working and sending an update failed e-mail every day. It is readded on every execution of Plesk Installer.

Well, we don't - but the source files are still included in apt. The workaround noted by Plesk also doesn't help - the Imunify repositories are still considered to be in failure and as such we still get an e-mail every day noting to us that updating failed.

So a security software is not able to actually provide secure keys, despite warnings about that having been given for ages and the "in due course" is so far months since they have been made first aware? Noone should use that security software. I don't even know why these repositories are...

Imunify still shows the error.

Hello, we are also getting this issue with the Plesk Grafana extension, additional to Imunify and PHP 7.4. If you have automatic updates enabled in Plesk, you will get sent a mail noting that the updates failed every day, as these warnings are considered an error for that purpose.