# Install problem: \`getaddrinfo: Name or service not known\`

**URL:** <https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783>\
**Category:** Product Support\
**Created:** [May 4, 2018, 7:23pm UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783 "2018-05-04T19:23:52Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [May 5, 2018, 1:50am UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/3 "2018-05-05T01:50:00Z")

</div>

Thanks, Matt. I am somewhat relieved that you didn’t say something like “Uh, duh, you just need to fix the permissions,” so I don’t look foolish. But, really, I’m disheartened that there’s not an obvious and quick solution.

I’m 90% sure that I did an install that worked when these machines were on my home network.

~~I guess I’ll dust off my `discourse-pin-docker` script and work down the list.~~ Well, that wasn’t it.

But, the `tcpdump` appears to have shed the necessary light! And now I see the typo in `/etc/network/interfaces` (perfectly replicated on all three servers) that was the root of the problem.

Hooray for simple (that I still don’t quite understand) networking errors!

And from there I found that I _do_ know how to get `pups` to bind to a single IP.

And soon, a few people can use a server that if it catches on fire will be down until I wake up and look at my phone.

Thanks, Matt. **My day is saved.**

 ![image](https://global.discourse-cdn.com/meta/original/3X/7/2/72eec2d493e020febc66224c69b5e61a437ab84d.png)

---

_[View the full topic](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783)._