Won't start?

[seanchasprod]

Hi,
Attempting an install via the lovely new program but when it runs terminal it can't install home brew as it seems to think I'm not administrator... think I am? Same for python I think
Johnny
setup.log
setup.log

[seanchasprod]

launch.log

[DozaVisuals]

Hi Johnny — thanks for the logs, they make the cause clear.

The error from Homebrew's installer is this line:

Need sudo access on macOS (e.g. the user jonathanwhite needs to be an Administrator)!

That's not Doza Assist refusing — it's macOS itself reporting that the account you're logged into (jonathanwhite) is a Standard user, not an Administrator. Homebrew has to write into /usr/local (or /opt/homebrew) which requires admin rights, and the same is true for installing Python afterward, which is why both phases fail.

A couple of ways forward:

Option A — Promote your account to Administrator (easiest if it's your own Mac)

1. System Settings → Users & Groups
2. Click the (i) next to jonathanwhite
3. Toggle on "Allow this user to administer this computer"
4. You'll need to enter an existing admin password, then log out / log back in
5. Re-launch Doza Assist

Option B — Have an admin install Homebrew once
If you can't change your account type (e.g. work-managed Mac), ask whoever has the admin account on this Mac to log in once and run:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

After that, switch back to your account and relaunch Doza Assist — it will pick up the existing Homebrew install and continue with Python/ffmpeg/Ollama on its own (those don't need admin once Homebrew is in place).

Option C — IT-managed Mac
If this is a work computer with MDM, your IT team will need to grant admin or pre-install Homebrew. There's no way for the app to bypass this — macOS won't let any installer write to system paths without admin rights.

Let me know which situation applies and I can help further.

[seanchasprod]

Thanks Chris, it’s my own machine so I assumed I was admin!! I’ll fix it :)JSent from my iPhoneOn 16 Apr 2026, at 18:24, Chris Cardoza ***@***.***> wrote: Hi Johnny — thanks for the logs, they make the cause clear. The error from Homebrew's installer is this line: Need sudo access on macOS (e.g. the user jonathanwhite needs to be an Administrator)! That's not Doza Assist refusing — it's macOS itself reporting that the account you're logged into (jonathanwhite) is a Standard user, not an Administrator. Homebrew has to write into /usr/local (or /opt/homebrew) which requires admin rights, and the same is true for installing Python afterward, which is why both phases fail. A couple of ways forward: Option A — Promote your account to Administrator (easiest if it's your own Mac) System Settings → Users & Groups Click the (i) next to jonathanwhite Toggle on "Allow this user to administer this computer" You'll need to enter an existing admin password, then log out / log back in Re-launch Doza Assist Option B — Have an admin install Homebrew once If you can't change your account type (e.g. work-managed Mac), ask whoever has the admin account on this Mac to log in once and run: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" After that, switch back to your account and relaunch Doza Assist — it will pick up the existing Homebrew install and continue with Python/ffmpeg/Ollama on its own (those don't need admin once Homebrew is in place). Option C — IT-managed Mac If this is a work computer with MDM, your IT team will need to grant admin or pre-install Homebrew. There's no way for the app to bypass this — macOS won't let any installer write to system paths without admin rights. Let me know which situation applies and I can help further. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[seanchasprod]

Just tried on my laptop which says I'm admin but got the same error?? I've a feeling I'm admin on my mac studio too... Johnny

…

On Thu, 16 Apr 2026 at 18:32, Jonathan White ***@***.***> wrote: Thanks Chris, it’s my own machine so I assumed I was admin!! I’ll fix it :) J Sent from my iPhone On 16 Apr 2026, at 18:24, Chris Cardoza ***@***.***> wrote:  Hi Johnny — thanks for the logs, they make the cause clear. The error from Homebrew's installer is this line: Need sudo access on macOS (e.g. the user jonathanwhite needs to be an Administrator)! That's not Doza Assist refusing — it's macOS itself reporting that the account you're logged into (jonathanwhite) is a *Standard* user, not an *Administrator*. Homebrew has to write into /usr/local (or /opt/homebrew) which requires admin rights, and the same is true for installing Python afterward, which is why both phases fail. A couple of ways forward: *Option A — Promote your account to Administrator* (easiest if it's your own Mac) 1. System Settings → Users & Groups 2. Click the *(i)* next to jonathanwhite 3. Toggle on *"Allow this user to administer this computer"* 4. You'll need to enter an existing admin password, then log out / log back in 5. Re-launch Doza Assist *Option B — Have an admin install Homebrew once* If you can't change your account type (e.g. work-managed Mac), ask whoever has the admin account on this Mac to log in once and run: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" After that, switch back to your account and relaunch Doza Assist — it will pick up the existing Homebrew install and continue with Python/ffmpeg/Ollama on its own (those don't need admin once Homebrew is in place). *Option C — IT-managed Mac* If this is a work computer with MDM, your IT team will need to grant admin or pre-install Homebrew. There's no way for the app to bypass this — macOS won't let any installer write to system paths without admin rights. Let me know which situation applies and I can help further. — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44QL7RZMKISF3UI2RIXGAD4WEJLVAVCNFSM6AAAAACX3WWU2WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJZGA4TGMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Seanchas Productions* Medical Centre, Main Street, Ennistymon, Co. Clare 087-2351985

[DozaVisuals]

Ah, that confirms it — the error message is misleading. Sorry about that. Here's what's actually happening:

Doza Assist runs the Homebrew installer with NONINTERACTIVE=1 so it doesn't have to prompt you in a Terminal window. In that mode, Homebrew refuses to run unless sudo works without asking for a password — which it normally never does, even for admins. So even though you ARE an admin, Homebrew bails out and reports the (confusing) "needs to be an Administrator" message.

The fix is to install Homebrew yourself once, in Terminal, where you can type your password normally:

1. Open Terminal (Applications → Utilities → Terminal, or Spotlight: ⌘Space → "Terminal")
2. Paste this and hit Return:

   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
   

3. When it asks for your password, type it (you won't see the characters as you type — that's normal) and hit Return
4. Wait a few minutes for it to finish
5. Relaunch Doza Assist — it'll detect Homebrew is already installed and continue with Python/ffmpeg/Ollama

Do this on both the laptop and the Mac Studio if you want it on both.

This is a Homebrew-side limitation rather than something Doza Assist can sidestep automatically — I'll look at improving the error message in the app and possibly switching to an interactive Terminal handoff so future users don't hit this. Thanks for surfacing it.

[seanchasprod]

Thanks for the detailed responses :) looking forward to using it :)Sent from my iPhoneOn 16 Apr 2026, at 18:56, Chris Cardoza ***@***.***> wrote: Ah, that confirms it — the error message is misleading. Sorry about that. Here's what's actually happening: Doza Assist runs the Homebrew installer with NONINTERACTIVE=1 so it doesn't have to prompt you in a Terminal window. In that mode, Homebrew refuses to run unless sudo works without asking for a password — which it normally never does, even for admins. So even though you ARE an admin, Homebrew bails out and reports the (confusing) "needs to be an Administrator" message. The fix is to install Homebrew yourself once, in Terminal, where you can type your password normally: Open Terminal (Applications → Utilities → Terminal, or Spotlight: ⌘Space → "Terminal") Paste this and hit Return: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" When it asks for your password, type it (you won't see the characters as you type — that's normal) and hit Return Wait a few minutes for it to finish Relaunch Doza Assist — it'll detect Homebrew is already installed and continue with Python/ffmpeg/Ollama Do this on both the laptop and the Mac Studio if you want it on both. This is a Homebrew-side limitation rather than something Doza Assist can sidestep automatically — I'll look at improving the error message in the app and possibly switching to an interactive Terminal handoff so future users don't hit this. Thanks for surfacing it. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[seanchasprod]

Seems to be setup but not launching..

…

On Thu, 16 Apr 2026 at 19:02, Jonathan White ***@***.***> wrote: Thanks for the detailed responses :) looking forward to using it :) Sent from my iPhone On 16 Apr 2026, at 18:56, Chris Cardoza ***@***.***> wrote:  Ah, that confirms it — the error message is misleading. Sorry about that. Here's what's actually happening: Doza Assist runs the Homebrew installer with NONINTERACTIVE=1 so it doesn't have to prompt you in a Terminal window. In that mode, Homebrew refuses to run unless sudo works *without* asking for a password — which it normally never does, even for admins. So even though you ARE an admin, Homebrew bails out and reports the (confusing) "needs to be an Administrator" message. *The fix is to install Homebrew yourself once, in Terminal, where you can type your password normally:* 1. Open *Terminal* (Applications → Utilities → Terminal, or Spotlight: ⌘Space → "Terminal") 2. Paste this and hit Return: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" 3. When it asks for your password, type it (you won't see the characters as you type — that's normal) and hit Return 4. Wait a few minutes for it to finish 5. Relaunch Doza Assist — it'll detect Homebrew is already installed and continue with Python/ffmpeg/Ollama Do this on both the laptop and the Mac Studio if you want it on both. This is a Homebrew-side limitation rather than something Doza Assist can sidestep automatically — I'll look at improving the error message in the app and possibly switching to an interactive Terminal handoff so future users don't hit this. Thanks for surfacing it. — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A44QL7T356JFQG4ILA5G4YD4WENGPAVCNFSM6AAAAACX3WWU2WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJZGE2DSNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Seanchas Productions* Medical Centre, Main Street, Ennistymon, Co. Clare 087-2351985

[DozaVisuals]

Glad you got Homebrew installed! The logs you attached look like the same ones from yesterday (same timestamps), so I can't see what's going wrong on this latest attempt. Could you grab the current logs so I can see what's happening now?

To grab fresh logs:

1. In Finder, press ⌘⇧G (Cmd-Shift-G)
2. Paste this path and hit Return:

   ~/Library/Application Support/DozaAssist
   

3. Attach these three files (whichever are present):
   • launch.log
   • setup.log
   • server.log

A couple of things worth checking in the meantime:

Did Python get installed? Open Terminal and run:

brew --version && python3.12 --version

If python3.12 isn't found, run:

brew install python@3.12

…then relaunch Doza Assist.

Is something holding port 5050? The app runs on 127.0.0.1:5050. If another app is using that port it won't come up. In Terminal:

lsof -i :5050

If something shows up, that's the culprit.

---

On the root cause: I've just fixed the bootstrap script so future users won't hit that misleading "Administrator" error — it was forcing Homebrew into non-interactive mode even though the Terminal window is right there to type the password into. That'll be in the next release. Thanks again for being patient working through this.