hm if haproxy was causing the issue, shouldn't it be sooner than that? So I tried and reproduced my issue: https://pastebin.com/XtsWzRKK this is what is seen when netmaker runs for the first time. I create my network, my keys and nodes and then I trash the container. I wait for all time_wait to expire and then pop my container back again:

$ ss -lntpuae|rg -i 8081

docker-compose -f docker-compose-postgres.yml up -d netmaker
Creating netmaker ... done

which is seen as

ss -lntpuae|rg -i 8081
tcp      LISTEN        0         4096                        127.0.0.1:8081                                              0.0.0.0:*                               users:(("docker-proxy",pid=15485,fd=4)) ino:30357445 sk:60fb <->               
tcp      LISTEN        0         4096                       172.17.0.1:8081                                              0.0.0.0:*                               users:(("docker-proxy",pid=15473,fd=4)) ino:30360302 sk:60fc <->               
tcp      LISTEN        0         4096                    91.121.55.138:8081                                              0.0.0.0:*                               users:(("docker-proxy",pid=15462,fd=4)) ino:30361040 sk:60fd <->

on the socket side and I have no API server

$ docker exec -ti netmaker ss -lntpuae|rg -i listen
tcp   LISTEN 0      4096      127.0.0.11:38645        0.0.0.0:*    ino:30363883 sk:6106 cgroup:unreachable:1 <->

poping inside the container