I get this error a lot when building: requests.exceptions.ConnectionError:

I receive this error often when using gradio.Interface.load(“spaces/Repo/Name”)
Is this a problem that I can fix on my end?

‘’’
requests.exceptions.ConnectionError: HTTPSConnectionPool(host=‘huggingface.co’, port=443): Max retries exceeded with url: /api/spaces/Omnibus/DPT-Light/host (Caused by NewConnectionError(‘: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution’))
‘’’

5 times in a row now on a space I’m building, and it prevents the build from completing.
Previous commits had no trouble connecting to the space in question.

more words on the topic:

Fetching Space from: https://huggingface.co/spaces/Omnibus/DPT-Light
Traceback (most recent call last):
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/util/connection.py", line 72, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

I duplicated and renamed the target space, (“DPT-Light” => “DPT_Light”), and the 50 lines of code in that space have been building for 10 minutes.

the investigation continues…

image

I’m seeing others with similar errors popping up, so it must be a system problem.

Fetching model from: https://huggingface.co/cedpsam/chatbot_fr
Traceback (most recent call last):
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/util/connection.py", line 72, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

yeah, looks like the problem is systemic. Some spaces are able to build though, if that clue lends itself to a solution.

changing my target space name from (“DPT_Light” => “dptlight”) allowed that space to build without being stuck “building” for 30 mins.

that did not fix it:

Fetching Space from: https://huggingface.co/spaces/Omnibus/dptlight
Traceback (most recent call last):
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/util/connection.py", line 72, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

yeah, something is broken.
"

launch timed out, space was not healthy after 30 min

"

I am also facing a similar issue.

Traceback (most recent call last):
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/home/user/.local/lib/python3.8/site-packages/urllib3/util/connection.py", line 72, in create_connection
    for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
1 Like

I see that Spaces are also being swamped with “UFC advertisements”, so I’m wondering if that is being aligned with a ddos attack, to get those spaces visible, while preventing spaces that have actual content from building. Pure speculation, I have no idea what’s up.

It appears that the issue has been resolved.

1 Like

Just checked in, 2 hrs after your comment here. Seems to be back.

1 Like

This issue has resolved.