[Bug]: Cannot start nginx and dnsmasq - password is required

[SebHanke]

Operating system version

macOS Sonoma 14.0

System architecture

ARM64 (M1, M2, etc)

Herd Version

1.3.1

PHP Version

PHP 8.2

Bug description

I have installed herd.
FPM 8.2 runs.

But nginx and dnsmasq wont start.
Logfile says for both: "sudo: a terminal is required to read the password; either use the -S option to read form standard input or configure an askpass helper"

What can i do to start the complete environment?

Steps to reproduce

No response

Relevant log output

No response

[decnorton]

We're having a similar issue when trying to run herd from a non-sudoers account. Our organisation has a requirement where day-to-day activities (i.e. web, email) must be carried out on a non-admin account. Developers can have an admin account, but must use it sparingly and not use it by default.

Installing from a non-admin account was promising: prompted for an admin username and password. When it came to running the services, the same problem occurred as above happened when trying to start the services; only affecting nginx and dnsmasq.

Ideally, we'd like to be prompted for a sudo username and password when starting the services (if sudo is required).

[thynus]

Same problem nginx won't start logged into my standard account. Works when logged in as admin.
Macbook Pro Intel macOS 12.7.1

[yocmen]

The same thing is happening to me, if the account is not an admin account you get that error in the logs

[xartuu]

I come with the same problem. The installation was successful while as a normal user you can't enable nginx, dnsmasq or php-fpm services. A super option would be to add a window to ask for the administrator password for those without privileges, as is the case during installation. Featured image:

[mpociot]

Herd cheaters a sudoers file in /etc/sudoers.d/herd

We usually target the "admin" group which by default every Mac user belongs to.
Could you check if your user is in that same group as well?

[xartuu]

For security reasons, I decided to use a separate admin account with sudo permissions to avoid sudo abuse from different applications. The user I use on a daily basis is not in the admin or sudo group and I wouldn't want him to be.

That's why I'm thinking about how cool it would be if Herd would ask for additional permissions via the admin login window when a user doesn't have enough permissions. Many users like me would be delighted with such a function.

[shackep]

I am in a similar boat as some of the others here. I am on a locked down corporate laptop. I do have sudo access, but any sudo interactions have to be prompted, but I don't get a change to provide one in herd. I am not able to start Nginx, DNSMasq or FPM.

[robertspektor]

Same issue here :/

[xartuu]

Any updates here?

[sschlein]

We've identified the problem and have a rough idea for a solution but don't know when this will be implemented

[decnorton]

We've identified the problem and have a rough idea for a solution but don't know when this will be implemented

Great that you've managed to identify it. Are you able to share details so that we may look for a potential workaround?

Separation of privileged and non-privileged accounts is a pain for us to manage as an organisation. If this could be addressed, we'd have no hesitation in purchasing Herd Pro for all of our developers.

[mpociot]

I don't think there's a workaround.
We are currently relying on the sudoers file entry and therefore execute root services, such as dnsmasq or nginx, via sudo.
We would need to modify it so that we manually check if a user is actually in the sudoers group/file or not and ask for a password if that's not the case.

I assume in your setup, the sudoers file exists, but it got written for a different user. We basically allow the herd commands for everyone in the %admin group, which your user is not a part of.