Willyam Castro

> Why these particular exit codes/return values? I agree this sounds like a useful enhancement. I am just curious why you specifically mentioned 127, 128, 130 as values, _vs_ 1,...

Hi Simon, I tested now release 1.71 and error persists In container nextcloud-aio-nextcloud: ``` Next OC\DB\Exceptions\DbalException: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[08006] [7]...

Same problem in stable release 1.0.0 / 33dc5a554b496bd253bedbecc6755de514a64867. This version is used in [nextcloud-all-in-one](https://github.com/nextcloud/all-in-one) that is running ok. In nextcloud Infra HPB status: > "OK: Version running: unknown." \# nextcloud-spreed-signaling-1.0.0/bin/signaling...

> Same problem. Latest versions of conferences and signaling server. In commit cbfc96e (release stable 0.5.0) this problem does not happen. If it helps you...

The same problem in Apache with ModSecurity v3.0.4 too, test show below 

Excusme, for lack attention. Very thanks Is an equivalent directive foreseen?

The workaround with TIME_EPOCH works, but it seems not 100%. Using TIME_EPOCH sometimes receives a different value in the middle of the execution. See below: Rules: ``` SecAction "phase:1,log,initcol:ip=%{REMOTE_ADDR},id:10" SecRule...

@PeterP55P check directive "SecAuditLog" in your modsecurity.conf, in file this directive must to have all content from match rules. In logger error normally show only wich generate action the lock.

Hi @Danrancan, Although the body is not being parsed ("SecRequestBodyAccess Off") the "SecRequestBodyLimitAction Reject" directive may be causing the problem. Change the "Reject" value to "ProcessPartial" and test again. If...

I agree @vedantmgoyal2009. One option would be to for Linux can do query in WinGet repository, logically not upgrade nothing, only query and search. If the idea is valid