In Herd, NGinx not starting

Level 1

If I try to stop Valet I get this:

petervandijck@peters-air code % valet stop
Password:
/opt/homebrew/bin/valet: line 185: /Users/petervandijck/Library/Application: No such file or directory
petervandijck@peters-air code %

Level 1

In Herd, if I click Stop All and then click Start All again, nginx lights up green for a moment and then goes gray.

jurnskie

Level 6

@petervandijck i'm running into this problem aswell.

Level 1

I can't copy and paste the NGINX logs but it says: basically

[emerg] bind() to 127.0.0.1:80 failed (48 Adress already in use)

Level 1

I tried to uninstall and re-install Bind, still the same issue.

Level 18

Do you have Docker running in the background? Docker also uses port 8080, so it can cause problems when using Laravel herd.

you can check bij running this command in the terminal: docker ps

If you get Cannot connect to the Docker daemon... Docker is not running.

You don't need to uninstall Valet, as Herd runs on top of Valet. During installation you were asked whether the Valet settings should be adopted.

Laravel Herd may not be able to stop certain processes when closing, causing them to be grayed out. To test whether this is the cause, you can manually kill all processes and the start Laravel Herd again.

Intel Mac sudo killall nginx-x86 dnsmasq-x86

Apple Silicon Macs: sudo killall nginx-arm64 dnsmasq-arm64

DBngin needs specific settings in the .env file:

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=name_of_database
DB_USERNAME=root
DB_PASSWORD=

Make sure your DB_HOST is 127.0.0.1 and NOT localhost or you’ll get a connection error. DBngin does, if I remember correctly, not handle usernames and passwords instead use ‘root’ and a blank password.

You will have to import existing databases from other DBMS, these are not automatically available in DBngin.

Level 18

To administer the database you could use TablePlus, which works well with DBngin. In DBngin you can click on the arrow next to the database to administer the database in TablePlus.

Level 1

Thank you @eheins

I tried the suggestions but Herd is not starting nginx, and I get the same "address already in use" error in the NGINX logs that I see through Herd.

Any other suggestions to fix this? (I am on an M1 Macbook Pro)

Details:

I do have the right database .env file (127.0.0.1) For Docker, I get this:

petervandijck@peters-air code % docker ps
zsh: command not found: docker

I tried killing processes and got this:

petervandijck@peters-air code % sudo killall nginx-arm64 dnsmasq-arm64
Password:
No matching processes were found
petervandijck@peters-air code %

For DBNgin, I am not sure how to Yimport existing databases from other DBMS?

https://github.com/beyondcode/herd-community/issues

Level 18

You could test whether your local development sites in Herd will work with a secure connection. Then Herd does not use port 8080, but port 443. This can be done in Herd by clicking the relevant lock in the list of websites.

Obviously this does not solve the original problem. You can report your problem on the Laravel Herd support page, perhaps they have a solution.

Level 1

Thanks that's a great idea

Level 1

The weird thing is that even though NGinx in Herd isn't running, my sites are running fine at http://localsite.test

https://abedt.com/blog/fix-laravel-valet-with-a-clean-install/

Level 18

I came across this about uninstalling Valet.

Maybe you can try the steps up to and including Remove dnsmasq, and then reinstall Laravel Herd? Apparently there is a setting left behind somewhere that is getting in the way of NGinx.

1 like

Tesfamariam

Level 1

I was running into this same problem. but I followed these steps then it worked 1 - Uninstalled Herd, from documentation (https://herd.laravel.com/docs/1/troubleshooting/uninstalling) 2 - opened ~/.zshrc and removed path injected by Herd 3 - Installed Herd again, then It worked

1 like

Anaxarchos

Level 15

@Tesfamariam That worked for me as well. But I like to mention, that the final step is to restart the computer after reinstalling Herd. Only then the bug was gone. That might be obvious, but it took me a few minutes before this idea crossed my mind. \ {^_^} /

riordanmb

Level 1

On my system, nginx was installed via homebrew. brew services stop nginx should do it. Additionally, if you don't use the homebrew version of nginx for anything else, brew uninstall nginx. For me, this solved not just the nginx problem, but various other issues as well - including problems starting php.

1 like

makhmuddzhalalov

Level 1

@riordanmb Thanks! This worked for me!

donnell.wyche