# Gitea: Push to create is not enabled for organizations

**URL:** <https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643>\
**Category:** Install/Maintain/Configure\
**Created:** [February 23, 2024, 12:13pm UTC](https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643 "2024-02-23T12:13:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![reetp](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@reetp](https://forum.gitea.com/u/reetp)\
**Post date:** [February 23, 2024, 12:13pm UTC](https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643/1 "2024-02-23T12:13:25Z")

</div>

This is a fresh instance of Gitea 1.25.2

I have copied various repos from Gitlab into Gitea (like a breath of fresh air!!). I seem to have all the basics setup and working OK.

I’ve been trying to update repo information on my desktop but having issues trying to push to the server.

With this error

`git push`

> Gitea: Push to create is not enabled for organizations.  
> Gitea: ServCommand failed: internal API error response, status=403  
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights  
> and the repository exists.

So I have one organisation only. One Team of Owners only.

It seems to work OK if I clone, add files, commit and push, but I cannot get an existing one to sync.

Any suggestions or bright ideas? I’m sure it is lack of knowledge and/or stupidity on my part but can’t see an answer so far.

---

<div class="post-metadata">

**Author:** ![delvh](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/delvh/32/5047_2.png) [@delvh](https://forum.gitea.com/u/delvh)\
**Post date:** [February 23, 2024, 3:49pm UTC](https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643/2 "2024-02-23T15:49:19Z")

</div>

1. Gitea 1.25.2? Are you a time traveler?

2. 

> Push to create

That’s the feature to create a non-existing repo with a push. You should create the repo first without initializing it, then you can push it.  
Or you [enable push to create](https://docs.gitea.com/next/zh-cn/usage/push-to-create#enabling-push-to-create).

---

<div class="post-metadata">

**Author:** ![reetp](https://avatars.discourse-cdn.com/v4/letter/r/4bbf92/32.png) [@reetp](https://forum.gitea.com/u/reetp)\
**Post date:** [February 23, 2024, 4:21pm UTC](https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643/3 "2024-02-23T16:21:26Z")

</div>

> [@delvh](#):
>
> Gitea 1.25.2? Are you a time traveler?

Ha - that was yesterdays job. 🤣

v 1.21.5

Yeah this is an existing repo I am try to synchronise with, not create new one.

I have sneaking suspicion it is because either the keys aren’t working as expected or the url is incorrect.

I need to go get wine, have a long relaxing weekend, and then test again with a clear head on Monday.

---

<div class="post-metadata">

**Author:** ![delvh](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/delvh/32/5047_2.png) [@delvh](https://forum.gitea.com/u/delvh)\
**Post date:** [February 23, 2024, 9:22pm UTC](https://forum.gitea.com/t/gitea-push-to-create-is-not-enabled-for-organizations/8643/4 "2024-02-23T21:22:58Z")

</div>

Yep, sounds like a wrong pushing URL then.  
What’s the output of `git remote show origin`?