1
Web Proxy Filtering and Caching / Re: Starting frontend xxxx: cannot bind socket
« on: September 07, 2024, 11:28:51 am »
Also if you have dynamically assigned IP addresses on you WAN interface, check that the "Listen Addresses" for your HTTP Public Service does not contain an old WAN interface IP-address.
I added my WAN IP like "<wan-ip>:80" in the Listen Addresses and all worked fine until the external IP changed. As far as i understand you do not need to have the WAN IP in the Listen Addresses, only a domain. You will still be able to connect to http://<wan-ip> and have the connection be managed by HAproxy, if you so choose.
Sorry for necro, but this was one of the first hits on google for the error, hopefully it will help someone.
I added my WAN IP like "<wan-ip>:80" in the Listen Addresses and all worked fine until the external IP changed. As far as i understand you do not need to have the WAN IP in the Listen Addresses, only a domain. You will still be able to connect to http://<wan-ip> and have the connection be managed by HAproxy, if you so choose.
Sorry for necro, but this was one of the first hits on google for the error, hopefully it will help someone.