-1

I have a Windows Server 2022 with 1 NIC that has 2 addresses, 192.168.1.8 and 192.168.1.9.

There's 2 sites on IIS that listen on 192.168.1.9:80, 192.168.1.9:443 and 192.168.1.9:856, these used to listen on *:80, etc..., changed on IIS Admin "sites > bindings"

Now I want to start apache and I've added Listen 192.168.1.8:80 and Listen 192.168.1.8:443 on the config files but I get the error:

(OS 10013)Intento de acceso a un socket no permitido por sus permisos de acceso.  : AH00072: make_sock: could not bind to address 192.168.1.8:80
AH00451: no listening sockets available, shutting down
AH00015: Unable to open logs

netstat -ano | findstr :80 returns this

TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
TCP    192.168.1.9:57152      x.x.x.x:80          ESTABLISHED     7872
TCP    192.168.1.9:57153      x.x.x.x:80          ESTABLISHED     7872
TCP    192.168.1.9:57154      x.x.x.x:80          ESTABLISHED     7872
TCP    192.168.1.9:57155      x.x.x.x:80          ESTABLISHED     7872
TCP    [::]:80                [::]:0                 LISTENING       4
Daviid
  • 99
  • 4

1 Answers1

-1

From the output you posted, you can see that a process with PID 4 is listening on all interfaces on port 80 IPv4 and IPv6. Next step would be to open your task manager and check which process has PID 4. Then go ahead and change that configuration or shut down that service to free up the port mapping and apache should start without issue.

MoWo
  • 683
  • 1
  • 4
  • 16