Thanks for your report, logs and the steps you’ve tried so far, @alonsodude.
If libcap2-bin is installed on your system (Local’s installer should have added it for you), Local will attempt to run setcap on the nginx binary after checking with getcap if that’s needed; you shouldn’t need to do it manually, but it’s great that you’ve confirmed with getcap that capabilities seem correct.
Do you have AppArmor or anything else that might restrict services on port 80?
sudo aa-status should tell you if it’s running — you’re looking for a path to the Local nginx binary to see if it’s being restricted by AppArmor.
If AppArmor isn’t interfering with nginx, one “last resort” thing you can try is to change what Linux considers to be a priviliged port. By default anything under 1024 is privileged and requires cap changes. You can check the current value with:
sudo sysctl net.ipv4.ip_unprivileged_port_start
And drop it to 0 temporarily with:
sudo sysctl -w net.ipv4.ip_unprivileged_port_start=0
Then run Local and see if site domains work. If they do, you can make the above change permanent by adding the line below to /etc/sysctl.conf. I label this ‘last resort’, though, because it’s a security risk. Any process including those run by non-admin users will then be able to bind to lower port numbers like 80 and 443.
net.ipv4.ip_unprivileged_port_start=0
Then run sudo sysctl -p to apply those changes.