iv-org / invidious

Invidious is an alternative front-end to YouTube
https://invidious.io
GNU Affero General Public License v3.0
16.42k stars 1.85k forks source link

[Question] Hostname lookup for www.youtube.com failed: Try again (Socket::Addrinfo::Error) #3538

Closed HaJue60 closed 1 year ago

HaJue60 commented 1 year ago

Describe the bug

  1. Health Check invidious container on docker fails.
  2. I can see Message: Error connecting to 'invidious-db:5432': Connection refused (Socket::ConnectError)
  3. application is running, but very very slow.

Steps to Reproduce

Logs

Screenshots

logs.txt docker-compose.yml.txt

Additional context

unixfox commented 1 year ago

Something is wrong with the dns server.

Can you explain how did you install invidious?

HaJue60 commented 1 year ago

Hello Unixfox, thank you for the fast anser. I installed it as descibed in https://docs.invidious.io/installation/#docker-compose-method-production it is a fresh installation.

nslookup www.youtube.com on server is working. see attachment nslookup_on_raspi.txt

inside the container I got an error: /invidious $ nslookup www.youtube.com ;; connection timed out; no servers could be reached

/invidious $

So you it seems that you are right, but at the moment I have no idea why the docker container connot find the dns-server

unixfox commented 1 year ago

What's the architecture of your RPI? Is it ARMv8 or ARM64? You can find it in uname -a.

By the way on RPI you should use the correct docker image: https://github.com/iv-org/invidious/issues/361#issuecomment-881047911

HaJue60 commented 1 year ago

System: Kernel: 5.15.76-v8+ aarch64 bits: 64 Console: tty 0 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: ARM Device System: Raspberry Pi 4 Model B Rev 1.4 details: BCM2835 rev: d03114 serial: uname -a Linux raspberrypi 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux

HaJue60 commented 1 year ago

maybe important: I've running a pihole in the same docker environment.

HaJue60 commented 1 year ago

I found a workaround: I've changed the docker-compose.yml of the pihole as desribed in

https://discourse.pi-hole.net/t/solve-dns-resolution-in-other-containers-when-using-docker-pihole/31413

now it is working

unixfox commented 1 year ago

I'll close this issue as it was a misconfiguration on your side.