We run a discourse at discourse.lubuntu.me. It is configured to have that as its base URL. However, internally, the system is getting 500 errors with its internal certificate.svg links and the discobot builtin for greeting users. SocketError (Failed to open TCP connection to discourse.lubuntu.me:443 (getaddrinfo: Name or service not known)) /usr/local/lib/ruby/2.6.0/net/http.rb:949:in `rescue in block in connect' This is behaving like it’s unable to do a DNS lookup inside the container running Discourse. Is there a way to fix this issue or better debug it?

This instance was installed following the installation guides here: discourse/docs/INSTALL.md at main · discourse/discourse · GitHub So a straight Docker installation on Ubuntu as a host system. The host system can resolve domains without issue, but it appears that because LXD also runs on the host system it’s intercepting all DNS requests. I’ll have to fix that in a bit, because LXD handling DNS is breaking resolutions. THIS SAID, going into the container and forcing it to recognize itself as the domain returns a “Connection Refused” - so I’ve repointed to the ‘internet facing’ reverse proxy that serves HTTPS here, which seems to work. BUT this required going into /etc/hosts to do it. I’ll have to see if there’s a way to ‘force’ an entry into there during the docker container startup process, but that’s a task for later as it’s ‘working’ for now.

Failure to resolve own domain?

Product Support

Stephen (Stephen) July 8, 2019, 2:36pm 2

Have you tried resolving addresses from inside/outside the container?

How was this instance installed?

Topic		Replies	Views
Discourse docker container has trouble reaching DNS Self-hosting	10	4590	April 30, 2018
Discourse installed in UNRAID Ubuntu Server VM behind NPM reverse proxy not resolving hostname Self-hosting	10	1130	January 30, 2024
After upgrade, docker cannot communicate with the outside world Self-hosting	26	3930	February 1, 2021
./discourse-setup: could not resolve host: github.com Product Support	5	2874	January 3, 2021
Installing: Available on 127.0.0.1 (locally) but not on the public addressout Self-hosting docker	2	1315	June 19, 2015

Failure to resolve own domain?

Related topics