[Bug]: nginx port stuck on 80

[kolaval]

Platform

Windows

Operating system version

Windows 11 Pro

System architecture

Windows

Herd Version

1.6.1

PHP Version

8.3 (8.3.7)

Bug description

I updated the %USERPROFILE%.config\herd\config\nginx\herd.conf with a new port:
listen 127.0.0.1:8050 default_server;

Nginx service still fails to start with : bind() to 127.0.0.1:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)

Steps to reproduce

Change nginx port in I updated the %USERPROFILE%.config\herd\config\nginx\herd.conf
Start nginx service

Relevant log output

No response

[mpociot]

Do you have any secured/isolated sites? Those could have individual configuration files, that still use port 80.

While you can manually modify the port in your config files, Herd is currently not designed for this and some parts might break by changing the port.

[powlam]

I'm in a similar situation: my company has blocked the port 80 of localhost, so I need to change the port for Nginx manually at herd.conf.
It would be great to allow changing the port of Nginx from Herd's UI; that way it would be under controll and Herd would guarantee that nothing breaks ;)

[patrickodacre]

@mpociot Are you able to provide more detail on what would break if we change this port manually, please? While it would be nice to have a simple option in the app itself, if there were a documented workaround things wouldn't be so bad. From comments like this - #860 (comment) - you can see that Windows 11 users have a less-than-straightforward way to deal with this. It isn't great that we should disable core features of Windows 11 just to get Herd to work.

So to clarify, my first request would be for some details on what would "break" should we change the nginx port in all the config files.
My second request would be for some documentation on the subject, because piecing together all these details from GitHub issues was a bit of a hassle.