© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
Ok attempt #2.
Looks like the original clause below didn't match any addresses so I was getting connection refused messages
listen-on { ! 10.0.3.1; };
What I found worked on my end was specifying a secondary address match list 'any' which we fall through to match any ipv4 address that is not 10.0.3.1:
listen-on { ! 10.0.3.1; any; };