Open bkmystim opened 1 year ago
Did you manage to solve this problem? The only thing I can think of is that something else is now bound to that port at login time when the service tries to start (given sudo brew services start stubby
) works later..... but that is a guess.
Hi Sara, thanks for your reply.
After rebuilding the launch services database, I even got "permission denied" when trying to start stubby via terminal. Thus the only way for me now is to use "sudo" to start stubby (for command line and brew service).
I'm not too happy to have stubby running as root, but since I couldn't figure out a different solution . . .
I can still only try to guess what caused the problem. (OSX 12.6.2 update? Homebrew update?, ??)
So I'm still open to any advice ;-)
OK - I think I am seeing the problem too and am a bit baffled at this stage. I'll have to try to dig into this but can't see an obvious cause at the moment....
Hi guys, im on a Apple M1 with OSX 12.6 Monterey using Homebrew.
I used to have stubby running as a daemon with brew services. For some unknown reason it stopped working yesterday. I added the logging option to the "homebrew.mxcl.stubby.plist" and got the following error:
[11:14:09.736549] STUBBY: Stubby version: Stubby 0.4.2 error: Could not bind on given addresses: Permission denied
with "brew services list" I get:
stubby error 256 user ~/Library/LaunchAgents/homebrew.mxcl.stubby.plist
and with "brew services info stubby":
stubby (homebrew.mxcl.stubby) Running: ✘ Loaded: ✔ Schedulable: ✘
I can run stubby from terminal and I can start brew services from root via "sudo brew services start stubby". But no luck to get it running again as a homebrew service at user login.
Any ideas how to fix this? THX