Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - nope

#1
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.
#2
Just in case someone is as stupid as me and ends up on this page frustrated for not finding the kea configuration setting for default route or default gateway in the web gui for their layer3 switch or secondary router.

Uncheck the "Auto collect option data" to find all the settings you where frustrated wasn't there: