Failed to Retrieve any content

[alekhinexxx]

What should i do for this issue ?

[svilenmarkov]

Could you please confirm that the container has network access?

docker exec glance nslookup github.com

(you might need to replace glance with the appropriate container name or ID)

[alekhinexxx]

Could you please confirm that the container has network access?

docker exec glance nslookup github.com

(you might need to replace glance with the appropriate container name or ID)

i try it but it still failed to retrive any content

[Blemming]

I am getting same thing with twitch and youtube, same error : context deadline exceeded Here are the result from nslookup:

[alekhinexxx]

I am getting same thing with twitch and youtube, same error : context deadline exceeded Here are the result from nslookup:

Hi Blemming, thank you for your information. i dont have any solution for this issue.

[limmh4988]

same issue since 0.63, not resolved in 0.7

[svilenmarkov]

I don't yet know if this is specifically caused by Glance or the presence of some setup-specific OS/Docker configuration change. So, in order to get to the bottom of this, if you're also experiencing the same issue please share the following information:

• Which distro are you using? Debian, Ubuntu, Raspbian, anything else
• Are you using Docker (rootless?) or Podman?
• Have you made any tweaks to the recommended docker-compose.yml?
• Which network mode are you using? (if you don't know you can leave this blank)
• Have you made any network-related OS changes? Custom firewall rules via iptables, etc
• Have you ever had issues with any other containers/services not having network connectivity?
• Are you using a VPN?
• Is your server a VPS?

In addition, could you also run the new diagnose command (since v0.7.0) and check whether you can access anything at all, DNS resolution or a specific service:

docker exec glance /app/glance diagnose

[limmh4988]

hi there.

i think i managed to resolve it.

i am using adguard in my mcvlan (and configure my wifi router to go through that) and I suspected that was the issue.

i included a dns: 8.8.8.8 in my docker compose and restarted.

so far it works.

[jknowles]

I was having the same issue with connections timing out and including a DNS in my docker compose fixed it. I suspect it was my AdGuard instance as well, and bypassing it with a DNS for the container worked like a charm.

[akzov]

* Which distro are you using? Debian, Ubuntu, Raspbian, anything else

Unraid

* Are you using Docker (rootless?) or Podman?

Docker

* Have you made any tweaks to the recommended `docker-compose.yml`?

No

* Which network mode are you using? (if you don't know you can leave this blank)

bridge

* Have you made any network-related OS changes? Custom firewall rules via iptables, etc

no

* Have you ever had issues with any other containers/services not having network connectivity?

no

* Are you using a VPN?

no

* Is your server a VPS?

no

In addition, could you also run the new diagnose command (since v0.7.0) and check whether you can access anything at all, DNS resolution or a specific service

Everything has a tick next to it

[alekhinexxx]

sorry friend, this issue has been resolved. i have report to my vps vendor and this issue occured due to network issue of my vps vendor

[akzov]

I don't have a VPS vendor

[alekhinexxx]

I don't have a VPS vendor

no, i mean provider

[akzov]

I don't have a VPS vendor

no, i mean provider

That's ok because I don't have a VPS provider either

[avlm]

hi there.

i think i managed to resolve it.

i am using adguard in my mcvlan (and configure my wifi router to go through that) and I suspected that was the issue.

i included a dns: 8.8.8.8 in my docker compose and restarted.

so far it works.

same happening here but using pihole. instead of google's dns I just used my pihole's IP and it worked.

dns: my-pihole-ip