# Dns errors with youtube?

**URL:** <https://discuss.huggingface.co/t/dns-errors-with-youtube/163655>\
**Category:** Beginners\
**Created:** [July 18, 2025, 10:09pm UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655 "2025-07-18T22:09:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![atri789](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/atri789/32/50912_2.png) [@atri789](https://discuss.huggingface.co/u/atri789)\
**Post date:** [July 18, 2025, 10:09pm UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/1 "2025-07-18T22:09:44Z")

</div>

apparently hf spaces lost access to youtube for some reason  
not sure if youtube is specifically blocking the calls or is it something else?  
for example i run a simple script and it shows me :  
{  
“detail”: “Error searching video by title: ERROR: Unable to download API page: \<urllib3.connection.HTTPSConnection object at 0x7fd08f2b35c0\>: Failed to resolve ‘[www.youtube.com](http://www.youtube.com)’ ([Errno -5] No address associated with hostname) (caused by TransportError("\<urllib3.connection.HTTPSConnection object at 0x7fd08f2b35c0\>: Failed to resolve ‘[www.youtube.com](http://www.youtube.com)’ ([Errno -5] No address associated with hostname)"))”  
}  
it also applies to all spaces  
any space that has a youtube transcription ,download or anything related to youtube will show the same error  
is it a temporary thing or is there a workaround ?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [July 18, 2025, 11:40pm UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/2 "2025-07-18T23:40:02Z")

</div>

Same here on HF space… What’s going on…?

---

<div class="post-metadata">

**Author:** ![eienmojiki](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/eienmojiki/32/51353_2.png) [@eienmojiki](https://discuss.huggingface.co/u/eienmojiki)\
**Post date:** [July 19, 2025, 1:52am UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/3 "2025-07-19T01:52:14Z")

</div>

same issue with discord api on HF Spaces

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [July 19, 2025, 2:34am UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/4 "2025-07-19T02:34:20Z")

</div>

Also with some other URLs.

> [@N8n on Hugging Face Space: getaddrinfo ENOTFOUND api.telegram.org Connection Error](https://discuss.huggingface.co/t/n8n-on-hugging-face-space-getaddrinfo-enotfound-api-telegram-org-connection-error/163348):
>
> Hello Hugging Face Community, I’m encountering a persistent network connection issue with my n8n instance hosted on a Hugging Face Space, and I’m hoping for some guidance. Problem Description: My n8n workflow, which includes a node attempting to interact with the Telegram Bot API, is consistently failing with connection errors. The primary and most specific error I’m seeing repeatedly is: The connection cannot be established, this usually occurs due to an incorrect host (domain) value getaddr…

---

<div class="post-metadata">

**Author:** ![Vad350](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/vad350/32/51396_2.png) [@Vad350](https://discuss.huggingface.co/u/Vad350)\
**Post date:** [July 20, 2025, 9:13am UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/5 "2025-07-20T09:13:40Z")

</div>

same here with telegram api, it’s not working

---

<div class="post-metadata">

**Author:** ![pikachubolk](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/pikachubolk/32/51660_2.png) [@pikachubolk](https://discuss.huggingface.co/u/pikachubolk)\
**Post date:** [July 24, 2025, 7:16pm UTC](https://discuss.huggingface.co/t/dns-errors-with-youtube/163655/6 "2025-07-24T19:16:25Z")

</div>

This is intended behavior, huggingface will start cracking down on external requests as the majority of users have been abusing it.

Response of HF staff:

 ![1000002431](https://us1.discourse-cdn.com/hellohellohello/original/3X/e/3/e3d5a4a3442c040c1e1d766df99f0b09b22c4d05.jpeg)
