# Subject: Issue with Accessing Hugging Face Spaces

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%3E%5C
**Category:** Spaces\
**Created:** [April 12, 2024, 8:46pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493 "2024-04-12T20:46:10Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wheels3321](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@Wheels3321](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FWheels3321)%5C
**Post date:** [April 12, 2024, 8:46pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F1 "2024-04-12T20:46:10Z")

</div>

Dear [Hugging Face Support Team],

I hope this message finds you well. I am reaching out to report an issue I’m encountering with accessing Hugging Face spaces, specifically CohereForAI. Today, Friday, April 12, 2024, I’ve attempted to access various spaces, but unfortunately, I’m unable to view anything. It seems that all spaces are inaccessible at the moment.

I would greatly appreciate any assistance you could provide in resolving this matter.

Thank you for your attention to this issue.

Best regards,

[Wheels3321]

---

<div class="post-metadata">

**Author:** ![ManicHD](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/manichd/32/25780_2.png) [@ManicHD](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FManicHD)%5C
**Post date:** [April 13, 2024, 2:29am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F2 "2024-04-13T02:29:44Z")

</div>

This is also happening to me. I have tried to use many spaces that help me with my needs, but I can not seem to get anything to work, as they show the same screen.  
Below is one image of spaces not working (All spaces do not work for me)

![chrome_PsnEOmTgTp](https://us1.discourse-cdn.com/hellohellohello/original/3X/2/c/2c688f5a0917c8e5ac0e5bfdf4ca1edec23283a2.png)

---

<div class="post-metadata">

**Author:** ![ManicHD](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/manichd/32/25780_2.png) [@ManicHD](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FManicHD)%5C
**Post date:** [April 13, 2024, 3:31am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F3 "2024-04-13T03:31:01Z")

</div>

I had it working, but it went down once again.

---

<div class="post-metadata">

**Author:** ![Wheels3321](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@Wheels3321](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FWheels3321)%5C
**Post date:** [April 13, 2024, 7:36pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F4 "2024-04-13T19:36:11Z")

</div>

Hello Hugging Face Team,

I hope this message finds you well. I’m writing to follow up on the issue I reported yesterday regarding the accessibility of Hugging Face spaces, particularly CohereForAI. Despite checking again today, Saturday, April 13, 2024, the spaces are still inaccessible. Additionally, it seems another user is experiencing the same problem.

Your attention to resolving this matter would be greatly appreciated.

Best regards,  
[Wheels3321]

---

<div class="post-metadata">

**Author:** ![Jplummer19](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@Jplummer19](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJplummer19)%5C
**Post date:** [April 14, 2024, 3:51pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F5 "2024-04-14T15:51:02Z")

</div>

I am having the same issue described above. I switched browsers to see if it was an issue with firefox, but no success. Firefox is giving this error when trying to open a space:

Error code: SSL\_ERROR\_RX\_RECORD\_TOO\_LONG

```
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.

```

Chrome is giving the same frowny face as the user above posted.

---

<div class="post-metadata">

**Author:** ![pierric](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/pierric/32/50750_2.png) [@pierric](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fpierric)%5C
**Post date:** [April 15, 2024, 8:19pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F6 "2024-04-15T20:19:24Z")

</div>

Hi @Wheels3321 @ManicHD @Jplummer19, sorry about that, it seems some internet providers started to block access to Hugging Face Spaces. Can you share your internet providers names?

Also, if you’re comfortable with the command line, can you try this command and share the result: `curl -v http://test.hf.space/`

Thanks!

---

<div class="post-metadata">

**Author:** ![ManicHD](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/manichd/32/25780_2.png) [@ManicHD](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FManicHD)%5C
**Post date:** [April 16, 2024, 12:05am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F7 "2024-04-16T00:05:08Z")

</div>

I am with spectrum.

 ![WindowsTerminal_9n3sFB9xD5](https://us1.discourse-cdn.com/hellohellohello/original/3X/e/a/ea85b9e75714c544840c9f2191094da4beac8257.png)

---

<div class="post-metadata">

**Author:** ![xddlol](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/xddlol/32/25865_2.png) [@xddlol](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fxddlol)%5C
**Post date:** [April 16, 2024, 12:10am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F8 "2024-04-16T00:10:49Z")

</div>

Getting the error on xfinity as well.

 ![Untitled](https://us1.discourse-cdn.com/hellohellohello/original/3X/0/1/01441a3f8ebf4908410675239bb07d8268a06b73.png)

---

<div class="post-metadata">

**Author:** ![pierric](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/pierric/32/50750_2.png) [@pierric](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fpierric)%5C
**Post date:** [April 16, 2024, 11:33am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F9 "2024-04-16T11:33:39Z")

</div>

This confirms the block is at your internet provider level, and there’s nothing we can do on our side unfortunately to fix the problem.

We encourage you to report the problem at [https://spa.xfinity.com/report](https://spa.xfinity.com/report) for Infinity, and [https://www.spectrum.net/support/forms/verify\_url\_security](https://www.spectrum.net/support/forms/verify_url_security) for Spectrum. For instance, in the case of @ManicHD, based on their screenshot above, the URL to report as wrongly blocked would be `metal079-wd-v1-4-tags.hf.space`

Don’t hesitate to report multiple URLs, or to add a message saying that all the apps hosted under `hf.space` seem to be wrongly blocked, not just the one you reported. Thank you for your help!

---

<div class="post-metadata">

**Author:** ![kokomoweb](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/kokomoweb/32/25884_2.png) [@kokomoweb](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fkokomoweb)%5C
**Post date:** [April 16, 2024, 2:16pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F10 "2024-04-16T14:16:18Z")

</div>

Same issue here. Videotron in Canada

---

<div class="post-metadata">

**Author:** ![pierric](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/pierric/32/50750_2.png) [@pierric](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fpierric)%5C
**Post date:** [April 16, 2024, 10:09pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fsubject-issue-with-accessing-hugging-face-spaces%2F81493%2F11 "2024-04-16T22:09:48Z")

</div>

Sorry to hear that @kokomoweb - can you try sending a complaint through [https://www.videotron.com/vcom-ext/secur/forms/Courriel?domain=sac&produit=16&question=145](https://www.videotron.com/vcom-ext/secur/forms/Courriel?domain=sac&produit=16&question=145)?

As mentioned previously, this is unfortunately not under our control, and we need a maximum of users to report those illegitimate blockings to their internet providers.
