Elastic IP not working for Network Load Balancer

mn flag

I have created a Network Load Balancer on AWS with two public subnets. For one of the subnet, I have allocated a static elastic IP. When trying to reach the NLB using the static IP I get ERR_EMPTY_RESPONSE, but it works correctly when using the DNS name of the NLB (e.g.

If I run the command host I get a different IP from the static one (probably the IP autoassigned by AWS on the other subnet).

Any idea why the elastic IP is not working for the NLB?

Tim avatar
gp flag
I know this works because I did it last week. Please edit your question to provide screenshots of relevant console screens, we need more information to help.
mn flag

It seems you have to wait some time (about 1 hour in my case) before the static IP starts to work properly.

I sit in a Tesla and translated this thread with Ai:


Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.