Recent content by erick85

This probably does not apply to (still) older versions.

I received an answer that it's not a bug, I had to update it and not discuss it.

I have a new license system, I also tried the old one. I don't know if contact is possible because the license is lifetime.

I use 1.646 and it works for half a year. Suddenly it stops. I don't feel like updating DA, I want to use the version of my choice (this is the last version that supports suPHP).

I use DA version 1.646 on my servers. This is my conscious choice, I don't want to update DA. Why did you block me from using this version? How can I restore it? Now the message is displayed:

Did you somehow manage to solve these problems?

Backup.

After the update, I cannot set limits per user, why? I restored exim.pl and it works. There are a lot of differences between the current version. E.g. something like this:

If you can't update mysql now, it's very likely that you won't update php in the future.

I had to downgrade DA and after this operation I have wrong dates (eg 1968). Despite re-updating the date is still wrong (on the server it's correct). Do you have an idea what is the cause?

I use lifetime license, without propack. I don't need subscription solutions, I want to pay once and have it for life :)

No.

I am looking for a person who will implement on the server: 1) PHP version change plugin for more than 4 versions. 2) limiting cpu/ram cgroups for PHP FPM.

Close, reason was out of hdd space :)

I wanted to install on the server (centos 7, updated) PHP 7.4. After doing ./build update & ./build php I get the error: What could it be caused by?