-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] curl: (6) Could not resolve host: raw.githubusercontent.com #246
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Containers inherit DNS from your host. So unless you have some interesting DNS setup that your server is using, it should just work. |
But why would it work with any other container but not the linuxserver ones? Can I give you any logs or information? I tried it again for several other containers like pairdrop from linuxserver. ALL linuxserver have this problem for me. But all others not. |
I don't know what those scripts are that you're using but if you remove them, does it start working? are you able to curl any other addresses? |
also, might be worth explaining your DNS setup that unraid is using. |
I can curl any other address as I mentioned in the beginning. github.com works. google.com as well. Those scripts extend radarr with some features. This script just wants to access raw.githubusercontent.com with |
Unfortunately I haven't got access to any arr containers but testing in our homeassistant container I get:
so it works fine within our containers.
|
I mean I use AdGuardHome and I see request of my other devices on this URL but they are all whitelisted anyway. For you it works and if I do this in any linuxserver container as for example pairdrop it does not work. I have no clue why. Why only the linuxserver container? This is such a weird behavior and hard for me to get as other URLs work in this container as well. For the Home Assistant container it works as well but this is because it runs on the host. Maybe the same reason for you. So it's not a good example. |
Like I said, no access to an arr container at the moment. Just tested in SWAG (our reverse proxy container) which is in bridge mode, working fine (as this is nginx based like pairdrop).
If you're demanding to see an arr example, you'll have to wait for someone else to chime in. |
I have added Before I looked up the DNS config that was existing for radarr:
|
You haven't told us anything about how you've setup your DNS that the unraid server uses so it's impossible to tell. |
I try to find out. Does this help:
The first nameserver is the IP address of my router. In the router I have set a local DNS server to the IP of AdGuardHome. I mean it always used to work like this. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Current Behavior
Something seems to be wrong with all *arr containers of linuxserver. I have the problem for radarr, sonarr, and bazarr. For the first both I need to be able to access the URL
raw.githubusercontent.com
.I tried it with other Docker containers that also contain
curl
and it works fine. Are you blocking this URL for any reason?I need it for the arr-scripts and it used to work fine (https://github.com/RandomNinjaAtk/arr-scripts).
I tried to disable AdGuardHome and Tailscale but is has nothing to do with it as it is only the behavior for the linuxserver container.
Expected Behavior
It should be able to access
raw.githubusercontent.com
. It's no problem for other URLs like google.com or even github.com.Steps To Reproduce
curl raw.githubusercontent.com
curl: (6) Could not resolve host: raw.githubusercontent.com
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: