Recent content by andre.spindler

Yes, that works as a workaround. But plesk has to fix it's release managment for packages. Otherwise we will receive an apache-3.0-alpha1 one day. And I don't want that on a production system...

We have the same with Plesk onyx. See my post there. Composer 2.0-dev was released yust two days ago. Seems we have a lousy package management of plesk here which also uses the lates version. And as where are within easter at the moment, the plesk deployment routines run actually amok. I think...

I get unexpected errors when maintaining composer based applications on my web server. Composer is now version 2.0-dev (Composer version 2.0-dev (2.0-dev+40a35abb9423e16f8bafcb1ed1b7e027881b0422) 2020-04-10 10:24:43) on Plesk onyx. When was this update published? Why do we get this update...

As this has tag "forwarded to devs": What is the current state here? Do we have to wait for argon until php7.2 has reached EOL? It was the winner of the Password Hashing Competition in July 2015, three years ago...

Is there now a scheduled date for the release of 17.8 available? I'm now waiting for more than one year to get a bug fixed by plesk. To get me right: We're talking about a bug within the implementation of a security function, not a new feature. For more than a year now. What do you do with a...

It seems like the complete firewall bahaviour is very strange, not to say weird. For now I have 307 custom rules and the default rulkes of the firewall module enabled. Altogether 332 rules are defined. But there are many rules including more than one ip range. I've counted the ip ranges and got...

TITLE: Firewall ignores some rules PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk Onyx Version 17.5.3 Update #41 CentOS Linux 7.4.1708 (Core)‬ PROBLEM DESCRIPTION: There is a set of about 300 firewall rules defined in the plesk firewall module. If I check the iptables setup. The about...

When is plesk 17.8 planned to be released? Until now this bug is only fixed in the upcoming new version (17.8), but not in the current stable (17.5). Right? What about backporting the fix to the 17.5 branch?

I want to move data from a current plesk 12.5 on centos 6 to a new server with plesk 17.5 on centos 7. On the current server I have web and mail together on one server, now I want to split. For the moment I opnly want to migrate the mails from the old one to the new. But migration fails. After...

This was first reported at https://talk.plesk.com/threads/extension-lets-encrypt-fails-with-current-apache-version.341128/, but was the wrong place... The Extension is not able to renew certificates any more. Output shows that authorization failed as there was an error 500 returned. Error log...

Just found another thread about error message when renewing a certificate: https://talk.plesk.com/threads/plesk-error-when-creating-a-lets-encrypt-certificate.341080/ But this is related to Onyx. Current extension version is 1.9.2. And there is no update available now. Removal and reinstallation...

The Extension is not able to renew certificates any more. Output shows that authorization failed as there was an error 500 returned. Error log of the domain shows: "/var/www/vhosts/xxx/yyy/web/.well-known/acme-challenge/.htaccess: Satisfy not allowed here" Yesterday I updated httpd from...

I have to reopen this again: Now the same issue again: When I want to adopt the newly modifications, I run into the same time out. Clearing the caches as suggested above does not work. I have to reboot the complete server. When I click on "Adopt changes" (? - german: "Änderungen übernehmen")...

Thanks. Together with a server reboot (due to kernel update) this helped and works now. This thread should be marked as solved (is this possible? - didn't found that).

When I want to apply the modified ruleset, I get a timeout: 504 Gateway Time-out nginx Plesk version is 12.5.30 Update #30 on CentOS 6.7 (Final)