# Can't Push to New Space

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcant-push-to-new-space%2F35319%3E%5C
**Category:** Spaces\
**Created:** [April 2, 2023, 1:16pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcant-push-to-new-space%2F35319 "2023-04-02T13:16:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![radames](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/radames/32/28246_2.png) [@radames](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fradames)%5C
**Post date:** [April 3, 2023, 5:19pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcant-push-to-new-space%2F35319%2F3 "2023-04-03T17:19:14Z")

</div>

hi @Grokgpt ,

sorry you’re having issues, one note it seems like you’re on OSX, once had similar issue and it was due to my keychain access misconfigured.

> [@I got Authorization error](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fi-got-authorization-error%2F32881%2F5)%3A
>
> I’ve recently encountered similar issues while working on OSX. To resolve the problem, I had to clean up all the huggingface.co password on my keychain access. I also had to reconfigure my git config --global credential.helper osxkeychain then huggingface-cli login. After these steps, it was back to normal. Note these are OSX-specific

One hack way to solve it is to add your token and user to your `.git/config` inside your repo

```auto
[remote "origin"]
        url = https://USER:TOKEN@huggingface.co/spaces/Grokgpt/grokgpt
        fetch = +refs/heads/*:refs/remotes/origin/*

```

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fcant-push-to-new-space%2F35319)._