bt90

The limit got raised to a generous value of `512` in https://github.com/caddyserver/caddy/pull/1825 in order to solve https://github.com/caddyserver/caddy/issues/1723. But it's still possible to hit the limit due to misattribution of other...

The problem is that the numeric UID of the caddy user happens to overlap with one or more users inside Docker containers. On my host, the `caddy` user has the...

The limit seems to include threads as explained in [setrlimit(2)](https://man7.org/linux/man-pages/man2/setrlimit.2.html): > The maximum number of processes (or, more precisely on Linux, threads) that can be created for the real user...

The main offender in my case is the [browserless/chrome](https://hub.docker.com/r/browserless/chrome) container. ```sh docker top playwright-chrome o user,uid,pid ``` ``` USER UID PID caddy 999 2654461 caddy 999 2654495 caddy 999 2654496...

@francislavoie the following systemd documentation PR describes the situation very good: https://github.com/systemd/systemd/pull/23242

Note that users would still able to work around it using `systemctl edit caddy`.

We could also simply drop `LimitNProc` to be honest.

The change is mostly semantic as it groups the input elements in a form to tell the browser that they belong together. The benefit is that things work the way...

We could also go one step further and allow the user to submit the form without having javascript enabled. But that would require changes to `/login` endpoint in the backend...

The best way would probably to handle the POST of the form in `/` and get rid of `/login`: ```html ```