Hi, On Sun, May 31, 2026 at 07:09:38PM +0100, Andre Rodier wrote: > I tested the socket activation, and the systemd logic is working, i.e. > it is calling the user systemd service. BUT, the user service fails to > start, because the socket is own by systemd.
I have not tried to do what you're doing, but I note that .socket units can have the options: SocketUser SocketGroup SocketMode so can these be used to create the socket with ownership of user and read/write to system nginx? I am not sure about the idea of running one nginx process per active user, about wehther that would be scalable, but I guess it is still more scalabvle than running a container or a VM per user. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
